1CTP offline review
1
CTP offline meeting16/03/2009
A.Jusko and R.Lietava
2CTP offline review
2
Outlook
• News relative to January review:• Naming Convention• Trigger inputs - CTP readout• Counters for Cross section• Interaction record
3CTP offline review
3
Naming scheme
• Proposal discussed with trigger and offline prepared by F.Antinori, see: http://aliceinfo.cern.ch/Offline/Activities/TriggerConvention/index.html• Scheme discussed again in January, basic concept of fixed class names stays • Tuning continues – look for news from Federico A, offline (Cvetan), trigger (Anton)
4CTP offline review
4
CTP Configuration file
• At the beginning of run send to OCDB
- via DAQ logbook
- via DCS FXS (removed in the latest version)• Compatible with new general ECS scheme
5CTP offline review
5
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)
6CTP offline review
6
xCounters data
• 6 counters per Trigger class necessary for cross section
• Counters read viaVME at CTP CPU ( not part of ‘normal’ data flow)
• Data flow:
- CTP -> DCS FXS ->SHUTTLE->OCDB
7CTP offline review
7
xCounters: pending issues
– Check the consistency of collected data – in progress (Plamen)
– Propagate them to ESD/AOD (in progress Plamen/Cvetan)
• Spline fit in AliESDRun
• Or extrapolated values for each event/ESD
• Improve error managment
8CTP offline review
8
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
9CTP offline review
9
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
10CTP offline review
10
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
11CTP offline review
11
Back up
12CTP offline review
12
Configuration: Load/Start of Run
ECS
TRIGDB
CTPproxy
LoadPartition(name.cfg)
DAQ logbook
rxxxx.rcfg
rxxxx.rcfg
13CTP offline review
13CTP offline software status 08/04/2008
Configuration: End of Run
OCDB
DCS FXS
SHUTTLE
TRIGDBECS
CTPproxy
STOPPartition(runnum)
CTPDIM
server
xsecDIMclient
Stoprun
rxxxx.rcfg
14CTP offline review
14CTP offline software status 08/04/2008
Counters: Start of Run
ECS
CTPproxy
STARTPartition(runnum)
Open file (<7)
CTPDIM
server
xsecDIMclient
Startcounters
15CTP offline review
15CTP offline software status 08/04/2008
Counters: End of Run
ECS
DCS FXS
CTPproxy
STOPPartition(runnum)
Close file
CTPDIM
server
xsecDIMclient
Stopcounters Shuttle
OCDB
16CTP offline review
16
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
17CTP offline review
17CTP 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
18CTP offline review
18CTP 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
19CTP offline review
19CTP 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
20CTP offline review
20CTP 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
21CTP offline review
21CTP offline software status 08/04/2008
CTP data to ESD
Trigger and cluster mask or classes in ‘normal’ language as in config file
22CTP offline review
22CTP 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
2222
BX mask code
PF protection code
cluster code
rare class flag
descriptor code
23CTP offline review
23CTP 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