1 / 23

CTP offline meeting 16/03/2009

CTP offline meeting 16/03/2009. A.Jusko and R.Lietava. Outlook. News relative to January review: Naming Convention Trigger inputs - CTP readout Counters for Cross section Interaction record. Naming scheme. Proposal discussed with trigger and offline prepared by F.Antinori,

jackie
Download Presentation

CTP offline meeting 16/03/2009

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CTP offline meeting16/03/2009 A.Jusko and R.Lietava CTP offline review

  2. Outlook News relative to January review: Naming Convention Trigger inputs - CTP readout Counters for Cross section Interaction record CTP 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) CTP 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 CTP 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) CTP 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 CTP 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 CTP 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 CTP 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 CTP 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 CTP offline review

  11. Back up CTP offline review

  12. Configuration: Load/Start of Run ECS TRIG DB LoadPartition(name.cfg) rxxxx.rcfg CTP proxy rxxxx.rcfg DAQ logbook CTP offline review

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

  14. Counters: Start of Run xsec DIM client ECS Open file (<7) STARTPartition(runnum) CTP DIM server CTP proxy Start counters CTP offline review CTP offline software status

  15. Counters: End of Run xsec DIM client ECS Close file STOPPartition(runnum) DCS FXS CTP DIM server CTP proxy Stop counters Shuttle OCDB CTP offline review CTP offline software status

  16. alidcscom026 xcounters DAQlog .partition .cnts alidcsvme001 3 parted Pydim (parted) .pcfg ctpdims 2 1 4 .rcfg ctpproxy htmlctpBusy DAQ DB .html File r/w DIM messages DIMcmnd: SOR/EOR, CalTrig requests DIMcmnd: Load/Stop partition DIMservice: once per min. +SOR/EOR DAQDB update by ctpproxy

  17. 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 CTP offline review CTP offline software status

  18. 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) http://epweb2.ph.bham.ac.uk/user/pedja/alice/::CTP preliminary design review; Cross section calculation CTP offline review CTP offline software status

  19. Trigger Class Logic and Counters • σ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 – luminosity http://epweb2.ph.bham.ac.uk/user/lietava/alice.html Offline procedure for the cross Section calculation CTP offline review CTP offline software status

  20. Interaction signals logic • 2 interactions can be defined • Interaction: any logical function of 4 L0 inputs CTP Preliminary Design Review, http://www.ep.ph.bham.ac.uk/user/pedja/alice/ CTP offline review CTP offline software status

  21. CTP data to ESD Trigger and cluster mask or classes in ‘normal’ language as in config file CTP offline review CTP offline software status

  22. Naming scheme for classes rare class flag BX mask code cluster code PF protection code descriptor code CTP offline review CTP offline software status • Scheme under discussion (for offline use): • C<descriptor code>-<bcm code>-<pf code>-<cluster code>-<rare flag> • e.g.: C0SH1-B-NOPF-ALL-R 22

  23. 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 07/07/2008 CTP offline review CTP offline software status

More Related