HERA-B Target Data Base Description
HERA-B Target Data Base Description
This page was modified last: Jun. 1th 1997 by
Carsten Hast
On May. 31st 1997 C.H. added the database entry and description for
target/hera Label-11 and added the year to the run number counts
On Apr. 8th 1997 C.H. revised the description
On Oct. 21st 1996 C.H. added the description for
target/herabmagne and
target/herabvacuu
On this page a description of our Target Database is given.
Here you find the present data format and some major changes
which have been made during this year. Please refer to
our run protocolls to be informed about spezialities.
The general data flow is like this:
Our Target VME writes target data to a database file which is
completed by additional information from
Hera, Zeus, H1, and Hermes via a Netmex Client Program.
These data are initially written to the database server
hb-con04:33322 and a subset (IA-rate, Positions, p_tau etc.) is
online copied to the server hera-b:11111
The complete database file is copied to our central hera-b computer,
volume /hbd4/target_97/database typically the day after.
If you want to access these data
you should follow this gide line:
Online Situation,
i.e: we are taking data and you want to see the
actual status
Actual database files are locked by the database server
hb-con04:33322. You may access data via
tablex or some c-code with calls to this server.
You should not overload the server with too often calls, since
the online target needs are allready 10 requests/s!
If you just want to see our rates, wirepositions or eg. background
at the other experiments I recommend to use the following program
on any hb-con.. computer: /home/hbwire/running/information/HeraInfo.
It is pure ASCII and looks awfull at the beginning (you get trained)
but has the
advantage to show all gathered information on one page.
There is even a
description which includes some other hints how to access
data out of databases.
For an online display please use our copied data on the hera-b.
Please change to the
following hera-b directory /home/x4u/hbwire/information/TargetDisplay
and start the program "TargetDisplay" to see a regularily updated
rate and position display. In addition our actual target efficiency
is shown.
The entries into the Target Data Base are the following:
- target/h1
Title: H1:Lumi,FPSrates,FPSstatus,FPSpos,Bg
Label-1 float:Lumi
Label-2 ushort:FPSrates
Label-3 byte:FPSstatus
Label-4 ushort:FPSpos
Label-5 ushort:Bg
Lumi: (1 float value)
H1 specific Lumi in cm-2s-1mA-2
(1996 Run 1-6: current Lumi)
FPSrates: (6 unsigned short values)
FPS-rate 81/90, FNC-trig, FPS-trig, BLM-rate 84/92 all in Hz
(1996 Run 07-21: (3 us values) FPS-rate (81m), FPS-rate (90m), FNC-rate)
(1996 Run 01-06: (3 us values) FPS-rate (81m), FNC-rate, FNC-rate)
(1996 Run 01-21: Please check the ordering in your software since the
description was wrong!)
FPSstatus: (2 byte values) 3 1 is ok
first number: 0: no pot, 1: pot 81, 2: pot 90, 3: both pots are in,
second number: 0: no daq, 1: daq is running.
(In 1996 Runs 1-26 these numbers were allways 0)
FPSpos: (2 unsigned short values)
FPS-pos (90m), FPS-pos (81m) in mu_m (60000 is out)
Bg (2 unsigned short values) p and e gated Veto rate, both in Hz.
(this database entry exits since 1996 Run 24)
Major number is set to the H1 TimeStamp (h1.lumi.ts) (1996 Run 1-6)
Major number is set to the H1 TimeStamp (h1.fps90.pos.ts) (1996 Run > 6)
In both cases this means the time data were taken.
The TS of FPS90 is the same for both pot-pos/rates and the H1-FNC rate.
The difference to the lumi TS is small.
- target/hera
Title: HERA:pe Energy Curr
Tau,Tune,Emitt,BPM,ColRates,ColPos,BPMx,BPM
Label-1 ushort:Energy
Label-2 float:CurrTau
Label-3 float:Tune
Label-4 float:Emitt
Label-5 short:BPM
Label-6 ushort:Colrates
Label-7 ushort:Colpos
Label-8 short:BPMx
Label-9 short:BPMy
Label-10 float:BLM
Label-11 short:EBpmCol
Energy: (2 unsigned short values) E_proton, E_electron, both in GeV.
Curr Tau: (4 float values) I_p, T_p, I_e, T_e in mA, h.
Tune: (2 float values) proton tune x, y.
Emitt: (3 float values) proton emittance x,y and a meaningless 0.
(only measured in the beginning of a run, see db_entry for target/heraemitta)
BPM: (6 short values) beam position monitors: Zeus (L61xy) used for positioning the LPS,
HB_old(R126xy,R86xy), all in 10 mu_m.
ColRates: Collimator-rates WR94 ,W3319, WL105, WL150, all in 100Hz.
ColPos: Collimator-positions (above positions: above, below, inner, outer)
in mu_m without sign
There was an error in the description: WL150 and WR94 have
been interchanged. On Oct.14th 1996 C.H.
changed to the new order, given above (this order is valid since 1996 Run 25).
(The old order was: 1. WL150, 2. WL105, 3. WR94, 4. W3319)
BPMx: (9 short values) BPM X positions from WR126 86
68 36 10 WL24 44 96 128
(this database entry exits since 1996 Run 22)
BPMy: (9 short values) BPM Y positions from WR126 86 68 36 10 WL24 44 96 128
these are informations about the beam position monitors from WR126 up
to WL128, all in 10 mu_m.
(this database entry exits since 1996 Run 22)
BLM: (27 float values) Beam loss monitors in the West: WR252 225 196 163 185nc 133
94K2 94K1 61 40 33K2 33K1 18 WL19K1 19K2 23 43 58 79D 91 123 105K1
105K2 153K1 126CERN 162 195. The numbers are #protons lost per 5.2 msec
(this database entry exits since 1996 Run 22 but in 1996 Run 22 all are 0)
EBpmCol: (4 short values)
Electron Beam position monitors at WR133 X and Y in 1/100 mm and
electron collimator positions at WL11 above and inner in 1/100 mm.
(this database entry exits since 1997 Run 30)
Major number is set to the HB_client TimeStamp meaning the time when
our client program writes the data to the database. This is done since
all Hera TS differ severely, and will be changed when the situation improves.
- target/herabmagne
Title: HERA-B Magnet: Current
Label-1 float:CurrMagnet
Current: (1 float value)
Hera-B magnet current as delivered from MKI. This value is read out
all 7 minutes and hardly ever changes, the full power value is 4279.5 A.
During ramping times of the proton machine no update is
delivered. This is noted by 0 entries.
(this database entry exits since 1996 Run 24)
Major number is set to the time when the current was
measured
- target/herabvacuu
Title: HERA-B Vacuum: Preasures,Status
Label-1 float:HBvacuum
HBvacuum: (20 float values)
These are the vacuum preasures in and around our vertex vessel.
To which pump each individual number belongs is not totally clear to
me, but I try to find it out....
(this database entry exits since 1996 Run 24)
Major number is set to the time when the preasure was
measured
- target/heraemitta
Title: HERAemit: emitt, norm emittance
Label-1 float:Emittance
Emittance: (2 float values) emittance as measured by
wire scanner and normalized emittance as measured by wire scanner.
To be honest I don't know what these numbers mean.
Major number is set to the time when data were taken
- target/heratext
Title: HERAtext: HeraText1, HeraText2
Label-1 ascii:HeraText1
Label-2 ascii:HeraText2
HeraText1: (48 ascii values) first text line of the Hera display
HeraText2: (48 ascii values) second text line of the Hera display
Major number is set to the time when data were taken
- target/hermes
Title: HERMES:Proton Bg Rate
Label-1 ushort:bgRate
bgRate: (1 unsigned short value) proton induced bg rate in Hz
Major number is set to the time when data were taken
- target/t_info
These table entries give information about the settings
(mainly automatic parameters) done in the Target Control Center (TCC).
Title: Hera-B Autoinfo: T R SS D PD ND W TC S E OE
Label-1 byte:Autotype
Label-2 ubyte:Autorate
Label-3 short:Stepsize
Label-4 byte:Ratediff
Label-5 byte:Ratepdiff
Label-6 byte:Ratendiff
Label-7 byte:Width
Label-8 byte:Tconst
Label-9 ubyte:Steps
Label-10 ubyte:Autoemerg
Label-11 ubyte:OverAE
Autotype (1 byte value) T: Type of automatic
Autorate (1 unsigned byte value) R: Rate to be stabelized
Stepsize (1 short value) SS: StepSize used
Ratediff (1 byte value) D: max. rate-Difference between two actions
(used for drive-out-automatic only)
Ratepdiff (1 byte value) PD: max pos rate-Difference between two actions
(used for diff-automatic only)
Ratendiff (1 byte value) ND: max neg rate-Difference between two actions
(used for diff-automatic only)
Width (1 byte value) W: Width in % inbetween which the rate will be stabelized
Tconst (1 byte value) TC: Number of measures for calculating mean rate and width
Steps (1 unsigned byte value) S: Number of Steps for changing the inter auto rate
Autoemerg (1 unsigned byte value) E: Automatic Emergency rate
OverAE (1 unsigned byte value) OE: Overall Emergency rate
Major number is set to the time when data were taken
target/t_status
Title: Hera-B:Wstat(3=in,2=inbetween,1=out),Rstat(3=r>0.3MHz,2=low r,
Label-1 int:Status
Status (2 integer values) first: 1: all wires are
out, 2: at least 1 wire is moving in, 3: at least 1 wire is close to the beam
second: 1: no rate 2: background rate, 3: small to high rate produced
by the target.
This flags may be usefull for online displays.
Major number is set to 1, so entries are overwritten
target/target
Title: Hera-B:Pos,Rates,allRates,movelogging
Label-1 float:Positions
Label-2 float:Rates
Label-3 float:allRates
Label-4 byte:WireNo
Label-5 ushort:Step
Label-6 ushort:Rate
Label-7 ushort:mSec
Label-8 ushort:Time
Label-9 ushort:Mean
Label-10 ushort:Sigma
Label-11 ushort:Interar
Positions: (8 float values)
Pos: 8 wire Positions: I above, below, inner, outer; II a, b, i, o in
mm. Wires are out at values around -40.
Rates: (32 float values) Rates as measured by the target program (in MHz)
Please refer to the scaler input information which exist for each run
to get the meaning of each individual rate. As an example how these
file lookes like you may click here for Scaler Inputs. The interesting information you find below the header
"VME-scalers - target @ hb-vme01".
allRates (variing even number of float values)
Rates in MHz
odd entries: all interaction rates measured since the last database entry
even entries: all background rates measured since the last database entry
(this database entry exits since Run 22 but in Run 22 -- 24 all rates are
equal to 'Rates')
movelogging gives you detailed information about each single move since
the time given in Label-8: 'Time'. movelogging referes to Labels 4-11.
There may be up to 256 entries.
WireNo: (variing number of byte values) These values
code which wires have been moved: +/- 1-8: wires 1-8 have been moved
in/out. +/- 11-18: wires should have been moved, but the controler was
busy.
Step: (variing number of unsigned short values)
This gives the stepsize in 0.1 mu_m.
(1996 Run 1-26: There are some rounding problems for small numbers:
0.3->0.2, 0.6->0.5, 1.2->1.1, ... mu_m. You can correct for this by
checking the given positions and the number of 'Step's inbetween these.)
Rate: (variing number of unsigned short values)
Actual measured Interaction Rate in kHz. Max at 65535, for higher
rates you have to add this number to the given one, but be careful.
mSec: (variing number of unsigned short values)
Time in m_sec when the move was performed. This time has to be added
to the 'Time' value following next line.
Time: (1 unsigned short values)
Last 4 digits of the unixtime in seconds when the first move was
performed noted in these table entries. The correct time you have to
construct out of the major number of these database entries and these
last 4 digits. Starting from 'Time' the m_sec (given in 'mSec') are
following in increasing order. There may be entries for longer times than 1
second, so 'mSec' wraps around and you have to increase the number of
seconds by 1 at each crossing of 0 'mSec'.
Mean: (variing number of unsigned short values)
Mean value of the interaction rate as calculated by the automatic
procedure (in kHz). See comment for 'Rate'
Sigma: (variing number of unsigned short values)
Mean value of the sigma of the interaction rate as calculated by the automatic
procedure (in kHz). See comment for 'Rate'
Interar (variing number of unsigned short values)
Inter Auto Rate is a rate value which is inbetween the actual rate and
the desired rate. Used and calculated in the automatic procedures. (in kHz)
Major number is set to the time when data were taken.
- target/zeus
Title: slumi,C5,FLT,FPSstatus,FPSpos,C5singleBlmRates
Label-1 float:sLumi
Label-2 ushort:C5rates
Label-3 ushort:FLTrates
Label-4 byte:LPSstat
Label-5 ushort:LPSpos
Label-6 ushort:C5short
Label-7 ushort:LPSrates
slumi:(1 float value) Zeus specific Lumi in cm-2s-1mA-2
C5rates: (8 unsigned short values) C5-rates in
Hz. Seldomly updated by Zeus.
north beam pipe: proton side, electron side; south beam pipe: proton side, electron side;
coincidence: north, south; OR of coincidences; AND of coincidences
FLTrates: (7 unsigned short values) First Level Trigger rates in Hz
FNC, C5, C5VETO, BCALrc*VWout*IFRbp, VETOwall_IN, VETOwall_OR, LPS_hit
LPSstat: (2 byte values) Status of LPS, 1 0 is ok.
First number: LPS status = 1 if everything is okay,
second number: LPS panic = 0 if there's no reason to panic.
LPSpos: (9 unsigned short values) Roman Pot positions
in mu_m (S1, S2, S3, S4_up, SL63(=S4_down), S5_up, SL81(=S5_down), S6_up,
SL90(=S6_down)). The out positions are: 26556 31408 24663 37724 41915
29435 55727 33776 55166 mu_m.
C5short: (2 unsigned short values) Proton and
electron gated C5 background rates in Hz. Updated by Zeus each second.
(Implemented since 1996 Run 22 but entries are 0 in 1996 Run 22)
LPSrates: (3 unsigned short values)
S4_up Trigger rate, S6_up Trigger rate, BLM_SL116 rate, all in Hz.
(Implemented since 1996 Run 22)
Major number is set to the HB_client TimeStamp meaning the time when
our client program writes the data to the database (1996 Run 1-6)
Major number is set to ZEUS TimeStamp of the FLT (zeus.flt.ts) (1996 Run > 6), meaning
the time when data were taken.
Zeus TimeStamps for different values differ severely.
Last update: Oct-21-96 Carsten Hast
Last update: Dec-16-97 Torsten Jagla