MC/Offline Planning M. Moulson Frascati, 21 March 2005 MC status Reconstruction coverage and data quality Running time estimates MC & reprocessing production plans

Offline/MC tasks for 2006 Reconstruction of 2006 data (√ s = 1000 MeV) Data quality and database maintenance Make sure all reconstructed runs are complete Make sure bad runs flagged and reconstructed files deleted Close holes in data reconstruction and DST coverage DST file size problem = 1 week of scripting work MC production for Reprocessing of various data sets Most critical may be 2004 data with bad wire maps Need to define other data sets to reprocess Re-reconstruction of 2001/2002 MC sample Still interested? 30 pb –1 ? More?

 L dt (pb –1 ) tag total2394 Reconstruction of data pb –1 Runs (9 May 04) to (5 Dec 05) Updated to reflect DB work 21 Mar 06

Check of reconstruction coverage 1.Ensure that no reconstructed files or DSTs present for runs flagged bad 2.Review runs with no vote in run_logger: 1828 runs/11.8 pb -1 generally due to DAQ crashes 112 runs/11.6 pb -1 with integrated luminosity > 20 nb -1 Check logbook for these runs and vote accordingly 3.Ensure reconstruction complete for each run and DBV

Incomplete reconstruction For each run and DBV: 1.Require all raw files have corresponding kpm, ksl, rpi, rad, clb, bha, and lsb files 2.Entire reconstruction for this DBV deleted if any files missing, together with any DSTs 3.Database record deleted, as if run were never reconstructed 4.Reconstruction pass with latest versions to close holes Separate DST pass to close holes once we have: Complete reconstruction Script modifications to handle big DSTs

Incomplete reconstruction More complicated! Data have already been analyzed bgg files were made from bha files - DB2 dependences Many bha files have been deleted Can only delete files - not DB2 records Suggested procedure 1.Reprocess as needed 2.Handle completeness of reprocessed data set as in case of data (except for bgg files) 3.Delete files (not DB2 records) for previous DBVs 4.Make sure older DSTs were based on complete reconstruction, otherwise delete (should not happen)

Other maintenance 1.Several runs reconstructed with incorrect DBV in DB2: 68 runs reconstructed with DBV-21 recorded as DBV-20 4 runs reconstructed with DBV-25 recorded as DBV-24 All deleted - easier to reprocess than to update all DB2 tables 2.Delete off-peak runs reconstructed with DBV-24 Track mass evaluation in EvCl assumes √s = MeV All scan data, small part of 1000 MeV data 342 runs total

Reconstructed KLOE data DBV ScanComment Bad cut in FILFO No bias sample for FILFO No bias sample for rad bad wires ! 225 Various significant ECL mods Minor changes to recon No bias sample for rad Stable ECL Old bias sample for rad Stable ECL for  s = m f ufo as bias sample Stable ECL for off-peak ufo as bias sample analyzed total

Monte Carlo tests First production test 2 Nov: 25 pb –1 all_phys, LSF = 0.2 (Runs ) VERT banks corrupted, 1/4 endcaps missing! Second production test 25 Nov: Problems with VERT banks, endcaps fixed Same sample as first test - not enough events Timing problem for EmC background Third (“preproduction”) test 20 Feb - 13 Mar: 100 pb –1 all_phys, LSF = 0.2 (Runs ) Test new cluster efficiency parameters Test new EmC time resolution parameters Additional EmC studies on energy scale calibration Other additions and modifications added to test

Items we feel good about ItemDevelopImplement New IR geometryCB Attenuation lengths in EmC endcapsPGCB MM 2002 EmC time resolution adjustmentsCGMM 2002 cluster efficiency parametersMP TSMM Nuclear interactions/regenerationCB New secondary decay generatorsVariousCB LSB (background) insertionMM SQZ (compression) fixMM Cell/cluster index fixMM dE/dx simulationVPMM

Confirm/check status of these items ItemDevelopImplement 2004 data quality scan (√ s, etc)GV 2004 trigger: quality, DC thresh, DISH mapsMP BS 2005 trigger: quality, DC thresh, DISH mapsMP BS 2005 data quality scan (√ s, etc)GV Check lsb background insertionMM MP Check EmC energy scale calibrationPG Check EmC time resolution parametersCG Check cluster efficiency parametersTS Correlated noise for charged kaonsEDL PDS dE/dx calibrationsVP RV New generators h  p + p - e + e -, e + e -  wp 0 CG RV, ADS Check generator K S  p + p - e + e - CG

Monte Carlo production plans pb pb G evts 8800 B80 days 8.25G evts B80 days Averaged over entire MC sample: 0.21M evts/B80 day = 2.4 Hz 0.41 s/evt (simulation + reconstruction + DST) f  all, scale = 0.2 K S K L, 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) MC production Estimated time for MC

Offline resources: CPU NodesCPUsTypeB80 CPUs fibm14-15, P380 fibm P4+96 fibm45-47“96”P5198 All374 Notes: 1 “B80” CPU = 1 Power3 375 MHz installed in B80 server 1 P4+ CPU = 2.4 B80 CPU (scaling GEANFI execution time) Fairly well-known estimate Reconstruction runs even faster than GEANFI on P4+ iff DH smooth 1 P5 “CPU” = 0.86 P4+ CPU (GEANFI, 100 pb -1 production test) Less well known: many issues during production test DH in bad shape, other processes competing for P4+ time? Use old P4+ numbers, results consistent with PS & FF 1-Feb-06

Offline CPU needs 2006 offline projectsB80 days Online reconstruction of 2006 data3000 Reprocessing of 2004 data16000 MC production for data39000 Reprocessing data5000 Reprocessing DBV< Minimum total58000 Maximum total85000 Up to ~300 B80 available for offline, leaving 80 to users 283 days of offline work iff CPU (and not DH) limiting factor

Impact of DH problems NodesCPUsTypeB80 CPUsEffective B80 fibm14-15, P38065 fibm P fibm45-47“96”P All From a timing analysis of past production and 100 pb -1 test: t CPU (MC) = 210 B80 ms, t CPU (rec) = 180 B80 ms t DH = negligible in past, t DH = 90 ms now Assumes t DH doesn’t get any worse when we use more CPUs! 54 slots ~100 B80 for 100 pb -1 test + online reconstruction running Maintaining 80 B80 for users leaves 200 B80 for offline 425 days (instead of 283 days)

Various issues (HepDB & DB2) Missing MC entries in C1 calibration database (HepDB) DC - all calibration banks EMC - CCAV, QCAV banks Patch applied in RTPATH: For MC, always access CN database HepDB to DB2 migration! (FS) Are all calibrations in their final state? Need to copy dead/hot wire maps and efficiencies from test table to final table Need to get all bgg and lsb files into disk cache Generally, review selection of file types maintained on disk

Questions 1.What work needs to be completed before MC production starts? 2.Do we need any further MC production testing? 3.How many CPUs do we use for MC/reprocessing 4.What data do we reprocess first? 5.What can we do to improve DH system performance? 6.Do we start the HepDB to DB2 migration now?