Data-acquisition Configuration Files

The DAQ configuration files (*.dat setup files) are ASCII-files and can be found in directory $\:\tilde{}$calec_rc/defaults. A configuration file is read by the local CALDAQ RunControl at every run-startup and the data therein is sent to the CALDAQ transputer network as part of the SETUP command.

Here's an example setup file (NB: in this listing line numbers are added at the start of each line, for clarity):

 1:  6              /* experiment number */
 2:  6              /* run number        */
 3:  0000F5AF       /* FCAL boot    map  */
 4:  00000DFF       /* RCAL boot    map  */
 5:  0000FFFF       /* BCAL boot    map  */
 6:  0000F5AF       /* FCAL readout map  */
 7:  00000DFF       /* RCAL readout map  */
 8:  0000FFFF       /* BCAL readout map  */
 9:  600007FE       /* FCAL banks: CAL=2,SR=4,PR=8,LED/LAS=0x10/0x20,FNC=0x40,   */
10:  600007FE       /* RCAL banks  PRT=0x80,BPC=0x100,CAMAC=0x200,SRFLT=0x400,   */
11:  600007FE       /* BCAL banks  SLT1=0x800,SLT2=0x1000 (see file 'bank_bits') */
12:  17 16 16 15  0 16  0 16 16  0 16  0 15 16 16 17  /* FCAL cards/crate */
13:  15 16 14 14 14 14 16 16  8  0 14  3  0  0  0  0  /* RCAL cards/crate */
14:  16 12 16 12 16 12 16 12 16 12 16 12 16 12 16 12  /* BCAL cards/crate */
15:  50             /* triggers/configuration */
16:  300            /* requested trigger rate */
17:  19             /* run type (see file 'run_types') */
18:  0              /* not used */
19:  charge1.acf    /* CNF file */
20:  leopard.dac    /* LED CNF file */
21:  8              /* environment bits (see file 'environment_bits') */
22:  100            /* percentage of events to CALEC */
23:  4              /* data-compression option (see file 'compression_modes') */
24:  1              /* DSP code config, 0=m&s,1=time&energy,2=player,3=test */
25:  Qinj run, all components
26:  1129           /* calib constants (-1=none, 0=dummy, other=version) */
27:  0              /* CAL-SLT/polynomial constants version */
28:  2              /* to CALEC:bit0=testtriggers,bit1=fraction,bit2=all you can */
29:  00000000       /* FCAL crates force samples bitpattern */
30:  00000000       /* RCAL crates force samples bitpattern */
31:  00000000       /* BCAL crates force samples bitpattern */

Line 1 and 2 containing the experiment and run numbers are not significant; the CALDAQ readout system derives the run number from the BOR filename it gets from RunControl.

Line 3, 4 and 5 contain the boot mask for FCAL, RCAL and BCAL respectively; bits 0 to 15 of each mask stand for crate 1 to 16; if a crate is switched on (but not necessarily takes part in the readout) the corresponding bit has to be set to 1.

Line 6, 7 and 8 contain the readout mask for FCAL, RCAL and BCAL respectively; bits 0 to 15 of each mask stand for crate 1 to 16; if a crate is taking part in the readout the corresponding bit has to be set to 1.

Lines 9, 10 and 11 contain the socalled 'bankbit-pattern' for FCAL, RCAL and BCAL respectively, described in chapter 6 ('Bank Bit Pattern').

The lines 12, 13 and 14 containing the number of Digital Cards per crate are only in this file to make these numbers appear in the BOR-banks; the CALDAQ readout system extracts the number of Digital Cards from the hwconfig.dat hardware configuration file, described in chapter 4 ('Hardware Configuration File').

Line 15 and 16 contain the number of triggers per 'configuration' (of the frontend electronics) and the requested trigger rate respectively; these numbers are only taken into account by the CALDAQ system for standalone runs; the number of configurations is determined from the electronics configuration file (see line 19).

Line 17 contains the run type, coded in a decimal number; see table 7 for a list of possible run types.

Line 19 contains the front-end electronics configuration file name; these files are described in chapter 13 ('Front-End Electronics Configuration Files').

Line 20 contains the LED DAC-settings file name; these files are described in chapter 14 ('LED DAC-Settings Files').

Line 21 contains a decimal number, the binary representation of which describes an environment: component 'parts' and/or global components which are participating in the readout of the CALDAQ system in this run:

$\underline{{\bf Dec. value}}$		 $\underline{{\bf Bitmask}}$		$\underline{{\bf Component}}$ $\underline{{\bf participating}}$ 


1 		  0x01 		 GFLT 


2 		  0x02 		 GSLT 


4 		  0x04 		 (Local) EventBuilder 


8 		  0x08 		 CAL equipment computer (aritra) 


16 		  0x10 		 CAL Second Level Trigger transputer network


32 		  0x20 		 BPC Second Level Trigger transputer


128 		  0x80 		 Test-GSLT transputers (replacing GSLT) 

Line 22 contains the percentage of events sent to and stored on the CAL equipment computer, that is: if the 'spy'-option on line 28 is set to getting a 'fraction'.

Table 7: CALDAQ run types.

