Generation

In this chapter will be described how the selection of banks to be generated on the READOUT transputers takes place.

Per (sub)component and per triggertype there is a list of banks (see file banksets.inc) to be produced; at every startup a hardware configuration file (hwconfig.dat, see chapter 4 ('Hardware Configuration File')) is read that contains amongst other things per crate a list of Digital Cards and the component each Digital Card belongs to; from this information and the banklists the READOUT transputer compiles a banklist per triggertype containing all banks to be produced from all components present in that crate for that particular triggertype.

There are some limitations to the Digital Card distribution related to the generation of banks:

• Digital Cards in one crate belonging to one subdetector should be located next to one another.
• Digital Cards of one subdetector can only be put in more than one of the FCAL, BCAL or RCAL parts of the CALDAQ system when different bank names are defined for each of the CALDAQ system parts in which the subdetector is present.

At every startup a socalled 'bank-bitpattern' is sent along with the hardware configuration (can be set separately for FCAL, BCAL and RCAL; see chapter 5 ('Data-acquisition Configuration File')).

Using the 'bank-bitpattern' the generation of banks can be steered; all banks of a certain component may be 'switched off' (i.e. its banks are not produced) or certain bank 'types' or 'classes' (e.g. BeginOfRun banks) may be enabled/disabled; see chapter 6 ('Bank Bit Pattern').

For every bank in the compiled banklists the required bank-bitpattern is compared to the received value and generation of the bank is disabled if the required bank-bitpattern is not a subset of the received value (this applies only to the bits in the bank-bitpattern that steer the generation of bank classes).

The most important constants governing the generation of banks:

• COMPONENT.BANKSET.LIST: a two-dimensional list of banklist identifiers (indices into array BANKSET.BANKLIST) ordered by component and by triggertype (in file banksets.inc).
• BANKSET.BANKLIST: a list of banklists ordered by banklist identifier (in file banksets.inc).
• BANK.CONTROL: the required bank-bitpattern for every possible bank can be found (in file bankcontrol.inc).

Adding a new bank(set) or component involves additions/changes to several files in the include, readout, libs and test subdirectories in /zeus/transputer/online/vxx.y/src/ (CALDAQ transputer code version xx.y).

Appendix B shows a complete list with short descriptions of all additions and modifications needed to incorporate a new Digital Card based subdetector in the CALDAQ readout system.

The most important include files are:

• bankbitpattern.inc: contains the definitions of the bits in the bank-bitpattern
• bankcontrol.inc: contains a list of required bank-bitpatterns, one per bank
• banks.inc: contains bank indices and per bank the number of columns
• banks_info.inc: contains per bank info about the component it belongs to, the amount of data associated with it and possible alternative banks (per event only one of the alternative banks can be generated); this info is used by the eventsize calculation tool described below
• banks_maxsize.inc: contains per bank and per calorimeter a maximum number of rows to avoid event sizes too large to be handled upstream by the EVB/TLT (e.g. if samples are forced in all crates)
• banksets.inc: contains lists of banks to be generated per component and per triggertype
• zebra_decl.inc, zebra_init.inc: contains definitions and lists of hollerith constants used by the ROCOLLECT transputer to build the banks in ZEBRA-format.