1 / 10

Offline running plans

Offline running plans. M. Moulson, 31 March 2004. Outline: Organizational issues MC status update Reconstruction: things to do for restart kpm streaming FILFO. Organizational issues. Graziano Venanzoni is new offline co-convenor effective at end of ppg paper (est. mid-April).

lance
Télécharger la présentation

Offline running plans

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. Offline running plans M. Moulson, 31 March 2004 • Outline: • Organizational issues • MC status update • Reconstruction: things to do for restart • kpm streaming • FILFO

  2. Organizational issues Graziano Venanzoni is new offline co-convenor effective at end of ppg paper (est. mid-April) Simona Giovannella is technical understudy (non-active role but ready to help in solving problems)

  3. MC production status • Problems with radiative K decays • precision problems • ordering of secondaries in K0e3 decays • New generators: K0  p+p-p0g, K+  p+p0p0g • Problem in all_phys card (affects DBV-17) • Both f  rp (including direct) and f  3p (direct) enabled • rad04 production run twice • 1st production: e+e-  wp0, p0 not simulated unless w  p0g • All problems fixed • rad04 rerun • all_phys currently running

  4. Other MC issues • New machines • Same geanfi executable, in principle no problems • However, should be considered two different platforms • All new productions (rad04, all_phys): • 25000-25999 new machines only • 26000-26499 old machines only • Other runs by luck of the draw • Tape space • 36 TB of library reserved for MC, ~24 currently used • When can I delete DBV-17? • Can we delete pre-mcprod MC?

  5. Plans & priorities • all_phys, 260M evts (running) 13 days • all_scan (all_phys off peak LSF=1), ~60M evts 3 days • neu_kaon, 410M evts 21 days • eeg100 (e+e-g, Eg > 100 MeV), 32M evts 2 days • Clear that we will conflict with restart of data taking • Not a big problem, one possible solution: • Old machines: MC • New machines: Reconstruction • Lengthens MC production time

  6. 1 – 28000 1 – 28000 1 - 99999 //cdcn/calibration/ //cdrn/run_cond/ //cdgy/geometry/ cn CALI rn RUNC gy GEOM c1 CALI r1 RUNC //cdc1/calibration/ //cdr1/run_cond/ 28001 - 99999 28001 - 99999 HepDB database upgrade (P. de Simone) Validity range PathName DBindex, DBname RTPATH routine selects the correct DB (index & pathname) based on run number and DB name: OLD: RTPATH(DBindex, BankName, PathName) NEW: RTPATH(RunN, DBname, BankName, DBindex, PathName )

  7. HepDB database upgrade (P. de Simone) • 2 new DBs have been created : rtcal_1_v2.rz (c1) • rtrnc_1_v2.rz (r1) • Done: RTDB library routines updated (in development area) • Done: Utilities to write/read the DBs for DC updated • EmC: dbload, other objects (?) still need update (EmC group) • In progress: All other routines in offline library that call RTPATH need updating

  8. Reconstruction upgrades • DC wire sags in tracking code— AA, SdA, MM • Adjust thickness of DC wall (-75 mm) in RTDB • Particular attention to backwards compatibility with MC • Medium-term plan is to re-reconstruct a significant fraction of old data • Do NOT want to pick up above changes since this would require re-reconstructing MC as well • May also want to continue MC production for old data with new executable • Hard cut on run number in ATFMOD and DCDBINI for both data and MC?

  9. Luminosity-scaling background trigger • Implement 20 Hz of random triggers in TORTA card • Generate test file • Decide how to implement luminosity scaling: • selection: stream one lsb to file event every N VLABs (LABs?) • insertion: stream all lsb events w/ n = number of intervening VLABs; insert only events with n > N • Modify ECLMOD to write lsb files • Modify INSERT to use lsb files (if scaling on insertion) • Modify MCPROD to use lsb files instead of bgg files • Attention to issues of backwards compatibility MM

  10. Miscellaneous streaming issues • dE/dx and DCDEDX A/C module: — MM, VP • Include DCDEDX in datarec path before streaming • Include DEID bank in DSTs • Event classification and streaming: • kpm — VP, BS • eliminate old tagging algorithms • dE/dx based tag • ksl: eliminate KSTAG algorithm— MM • rad: downscaled sample with less stringent cuts — FA, CdD • clb: various bug fixes — TS, MA

More Related