1 CTP offline software status (Offline week) A.Jusko and R.Lietava

2 CTP offline software status 07/07/2008 Outlook Naming scheme for ALICE trigger classes CTP Configuration file for Partition (Run) Counters for Cross section Interaction record - CTP readout Interaction record – online access Trigger inputs - CTP readout

3 CTP offline software status 07/07/2008 Naming scheme Proposal discussed with trigger and offline prepared by F.Antinori, see: Basic elements: Descriptor = logical AND of trigger inputs and 2 L0functions Detector cluster = group of detectors to be read-out Bunch crossing mask = defines which BC in orbit are vetoed Past future protection = conditon imposed on the presence of triggers in the BC preceeding and following the trigger BC Rare flag = defines rare classes, which have reserved special bandwidth

4 CTP offline software status 07/07/2008 Naming scheme for classes Scheme under discussion (for offline use):Scheme under discussion (for offline use): C C e.g.:e.g.: C0SH1-B-NOPF-ALL-R C0SH1-B-NOPF-ALL-R 4 BX mask code PF protection code cluster code rare class flag descriptor code

5 CTP offline software status 07/07/2008 Config File: rxxxxx.rcfg PARTITION: ALICE ############################################ INPUTS: # BC1 BC2 RND1 RND2 -special names for onboard #trigger generators #InName Det Level SignatureOrBCRNDvalue InpNum BC1 CTP RND1 CTP VZERO V SPD_GFO SPD ############################################ # Interaction is any function of first 4 L0 inputs or RND1,RND2,BC1,BC2INTERACTIONS: INT1 ~(SPD_GFO | VZERO) INT2 VZERO ############################################ # Check compatibility with parted # rcfg descriptor = parted descriptors+rnd+bc DESCRIPTORS: # L0 functions can be defined with the name: l0fxxxx l0fmb2 VZERO | SPD_GFO # descriptor = list of inputs and functions, always AND # between list items MB1_RND1 VZERO SPD_GFO RND1 MB2_BC1 l0fmb2 BC1 EMPTY_RND1 RND1 Format not changed (yet) – naming conventions to be used # Maximum of 6 CLUSTERS: ALL 1 SPD SDD SSD TPC TRD TOF PHOS CPV HMPID MUON_TRK MUON_TRG PMD TRG FMD T0 V0 ZDC ACORDE EMCal ############################################################## # Maximum of 4 PFS: NONE ######################################################### # Maximum of 4 BCMASKS: NONE ########################################################### # HW number of cluster is in clusters CLASSES: # Name HW Descriptor Cluster PF BCM Prescaler All/Rare MB1 01 MB1_RND1 ALL {NONE} {NONE} 10 1 MB2 03 MB2_BC1 ALL {NONE} {NONE} 0 1 PULSER 23 EMPTY_RND1 ALL {NONE} {NONE} 0 1

6 CTP offline software status 07/07/2008 Configuration file status Aliroot class written (Cvetan) Send to OCDB - via DAQ logbook - via DCS FXS

7 CTP offline software status 07/07/2008 Counters data 6 counters per Trigger class necessary for cross section Maximum Data volume: (50 classes* 6+ time stamp) counters=305 words Read 1 per min => 305*60=74 kB/hour (to allow for RUN fragmentation and control counter overflow) Counters read viaVME at CTP CPU ( not part of ‘normal’ data flow) Data flow: - CTP -> DCS FXS ->SHUTTLE->OCDB

version run #ofclasses listofclasses Orbit Periodcounter secs usecs L0before L0after L1b L1a L2b L2a Counters data format

9 CTP offline software status 07/07/2008 version Run #ofclasses listofclasses Orbit Periodcounter secs usecs L0before L0after L1b L1a L2b L2a Orbit Periodcounter secs usecs L0before L0after L1b L1a L2b L2a... Counters data format Run43357 (just 1 class)

10 CTP offline software status 07/07/2008 Counters data status File format defined Aliroot class written (Cvetan) CTP dim server part implemented CTP client part implemented Full chain tested from February 08 Todo: error management

