1 / 4

Addressing Trigger Configuration Issues in PbPb 2011 Run: Solutions & Challenges

In the online meeting held on January 30, 2011, M. Floris and J.F. Grosse-Oetringhaus discussed critical issues with the trigger configuration during the PbPb 2011 run. Frequent changes to trigger class names hindered data propagation from the trunk to the ALIROOT version used for Quality Assurance (QA)/AOD. Key problems revolved around the OADB configuration and its impact on data processing. Suggestions for fixes included utilizing custom configurations and the necessity of backward compatibility. Local tests showed success, yet grid job failures raised concerns about memory consumption.

lani-cardenas
Télécharger la présentation

Addressing Trigger Configuration Issues in PbPb 2011 Run: Solutions & Challenges

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. Physics selection: online changes & QA • M Floris, JFGrosse-Oetringhaus • Weekly offline meeting • 30/01/2011

  2. The problem • PbPb 2011 run  frequent changes of trigger configuration (trigger class names, offline selection...) • Did not propagate quickly enough from the trunk to the aliroot version used for the QA/AOD (i.e. the release) • The main issue is related to trigger class names (no name  no data) • The configuration is written in the OADB • Possible solutions: • Use a custom configuration in the QA macros (by hand) • OADB on alien, path containing rev number, path given on JDL • QA with analysis tag (one may need 1 tag/day + additional delays) Preferred https://savannah.cern.ch/bugs/?89170 Alice Physics Forum

  3. OADB on alien • Path contains the rev number, it’s written in JDL: • SplitArguments = {"/alice/…/#alienfilename# alien:////…/oadb_rev12345"}; • OADB size: ~ 29 MB (and counting), 80% centrality calibration • What it solves: • New trigger class names, improved selection with already existing cuts • Improved centrality calibration • What it does not solve: • An unforeseen selection cut is needed: this requires changing the classes (e.g. in 2010 we realized in the middle of the run that parasitic collisions could be rejected with ZDC) • Backward compatibility: if a new selection/calibration is implemented, this can in principle affect earlier runs (reprocessing old runs with the new OADB may change them) • If a class in OADB changes in the trunk, the new OADB may not be compatible with the rev (can be solved by policy) Alice Physics Forum

  4. Status • Local test successful (reading from Grid, as on a WN) • Job sent on the grid failed (all subjobs either expired or went into EIB) • Forensics (Latchezar): “jobs which ran killed for high memory consumption” • Local test w/ valgrind: no issue spotted • We believe this is not related to OADB • Request: make a full test on a run which was already reconstructed in the standard production • “The tests can be run after we finish with the Pb processing.” • Comments? Suggestions? Conclusions? Alice Physics Forum

More Related