The current handler supports the basic Taper, Clover and Cluster Ge+BGO
formats.
The inner ball will now be recognised also.
Auxillary FERA data may work but of now is untestable. If interested, please
contact us.
The Taper Ge and BGO detectors are output in one of two forms ...
If the orignal data was "Format Zero" then Ge and BGO are output together as N-parameter groups,
where the number of words in the following list is dependent on the neo subdetector definition ...
Taper[0:35] (e20, e4, ft, co, bgo_e, bgo_t, pattern)
If the orignal data was "Format Two" then Ge and BGO are output separate N-parameter groups as follows ...
Taper[0:35] (e20, e4, ft, co)
TaperBGO[80:115] (bgo_e, bgo_t, pattern)
The Clover Ge and BGO detectors are output as separate N-parameter groups as follows ...
ClovGe[36:61] (e20, e4, ft, co)
ClovBGO[116:141] (bgo_e, bgo_t, pattern)
The Cluster Ge and BGO detectors are output as separate N-parameter groups as follows ...
ClustGe[62:76] (e20, e4, ft)
ClustBGO[142:156] (bgo_e, bgo_t, pattern_msh, patten_lsh)
The inner ball detectors are output as separate N-parameter groups as
follows ...
BallRaw[157:168] (energy,pattern,tac) BallSum[169] (energy,mult)
The trigger is output as a separate 8-parameter group as follows
...
Trigger[255] (bus1mult,bus2mult,bus3mult,bus4mult,tac,pattern,LSB,MSB)
Auxillary FERA detector parameters must be suitably defined in hardware to be N detectors, each with M parameters to satisy the format as follows ...
FERA[170:249] (param1, param2, ... paramM) where N=249-112+1
If more detector numbers are required and some of the other detectors are not required (e.g. BGO), then it is possible to re-arrange the numbering scheme.
Further information may be obtained from the Euroball Event-by-Event Data Output Format Document EDOC312 (dvi)