1 / 19

Offline/MC status report

Offline/MC status report. M. Moulson 6th KLOE Physics Workshop Sabaudia, 10-13 May 2006. Offline/MC tasks for 2006. Define definitive KLOE data set: Close holes in data reconstruction and DST coverage DST file size problem Make sure all reconstructed runs are complete

jovita
Download Presentation

Offline/MC status report

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/MC status report M. Moulson 6th KLOE Physics Workshop Sabaudia, 10-13 May 2006

  2. Offline/MC tasks for 2006 • Define definitive KLOE data set: • Close holes in data reconstruction and DST coverage • DST file size problem • Make sure all reconstructed runs are complete • Reprocessing of various data sets • Most critical is 2004 data with bad wire maps • Data quality • Completeness of HepDB entries for MC production • Fine survey for analysis purposes • MC production for 2004-2005 • Re-reconstruction of 2001/2002 MC sample? • Requested by K group - problem of bad wire maps

  3. Reconstruction of 2004-2005 data Updated to reflect DB work 21 Mar 06 Runs 28700 (9 May 04) to 41902 (5 Dec 05) 1970 1930 1740 990 1480 1520 1480 pb–1

  4. DST size problem 32-bit I/O pointers in Fortran: Maximum file size = 2 GB There may be a workaround (esp. for reading w/ KID) but not easy! • Big headache! • Max sizes difficult to calculate: • Fluctuating background components • 10% for most streams • 33% for dkc/mkc • MC numbers assume: • Full cross section for stream • Size refers to scaled luminosity • Need to split DSTs into pieces • 100 nb-1 chunks • Must modify scripts • Working on DST standalone script to plug holes What does 2 GB limit mean? Max size (nb-1)

  5. Reconstructed KLOE data trgmon luminosity in pb-1 by year and DBV 645 pb-1 to be reprocessed for sure,278 pb-1(617 pb-1) as time permits

  6. Notes on reprocessing • Reprocessing most critical for 2004 data with bad wire maps • Reprocess 2004 data first • Other reprocessing priorities can be decided upon afterwards • When data are reprocessed, old reconstructed files will be deleted: • If data have already been used for analysis (e.g. 2001-2002 data): • files deleted, database record and old DSTs will be kept. • If data have not been used for analysis (e.g. 2004-2005 data): • database record and DSTs deleted, as if run had never been reconstructed in the first place. • Basically same treatment planned for incomplete runs in data set • Off-peak data reconstructed w/ DBV-24 need reprocessing for ppg use • 61 pb-1: all scan data, small amount of s = 1000 MeV data • Keep current files until ready to start reprocessing • Plan: Start 2004 reprocessing and 2005 MC production in parallel • If there are problems with DH-induced latency, hold reprocessing until additional disk space for the I/O cache arrives (it is expected in June).

  7. MC development items

  8. MC sign-off: Data quality & DB issues Data-quality parameters & DB loading Not to be confused with fine survey for analysis (S. Fiore) • 2004 run parameters (s, pf, etc.) already loaded into HepDB • 2005 run parameters obtained, need to be loaded • Trigger parameters in DB2 for 2004 & 2005 • Cluster efficiency, time resolution parameters updated • Dead/hot wire maps, DC efficiencies: need to unify tables HepDB-to-DB2 migration? F. Sborzacchi has developed: • DB2 tables to contain data currently in HepDB: All detector calibration data Much run-condition information (s, pf, etc.) • Code to fill and maintain new tables • Interface code (drop-in replacements for HepDB calls) Ready to go (but wait until MC started?)

  9. Work on LSB background to deal with: • Inconsistent cluster/KINE matching • Timescale alignment for MC and data • Treatment of “noise” hits (missing tA or tB) Diagnose performance: t0rec-t0MC distribution KS  p+p-, KL crash events MC sign-off: LSB background KS  p0p0from MC,t0recfrom T0_FIND linear scale t0 from MC track KS  p+p-, KL crash t0true from p+p- mixed t0 • data • MC t0 from LSB cluster t0rec-t0true(ns) t0rec-t0MC(ns)

  10. MC sign-off: LSB background • LSB files look OK! • Overall prob. for LSB cluster to set t0 = 0.82(4)% • Roughly half will steal t0 in f event Compare to data and reconstructed MC (all_phys test runs): • Harder filtering of noise hits increases stolen t0 prob • Are we dropping LSB events w/ no clusters? • Before starting production, must check DC timescale alignment!

  11. MC sign-off: K± background • New A/C module (SIMKBCK) adds background hits correlated to K tracks • Sample distribution of K-correlated background hits in: • layer, distance (in wires) from reconstructed track, time Private reconstruction of ~20 pb-1 of 2002 MC events to study how new background parameterization affects MC tracking efficiency etrk+vtx as a function of t*(K±) + e(MC) + e(data) before after t*(K±) (ns) t*(K±) (ns) • Note: Large correction (5) for absolute probability of background hits: • Background measured using reconstructed tracks • Don’t account for tracks not reconstructed because of background

  12. MC sign-off: dE/dx simulation Calibration of A/C module (DIGIDCADC) to simulate dE/dx response of DC • DE distribution rescaled and smeared to match data • Different s-t relations for data/MC  effective integration gates different dE/dx distribution Truncated mean distribution Kp2 sample Kp2 sample • data • MC Km2 sample Km2 sample dE/dx (count/cm) dE/dx (count/cm) General note: • Difficulties in calibrating for space-charge effects undermine resolution • dE/dx resolution adequate for K ID, but not e.g. Ke2/Km2 separation

  13. Monte Carlo tests in 2006 All tests based on all_phys card, LSF = 0.2

  14. Monte Carlo production plans Averaged over entire MC sample: 0.21M evts/B80 day = 2.4 Hz 0.41 s/evt (simulation + reconstruction + DST) Estimated time for 2004-2005 MC 2001-2002 MC production f  all, scale = 0.2 KSKL, scale = 1 K+K-, scale = 1 f radiative, scale = 5 Other (1M evts/pb-1) Total: 3.1M evts/pb-1 (about same as number of f decays in data) f all, KSKL, K+K- campaigns to be combined: all_phys, LSF = 1.2 Start with 2005 data: Reprocessing not necessary for comparison

  15. Offline resources: CPU • 1 “B80 CPU” = 1 P3 CPU installed in B80 server - KLOE standard unit • Accuracy of estimates depends on B80/P4+ and B80/P5 ratios • “MC” results based on MC tests (all_phys, ‘05 data) 3-8 May 06: • 87 CPU (132 B80 “MC”) configuration - no competing offline work • No serious DH problems observed • Conventional wisdom (“CW”) based on past experience: • 1 P4+ = 2.4 B80 (compare 2.2 above) • 1 P5 = 0.8 P4+ = 1.9 B80 (compare 1.3 above)

  16. Offline CPU needs Assuming: 294 B80 total (MC test, not CW) 80 B80 left to users for analysis 214 B80 for offline 9-12 months if there are no serious DH problems

  17. Offline resources: Disk space DSTs cached on nfs-mounted disks for fast analysis access DST volume* *Updated to account for scan data • Current DST cache capacity: 12 TB • New purchases: 21 TB FC disk + new controller • Gara closed yesterday • Delivery by end of June? ~30 TB available for disk cache

  18. Offline resources: Tape space • Allocations include currently occupied space • MC DSTs probably appear as datarec files to archiver • Current library system capacity ~720 GB New cassettes will have to be ordered in future • Temporary allocation based on 720 GB library Assumes MC production slow • Final allocation assumes completion of KLOE offline program

  19. Outlook and summary • Starting MC production a very high priority, but we need to make a few last checks • We are planning for a near simultaneous start of • MC production, all_phys, LSF = 1.2, 2005 data • Reprocessing 2004 data with bad wire maps • We have the CPU power needed to generate a definitive MC sample and reprocess as necessary on a time scale compatible with beginning of 2007 • We will probably want to expand DST disk cache • We will need to order new cassettes towards the end of the year

More Related