Presentation is loading. Please wait.

Presentation is loading. Please wait.

OPERA Collaboration Meeting, Januray 2009 Status of OpEmuRec L.Chaussard 1) I/O and management of algorithms 2) Implementation of algorithms 3) Pending.

Similar presentations


Presentation on theme: "OPERA Collaboration Meeting, Januray 2009 Status of OpEmuRec L.Chaussard 1) I/O and management of algorithms 2) Implementation of algorithms 3) Pending."— Presentation transcript:

1 OPERA Collaboration Meeting, Januray 2009 Status of OpEmuRec L.Chaussard 1) I/O and management of algorithms 2) Implementation of algorithms 3) Pending issues

2 1) I/O and management of algorithms OpEmuIO: - the extraction of real data from the Oracle DB into ROOT TTree is working, no major difficulty, some (minor ?) problems are under investigation (e.g. loss of some long int format) OpemuRec: - the interface of ROOT I/O and algorithms works in a “single algo” mode, it means that one reconstruction job must be sent for each reconstruction step - the “multi algo” mode is under development, it will allow to run the full reconstruction chain in one job Implementation of algorithms in OpEmuRec (see next slide): - SySal - FEDRA OPERA Coll. Meeting – Jan.09

3 2) Implementation of algorithms OpEmuRec/SySal interface: - alpha-omega reconstruction is accessed through Mono, Cristiano wrote the interface between ROOT OpRData model and his Sysal model - alignment, filtering and tracking were ported and work successfully, vertexing has not been tested yet, this should be straightforward - the execution time is comparable to standalone Sysal running, the output is comparable to standalone SySal output at least on a statistical basis, deeper comparisons will be done OpemuRec/FEDRA interface: - FEDRA has been interfaced to CMT on CCIN2P3 as an “external” kit, Valeri will write the interface between ROOT OpRData model and his FEDRA model OPERA Coll. Meeting – Jan.09

4 3) Pending issues Evolution of the TTree manager: - we have one ROOT file per event, containing one TTree, each entry in this TTree is one view, with the TList of associated microtracks ; other TTrees are requested e.g. a TTree dedicated to alignment parameters, a TTree with one entry per track, a TTree with one entry per vertex, a TTree with one entry per shower, etc… - this implies to modify our EmulTreeManager object, and find the best implementation for cross-linking these TTrees, this could be done in principle in 2-3 weeks Shower description: - we have classes which describe microtracks, tracks, vertices, but no class for showers - we need to involve other people in the discussion in order to define this or these new class(es) (ECC WG, oscillation WG, …) OPERA Coll. Meeting – Jan.09


Download ppt "OPERA Collaboration Meeting, Januray 2009 Status of OpEmuRec L.Chaussard 1) I/O and management of algorithms 2) Implementation of algorithms 3) Pending."

Similar presentations


Ads by Google