11 CTP offline software status 07/07/2008 Interaction records Interaction = 2 different interactions as two independent functions of (first) 4 L0 inputs are to be defined Interaction record = list of interactions in an ORBIT, up to 254 interactions per ORBIT For each DAQ event the interaction records from 2 ORBITS before and 2 ORBITS after are to be added to the event trigger data => Interaction records part of ‘normal’ data stream Full stream recorded also by DAQ Aim: to have full interaction history ± 88 μs for every event recorded by DAQ IR to event stream is being implemented by Klaus

12 CTP offline software status 07/07/2008 Interaction record – online access IR online access necessary for - beam structure monitoring - bunch crossing luminosity - low rate inputs alignment DAQ: Sylvain, Klaus, CTP: Ivan Kralik Tested in lab To be tested in ACR

13 CTP offline software status 07/07/2008 Trigger inputs – CTP Triger inputs (L0 24+L1 24+L2 12) are added to CTP readout by firmware (8+5 words) Software development: to extract them from raw data

14 CTP offline software status 07/07/2008 Summary Configuration file (Partition); ok Counters – Cross section; - error managment Interaction record – CTP readout; in progress - DAQ-CTP debug session in ACR necessary Interaction record – online; in progress Trigger inputs – CTP : ok Implement xsection calculation in aliroot

15 CTP offline software status 08/04/2008 Back up

16 CTP offline software status 08/04/2008 Naming conventions - detectors DetectorCharacter AcordeA BPTXB ReservedC D TRDH TPCL MTRGM TOFO PHOSP RTGR SPDS T0T V0V ZDCZ

17 CTP offline software status 08/04/2008 Inputs, Descriptors, Bunch Crossing mask, Past Future protection Input = n n – trigger level 0,1,2 2 nd char = detector Example: 0SH1 – level 0, SPD high multiplicity 1 trigger Desxriptor = DXXXX - minimum 5 chars

18 CTP offline software status 08/04/2008 Configuration: Load/Start of Run ECS TRIG DB CTP proxy LoadPartition(name.cfg) DAQ logbook rxxxx.rcfg

19 CTP offline software status 08/04/2008 Configuration: End of Run OCDB DCS FXS SHUTTLE TRIG DB ECS CTP proxy STOPPartition(runnum) CTP DIM server xsec DIM client Stop run rxxxx.rcfg

20 CTP offline software status 08/04/2008 Counters: Start of Run ECS CTP proxy STARTPartition(runnum) Open file (<7) CTP DIM server xsec DIM client Start counters

21 CTP offline software status 08/04/2008 Counters: End of Run ECS DCS FXS CTP proxy STOPPartition(runnum) Close file CTP DIM server xsec DIM client Stop counters Shuttle OCDB

22 CTP offline software status 08/04/2008 Counters data format 1 st line = ‘version’ 2 nd line = ‘run number’ ‘num of classes’ ‘list of classes’ 3 rd line = ‘1 st reading’ … n-th line=‘(n-2)-th reading’ EOF reading: 1 st line=time stamp (4 words): ORBIT (24 bits) ‘Period counter’ (28 b) ‘seconds from epoch’(32 b) msecs(32 b) 2 nd line = 1 st class counters: L0before,L0after,L1before,L1after,L2 before,L2 after … (num of classes+1)-th line= last class counters: L0b,L0a,L1b,L1a,L2b,L2a

23 CTP offline software status 08/04/2008 Cross section and Luminosity if you know L, you can calculate σ if you know σ, you can calculate L CTP counters provides information about the number of interactions N(ΔT) preliminary design review; Cross section calculation

24 CTP offline software status 08/04/2008 Trigger Class Logic and Counters σ class - uncorrected cross section for class ‘class’ N Xa,N Xb – counters at level X=[0,1,2] before and after vetoes (see picture). Formula assumes counters are cleared at the beginning L – luminosity Offline procedure for the cross Section calculation

25 CTP offline software status 08/04/2008 CTP Preliminary Design Review, Interaction signals logic  2 interactions can be defined  Interaction: any logical function of 4 L0 inputs

26 CTP offline software status 08/04/2008 CTP data to ESD Trigger and cluster mask or classes in ‘normal’ language as in config file