1CTP offline review
1
CTP offline meeting21/01/2009
A.Jusko and R.Lietava
2CTP offline review
2
Outlook
• Naming Convention• CTP Configuration file for Partition (Run)
– Prescaling (2 modes now)– Group time allocation
• Trigger inputs - CTP readout• Counters for Cross section• L2a counters at the end of the run • Interaction record• Misc – timing, beam structure
3CTP offline review
3
Naming schemeProposal discussed with trigger and offline prepared by F.Antinori, see:http://aliceinfo.cern.ch/Offline/Activities/TriggerConvention/index.html
Basic elements:• Detector• Input• 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 = condition imposed on the presence of triggers in the BC preceding and following the trigger BC• Rare flag = defines rare classes, which have reserved special bandwidth• Prescaler factor• Class = Descriptor+Cluster+BCM+PF+Rare+Prescaler
4CTP offline review
4
Naming conventions - detectors
Detector Character
Acorde A
BPTX B
Reserved C
Reserved D
TRD H
TPC L
MTRG M
TOF O
PHOS P
RTG R
SPD S
T0 T
V0 V
ZDC Z
5CTP offline review
5
Inputs, Descriptors, Class
• Input = n<3-char code>
n – trigger level 0,1,2
2nd char = detector
Example: 0SH1 – level 0 , SPD high multiplicity 1 trigger
• Descriptor = DXXXX
- minimum 5 chars
• Class:
6CTP offline review
6
Naming: Pending issues
• Naming for internal inputs (BC1,BC2,RND1,RND2,L0 functions) (F.Antinori)
• Naming scheme for multiple level trigger
• Review the scheme after first experience with its usage
7CTP offline review
7
Format not changed (yet) – naming conventions to be used
Config file: rxxxx.rcfg
VERSION: 3PARTITION: ALICE############################################INPUTS:# BC1 BC2 RND1 RND2 -special names for onboard #trigger generators#InName Det Level SignatureOrBCRNDvalue InpNum BC1 CTP 0 4799999 0RND1 CTP 0 52076 0VZERO V0 0 42 2 SPD_GFO SPD 0 20 4 ############################################# Interaction is any function of first 4 L0 inputs or #RND1,RND2,BC1,BC2 (operators: & | ~ ^)INTERACTIONS:INT1 ~(SPD_GFO | VZERO)INT2 VZERO | BC1############################################# Check compatibility with parted# rcfg descriptor = parted descriptors+rnd+bcDESCRIPTORS:# L0 functions can be defined with the name: l0fxxxxl0fmb2 VZERO | SPD_GFO # descriptor = list of inputs and functions, always AND # between list items MB1_RND1 VZERO SPD_GFO RND1MB2_BC1 l0fmb2 BC1 EMPTY_RND1 RND1
# Maximum of 6CLUSTERS:ALL 1 SPD SDD SSD TPC TRD TOF PHOS CPV HMPID MUON_TRK MUON_TRG PMD TRG FMD T0 V0 ZDC ACORDE EMCAL CTP############################################################### Maximum of 4PFS:NONE########################################################## Maximum of 4BCMASKS: NONE############################################################ HW number of cluster is in clustersCLASSES:# Name HW Descriptor Cluster PF BCM Prescaler All/RareMB1 01 MB1_RND1 ALL {NONE} {NONE} 10 1MB2 03 MB2_BC1 ALL {NONE} {NONE} 4 1PULSER 23 EMPTY_RND1 ALL {NONE} {NONE} 0 1
8CTP offline review
8
############################################################ HW number of cluster is in clustersCLASSES:# Name HW Descriptor Cluster PF BCM Prescaler All/Rare Group TimeMB1 01 MB1_RND1 ALL {NONE} {NONE} 0xa 1 0 0MB2 03 MB2_BC1 ALL {NONE} {NONE} 0x80000002 1 1 4MB3 03 MB2_BC1 ALL {NONE} {NONE} 0x2 1 1 4PULSER 23 EMPTY_RND1 ALL {NONE} {NONE} 0x0 1 2 1
Classes Prescaling
Prescalers options
• Random time veto option: pseudorandom veto generation with programmable rate (21 bits)
• Class busy option: programmable class trigger busy time (25 bits, 1bit=10 usec = 400 BC)
• 31th bit: 1 = class busy option
• Example: 0x80000002 – class busy downscaling with 20 microsecs dead time
9CTP offline review
9
Class Grouping
Class grouping
• To allocate time periods to groups of classes to avoid ‘resonances’ due to the regular triggers (e.g. initial period of beam)
• Group:
– 0 : allways on
– 1-9: active Time secs
• 0 and one of (1-9) active at any time
• Above example: MB1 always on; (MB2,MB3) 4 secs on, PULSER 1 secs on, (MB2,MB3) 4 secs on, PULSER 1 sec on, ….
############################################################ HW number of cluster is in clustersCLASSES:# Name HW Descriptor Cluster PF BCM Prescaler All/Rare Group TimeMB1 01 MB1_RND1 ALL {NONE} {NONE} 0xa 1 0 0MB2 03 MB2_BC1 ALL {NONE} {NONE} 0x80000002 1 1 4MB3 03 MB2_BC1 ALL {NONE} {NONE} 0x2 1 1 4PULSER 23 EMPTY_RND1 ALL {NONE} {NONE} 0x0 1 2 1
10CTP offline review
10
Configuration file status
• Aliroot class written (Cvetan)• Send to OCDB
- via DAQ logbook
- via DCS FXS (removed in the latest version)
11CTP offline review
11
Trigger inputs – CTP• Trigger inputs (L0 24+L1 24+L2 12) are added to
CTP readout by firmware (8+5 words)
12CTP offline review
12
CTP inputs: pending issues
• CTP inputs (24 L0 + 24 L1 + 12 L2)– Now read out by the DAQ whenever the CTP is
included as a readout subsystem– Code for reading from RAW is in place– Inputs parameters (delay,pos/neg) -> DB,
loading at CTP proxy restart • Action:
– propagate information to ESD and AOD? (Offline)
13CTP offline review
13
xCounters 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
14CTP offline review
14
123265 9 1 2 3 4 5 6 7 8 93431363 0 1204292441 6295160 0 0 0 0 01 0 0 0 0 0 0 0 0 0 0 0104 43 43 43 43 430 0 0 0 0 04 4 4 4 4 40 0 0 0 0 00 0 0 0 0 00 0 0 0 0 0 3723686 0 120429467 623556
versionrun #ofclasses listofclassesOrbit Periodcounter secs usecsL0before L0after L1b L1a L2b L2a1 0 0 0 0 0 0 0 0 0 0 0104 43 43 43 43 430 0 0 0 0 04 4 4 4 4 40 0 0 0 0 00 0 0 0 0 00 0 0 0 0 0 3723686 0 120429467 623556
xCounters data format
15CTP offline review
15
versionRun #ofclasses listofclassesOrbit Periodcounter secs usecsL0before L0after L1b L1a L2b L2aOrbit Periodcounter secs usecsL0before L0after L1b L1a L2b L2a...
xCounters data format(real example)
143357 1 1 10623527 0 1215243845 558137906491822 126163588 126163585 126163585 126163582 126163582 10855234 0 1215243866 162760906566888 126235112 126235109 126235109 126235106 126235106 11532829 0 1215243926 418087906786409 126454633 126454630 126454630 126454626 126454626 12210435 0 1215243986 674413907005933 126674157 126674154 126674154 126674151 126674151 12888041 0 1215244046 930743907225458 126893682 126893678 126893679 126893675 126893675 12896317 0 1215244047 666719907228139 126896358 126896355 126896355 126896352 126896352
Run43357 (just 1 class)
16CTP offline review
16
xCounters data status
• File format defined• Aliroot class written (Cvetan)• CTP dim server implemented • CTP client implemented• Full chain tested from February 08 –file/run is
sent to OCDB over DCS FXS
17CTP offline review
17
xCounters: pending issues
– Check the consistency of collected data (CTP group)
– In case they are needed in analysis we have to propagate them to ESD/AOD
• Spline fit in AliESDRun
• Or extrapolated values for each event/ESD
• Improve error managment
18CTP offline review
18
L2a counters: pending issues
• L2A counters
– The end-of run values are currently sent to the info logger, but not to the DAQ logbook
– Example: Run:62554 Partition:PHYSICS Duration(usecs) 563630834 L2a counts [class,counts]: [1,537] [2,71011] [3,2059]
• Action:
– propagate the information to the DAQ logbook (Anton)
• Can we make use of the counters in central (automatic) raw-data reconstruction?
19CTP offline review
19
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 (DAQ)
• Full stream recorded also by the End of Run Event (DAQ)• IR stream sampled for luminosity (per bunch) and beam structure
(I.Kralik)
Aim: to have full interaction history ± 88 μs for every event recorded by DAQ
20CTP offline review
20
IR: pending issues
• Items identified for further review– propagation of interaction record information in
the event data and at end of run (CTP + DAQ)• There are event data collected – DAQ parts works
fine, offline code as well
• End-of-run– STATUS ?
– Data flow max= 256 int/orbit=20Gb/hour
– Data flow 200kHz = 1.4 Gb/hour
21CTP offline review
21
Misc:• Time between interaction and L0:
– Fixed for given detector– Same for all triggers after alignment– In the initial period before alignment time can be
different for different triggers• Beam structure
– How and when do we get information about beam structure from LHC ?
• Configuration of triggering detectors:– Shuttle preprocessors to be modified, in
discussion
22CTP offline review
22
Summary
• Configuration file (Partition) – version 2 -> version 3• Counters – Cross section: - error management - to be checked in offline - add to ESD• Interaction record:
– to be checked in offline (EoRunEvent, ESD)– EOR interaction record status
• Trigger inputs –sent over DDL. - to be extracted from CTP readout - to be added to ESD - input parameters to be saved in CTP DB
23CTP offline review
23
Back up
24CTP offline review
24
Configuration: Load/Start of Run
ECS
TRIGDB
CTPproxy
LoadPartition(name.cfg)
DAQ logbook
rxxxx.rcfg
rxxxx.rcfg
25CTP offline review
25CTP offline software status 08/04/2008
Configuration: End of Run
OCDB
DCS FXS
SHUTTLE
TRIGDBECS
CTPproxy
STOPPartition(runnum)
CTPDIM
server
xsecDIMclient
Stoprun
rxxxx.rcfg
26CTP offline review
26CTP offline software status 08/04/2008
Counters: Start of Run
ECS
CTPproxy
STARTPartition(runnum)
Open file (<7)
CTPDIM
server
xsecDIMclient
Startcounters
27CTP offline review
27CTP offline software status 08/04/2008
Counters: End of Run
ECS
DCS FXS
CTPproxy
STOPPartition(runnum)
Close file
CTPDIM
server
xsecDIMclient
Stopcounters Shuttle
OCDB
28CTP offline review
28
parted
Pydim(parted)
htmlctpBusy
xcounters
ctpdims
ctpproxy
DAQ DB
.partition
.pcfg
.rcfg
.html
.cnts
DAQlogalidcscom026
alidcsvme001
1
3
2 1. DIMcmnd: SOR/EOR, CalTrig requests
2. DIMcmnd: Load/Stop partition
3. DIMservice: once per min. +SOR/EOR
4. DAQDB update by ctpproxy
File r/w
DIM messages
4
29CTP offline review
29CTP offline software status 08/04/2008
Counters data format
1st line = ‘version’
2nd line = ‘run number’ ‘num of classes’ ‘list of classes’
3rd line = ‘1st reading’
…
n-th line=‘(n-2)-th reading’
EOF
reading:
1st line=time stamp (4 words):ORBIT (24 bits) ‘Period counter’ (28 b) ‘seconds from epoch’(32 b) msecs(32 b)
2nd line = 1st 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
30CTP offline review
30CTP offline software status 08/04/2008
Cross section and Luminosity
)(tLdt
dN
T
dttLTN )()(
• 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)
http://epweb2.ph.bham.ac.uk/user/pedja/alice/::CTP preliminary design review; Cross section calculation
31CTP offline review
31CTP offline software status 08/04/2008
Trigger Class Logic and Counters
LX Trigger input Delayed Class L(X-1)
Class LX Trigger before vetoes
32 bits
Counter NXb
VME
32 bits
Counter NXa
VME
Class LX Trigger after vetoes
Class LX Trigger
LX Trigger Condition
LX Trigger Vetoes
50 circuits
X = [0,1,2]
Ldt
N
N
N
N
N b
a
b
a
bclass 0
0
1
1
2
• σclass - uncorrected cross section for class ‘class’• NXa,NXb – counters at level X=[0,1,2] before and after vetoes (see picture). Formula assumes counters are cleared at the beginning• L – luminosityhttp://epweb2.ph.bham.ac.uk/user/lietava/alice.html Offline procedure for the cross
Section calculation
32CTP offline review
32CTP offline software status 08/04/2008
L0 trigger input
Scaled-down BC
Random trigger
4
2
2
Look-up Table 16x1
(1 to 4)
Figure 3.9 Generation of Interaction signals
Sel
ecto
r
2 Select Interaction A
Interaction 1
L0 trigger input
Scaled-down BC
Random trigger
4
2
2
Look-up Table 16x1
(1 to 4)
Sel
ecto
r
2 Select Interaction B
Interaction 2
L0 trigger input 4 Look-up Table
16x1 (1 to 4)
Interaction Test
CTP Preliminary Design Review,http://www.ep.ph.bham.ac.uk/user/pedja/alice/
Interaction signals logic
2 interactions can be defined
Interaction: any logical function of 4 L0 inputs
33CTP offline review
33CTP offline software status 08/04/2008
CTP data to ESD
Trigger and cluster mask or classes in ‘normal’ language as in config file
34CTP offline review
34CTP offline software status 07/07/2008
Naming scheme for classes
• Scheme under discussion (for offline use):Scheme under discussion (for offline use):• C<descriptor code>-<bcm code>-<pf code>-<cluster code>-<rare flag>C<descriptor code>-<bcm code>-<pf code>-<cluster code>-<rare flag>• e.g.: e.g.:
C0SH1-B-NOPF-ALL-RC0SH1-B-NOPF-ALL-R
3434
BX mask code
PF protection code
cluster code
rare class flag
descriptor code
35CTP offline review
35CTP 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, CTP: Ivan Kralik• Tested in ACR• Dim interface to DCS lum mon