Name	Id
DAQ Runs
PHYSICS.MODE	1
DUMMY.MODE	2
DUTY.CYCLE.MONITORING	13
LASER	14
DUNO	15
LED.AC	16
LED.DC	17
EMPTY	18
QINJ	19
LED.QINJ	20
-4	21
-4	22
Calibration Runs
DUNO.MONITORING	30
PEDESTALS	31
GAINS	32
DC.LINEARITY	33
Q.LINEARITY	34
LASER.PULSE.SHAPE	35
Q.PULSE.SHAPE	36
DUTY.CYCLE	37
ADC.TO.VOLTS	38
WRITE.CONSTANTS	39
Checkout Runs
Q.CHECKOUT	40
PEDESTALS.CHECKOUT	41
DUNO.CHECKOUT	42
Calibration Runs5
PEDESTALS.CONSTANTS	50
GAINS.CONSTANTS	51
DUNO.MONITORING.CONSTANTS	52
Q.LINEARITY.CONSTANTS	53
ADC.TO.VOLTS.CONSTANTS	54

Line 23 contains the coded zerosuppress/compression option to be used:

$\underline{{\bf Option}}$		 $\underline{{\bf Description}}$ 


0 		    No compression.


1 		    Zero-suppression to the CxTENE-bank;


all channels that have a spark behaviour are saved; 


with 


spark.energy.cut    = 500  MeV 


spark.imbalance.cut = 0.9(REAL32)


2 		    Zero-suppression to the CxTENE-bank; 


with energy.cut = 50 MeV


3 		    Compression of CxTENE-bank entries that comply to:

((0 $<=$ left PM-energy $<$ 32)  OR (-128 $<=$ left PM-energy $<$ 0 ))


and

((0 $<=$ right PM-energy $<$ 32) OR (-128 $<=$ right PM-energy $<$ 0))


into CxPECO-bank entries, keeping the CxTENE-bank entries.


4 		 Same as 3, but now deleting CxTENE-bank entries that moved


to the CxPECO-bank.


5 		 Same as 4, but now the CxPECO-bank is deleted.


6 		 - Compression of xxTENE-bank entries that comply to:

((0 $<=$ left PM-energy $<$ E_THR) OR (-128 $<=$ left PM-energy $<$ 0 ))


and

((0 $<=$ right PM-energy $<$ E_THR) OR (-128 $<=$ right PM-energy $<$ 0))


into xxCOEN-bank entries, while keeping the xxTENE-bank entries,


with


E_THR = 16 for PRESAMPLER and 


E_THR = 32 for CAL, BPC, FNC, PRT, SRTD, Table Diodes (LASER).

- The BOR-event contains the xxPMNO-bank.

- The xxDCCN is compressed: redundant entries (on a crate-by-crate


basis) are marked by bit 15 of the first word (the ID) set.


7 		  Same as 6, but xxTENE-bank entries that moved to the xxCOEN-bank are


deleted, as well as redundant xxDCCN entries.


8 		 Same as 7, but now the xxCOEN-bank is deleted and the BOR-event


does not contain the xxPMNO-bank.

Line 24 contains the number of the DSP-code configuration file to use; see chapter 11 ('DSP-code Files') and 12 ('DSP-code Configuration Files').

Line 25 contains a string describing the type of run etc. (appears e.g. on the user screen of the Local CALDAQ RunControl).

Line 26 contains the calibration constants version to be downloaded; if the number is -1 no constants will be downloaded, if the number is 0 socalled 'dummy' constants will be downloaded; see chapter 8 ('Calibration Constants Files').

Line 27 contains the CAL Second Level Trigger constants version to be downloaded to the CAL-SLT transputers in case of physics runs or the polynomial constants version to be downloaded to the readout transputers in case of calibration runs; see chapter 9 ('CAL-SLT Constants Files') and 10 ('Polynomial Constants Files').

Line 28 contains a decimal number, the binary representation of which describes which 'spy'-option is to be used, meaning which events and the number of events taken ('spied') from the Local EVB buffer and sent to the CAL equipment computer to be stored locally on disk:

• bit 0 set means: take all testtriggers;
• bit 1 set means: take a fraction, the percentage of which is set in line 22;
• bit 2 set means: take as many events as possible without disturbing the central data-acquisition.

'Take-fraction' (bit 1) overrules 'take-as-many-as-possible' (bit 2). To store all events locally, 'take-fraction' should be set to 1 and the percentage (in line 22) to 100.

Lines 29, 30 and 31 contain a mask for FCAL, RCAL and BCAL respectively, defining in which crates the samples of the Digital Cards will be forced to be generated; bits 0 to 15 of each mask stand for crate 1 to 16; if in a crate the samples should be produced the corresponding bit has to be set to 1.

The files referred to in the comment of some of the lines of the DAQ configuration file can be found in directory $\:\tilde{}$calec_rc/defaults/info_caldaq and contain information which also can be found in this document:

• bank_bits: contains the definition of the bits of the 'bank-bitpattern'; see chapter 6 ('Bank Bit Pattern').
• run_types: contains a list of the decimal codes for the different run types; see table 7.
• compression_modes: contains a description of the data-compression options listed above.