Subevent Data Structures

A subevent is organized similar to an event, starting with a length field, followed by the Type/Subtype field.

The Subevent Types assigned so far are:

• 32-127: types common to CAVE B
  • 32: common FASTBUS data,
  • 33: common FASTBUS parameters,
  • 34: common CAMAC data,
  • 35: common CAMAC parameters,
  • 36: ASCII Data,
  • 37: LeCroy 1440 parameters,
  • 38: FERA Data,
  • 39: FERA Parameters,

  The definition of the Subevent SubTypes is up to the experiments themselves, in general they should have the meaning of a revision level.

  • 2000-2999 Reserved for 4
    • 2000: FOPI CAMAC,
    • 2001: beam monitor,
    • 2002: Strasbourg IC,
    • 2003: Spill scaler,
    • 2004: event scaler,
    • 2011: Florence telescope scaler,
    • 2010: Florence telescope data,

  A negative subevent type indicates that an error has occured somewhere in the acquisition of the data. See below for details.

 
Figure:  Structure of a common FASTBUS subevent

A FASTBUS module header preceeds a group of data words from modules of the same hardware type. At the moment of this writing, only one type of modules (LeCroy xxxx) is used and the field is zero.

 
Figure:  Structure of a Fastbus dataword

 
Figure:  Structure of a common CAMAC subevent

The Strasbourg data may be zero-suppressed. Therefore a format similar to the Plastic Wall FASTBUS data has been chosen.

 
Figure:  Structure of a Strasbourg CAMAC subevent