15 May 2012NA61 Collaboration Meeting, Budapest1 Shine: status and plans András László, for the Shine Group

15 May 2012NA61 Collaboration Meeting, Budapest2 Reminder: large-scale structure of Shine software ● Detector: Interface to detector parameters. Geometry setup, calibration parameters. Hardcoded data, or it can ask also Managers to retrieve data. ● Event: Describes the data content of a physical event. Different abstraction levels are possible (main parts: BOSRecord, RawEvent, RecEvent, ProcEvent, SimEvent). ● Modules: These are the substeps of the calibration and reconstruction process. Can only propagate information via Event. Can get detector related description only from Detector. ● Large part of the modules are wrapped NA49 'legacy clients'. These need occasionally extra treatment. ● EventBrowser: RawEvent, RecEvent and SimEvent visualization tool. ● Further standalone applications: t0calibration etc. Code under: trunk/Shine First order dependencies automatically fetched by: trunk/Shape Instructions: on NA61 twiki

15 May 2012NA61 Collaboration Meeting, Budapest3 Detector ● Summary: Reads and provides description of subsystems. TPC, TOF, BPD, PSD, Beam, Magnetic Field, DAQ channel remapping. ● Development since last collab meeting: ● DAQ channel remapping collected in one place, includes now TPC and Trigger related channel reshuffling, but not yet WFA and MHTDC. ● TPC geometry description separated from DAQ channel reshuffing. ● Magnetic field is given to legacy clients via wrapped Shine Detector (validated). ● Finalized PSD detector description. Prepared TOF description. ● Prototype for calibration constants (drift velocity, temperatures). ● To be done: ● Move dynamic channel reshuffling of WFA and MHTDC to DAQ. ● Master config files for multi-part detectors (TPC, TOF), ROOT format. ● Accomodate some stuff: TPC T0 correction, TPC Gain correction etc. ● Write 'padtrans' library with wrapped Shine Detector.

15 May 2012NA61 Collaboration Meeting, Budapest4 Detector related issues in legacy code ● Summary: Need to provide calibration information for legacy clients. ● Development since last collab meeting: ● Collection of all legacy calibration files under DB package. Automatic fetching via Shape as a dependency. ● Loading of all used calibration files into DSPACK memory based on a run period lookup table (CalibrationFileHandler module). This replaces HEPDB mechanism (but as black box). ● Native calibration handler mechanisms in Shine Detector (e.g. v d ). ● To be done: ● Further native calibration handler mechanisms in Shine Detector. ● Propagate this native Detector information to legacy clients: – With function wrappers around Detector (padtrans, like magfld). – With pushing these Detector info to DSPACK memory (e.g. with CalibrationHandler). ● Finally, get rid of legacy calibration files in the end.

15 May 2012NA61 Collaboration Meeting, Budapest5 Event ● Summary: Can store BOS data, Raw data, Proc data, Rec data, Sim data for a physical event. Main idea (Rec): flat containers of Clusters, Tracks, Vertices, laced via their relations. Also referred to as SHOE. ● Development since last collab meeting: ● Better EventIO for BOS data. ● More robust BOS →Raw conversion via Detector::DAQ. ● New cathegory ProcEvent for volatile event info between modules. ● Finalized RecEvent and NA49 → RecEvent conversion. ● Finalized PSD RawEvent. ● To be done: ● Accomodate remaining tiny stuff in RawEvent: TPC Clock Phase etc. ● Write PSD RecEvent. ● Finetunes to SHOE.

15 May 2012NA61 Collaboration Meeting, Budapest6 Modules ● Summary: Substeps of calibration and reconstruction procedure. Also there are wrapped 'NA49 legacy client' Modules. ● Development since last collab meeting: ● New generic TPC cluster finder module (ported from LMPD rec code). ● LMPD track finder module (ported from LMPD rec code). ● Porting, correction and validation of wrapped 'NA49 legacy clients' (validated up to cluster finding – but with some issues). ● To be done: ● Write PSD reconstruction module. ● Rewrite simpler clients as Shine module? (Maybe easier than port.) ● Write/finalize simulation legacy client / module. ● Continue correction and validation of wrapped 'NA49 legacy clients'.

15 May 2012NA61 Collaboration Meeting, Budapest7 Module related issues in legacy code ● Summary: The most important modules are wrapped 'NA49 legacy clients'. ● Development since last collab meeting: ● All the clients are ported to Shine and wrapped, so that one can call them as modules. ● Correction of programmetical mistakes up to cluster finding. ● Validation up to cluster finding – but recently some issues turned up. ● To be done: ● Go further in the rec chain with validation and subsequent mistake corrections. ← This is an extremely painstaking job.

15 May 2012NA61 Collaboration Meeting, Budapest8 EventBrowser ● Summary: RawEvent, RecEvent and SimEvent visualization application. Shipped with the Shine framework. ● Development since last collab meeting: ● Better connection philosophy to DAQ server for post-mortem inspection. ● WFA, MHTDC displays. ● Forward – backward stepping in event stream. ● Many further finetunes. ● To be done: ● Change RawEvent display data containers to THPoly. This would make easier the accomodation of non-box detectors (LMPD, TOF-s etc).

15 May 2012NA61 Collaboration Meeting, Budapest9 Other standalone applications ● Summary: some applications heavily using external dependencies may be not written as a Shine module, but as a standalone program, using Shine as an external library. ● Development since last collab meeting: ● Ported t0calibration program, now using Shine (under trunk/Shine/Applications/Calibration/t0calibration). Calculates pad-py-pad T0 shifts and gain factors based on pulser calibration data. ● To be done: ● Port further such programs.

10 Status of components

15 May 2012NA61 Collaboration Meeting, Budapest11 Where one can help? ● Fill the XML table of TriggerChannelMapping and keep it up-to-date – this is the run- period dependent reshuffling of trigger related detectors in data (for Trigger expert, with help of Shine devels). ● Organize your calibration files in your NA49 legacy clients. Collect them systematically like e.g. under trunk/DB/myclient directory and refer to this path via an environmental variable. Help to port calib info to Shine Detector. ● Use analysis codes based on SHOE event stuctures. ● Write new modules in the new framework for new detectors. ● Organize calibration data in the new framework for your modules in a systematic way (asking through Detector, files under DB). ● Optimize for use of combined Shine module + NA49 legacy client based reconstruction chain. ● Ask question if you want to accomodate new stuff.

15 May 2012NA61 Collaboration Meeting, Budapest12 Thank you!