1 / 8

Production status

Production status . Reconstruction team for 2009 - present data collected Maja Katarzyna Mackowiak- Pawlowska Dag Larsen Dimitrije Maletic Latest production was the BeBE 2011 runs processing. We are not having any significant problems with running the production at the moment. .

ira
Télécharger la présentation

Production status

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. Production status • Reconstruction team for 2009 - present data collected • MajaKatarzynaMackowiak-Pawlowska • Dag Larsen • Dimitrije Maletic • Latest production was the BeBE 2011 runs processing. • We are not having any significant problems with running the production at the moment.

  2. Production’s team assignment • - When there is a need for processing of some reaction, the Test production of one run is done, and checked by experts; • Alex – alignment,Antoni – vdrift, Szymon- dE/dx • We then proceed with production of remaining runs, and look over the running jobs. When the production is done and checked for various of errors the twiki is updated and the production is ready to be used by collaboration. • https://twiki.cern.ch/twiki/bin/viewauth/NA61/WebHome

  3. Stored data Version of the software: v12g Global database key Runs processed, you may also check the book keeping system page About additional information about runs storage

  4. Problems we run into - technical • Castor issues are present, but in much smaller scale then before. • The big improvement was the switching the users to default castor pool, and keeping production on na61 disk pool (with inclusion of garbage collection option). Production got more free disk space, and besides that this way we don’t spep on anybodies toes by demanding to clean user files from a castor pool for production reasons. • We now just observe, for a breef period of time, the castor in-responsivness, which doesn't create long delay in finishing up the production.

  5. Problems we run into - organizational • The need for clear procedure about SHOE log files - In the beginning of the inclusion of SHOE and mini-shoe conversion from ds files, the log files contaned very much of information. We were trying to have smaller log files and we were ignoring some part of log files. • We need to go over this issue with SNINE software team, in order to store good log files. • The creation of mini-shoe files for whole runs -The creation of single mini-shoe file for most runs is possible. For runs with many chunks, the lsf is complaining about usage of resources and fails the creaton of tne mini-shoe file. Those runs had to have several mini-shoe files. The way to continue with creation of mini-shoe files for whole runs should be discussed also with the SHINE software team.

  6. To be done • To follow the updates on PSD inclusions into the SHOE and mini-shoe files • To go over the scripts for SHOE and mini-shoe conversion • To go over Dag’s script for automated validation of reconstruction outputs

  7. Thank you!

More Related