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 maintenanceMake sure all reconstructed runs are completeMake sure bad runs flagged and reconstructed files deleted

Close holes in data reconstruction and DST coverageDST file size problem = 1 week of scripting work

MC production for 2004-2005

Reprocessing of various data setsMost critical may be 2004 data with bad wire mapsNeed to define other data sets to reprocess

Re-reconstruction of 2001/2002 MC sampleStill interested? 30 pb–1? More?

L dt (pb–1)

tag 100

2001 169

2002 292

2004 691

2005 1242

total 2394

Reconstruction of 2004-2005 data

0 500 1000 1500 2000

drn/drc

d3p

dk0

dkc

recon

tag 100

raw

1930

1740

1970

1000

1490

1530

1490

pb–1

Runs 28700 (9 May 04) to 41902 (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 2004-2005

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 2004-2005 reconstruction

• Script modifications to handle big DSTs

Incomplete reconstruction 2001-2002

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 2004-2005 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 = 1019.4 MeV• All scan data, small part of 1000 MeV data• 342 runs total

Reconstructed KLOE data

DBV 2001 2002 2004 2005 Scan Comment

12-15 161 34Bad cut in FILFONo bias sample for FILFONo bias sample for rad

19-21634bad

wires!

225Various significant ECL modsMinor changes to reconNo bias sample for rad

22 236 394Stable ECLOld bias sample for rad

23-24 13 499 61Stable ECL for s = m

ufo as bias sample

25 203Stable ECL for off-peakufo as bias sample

analyzed 161 283 634 1118

total 168 289 687 1237

Monte Carlo tests

First production test 2 Nov:25 pb–1 all_phys, LSF = 0.2 (Runs 37000-37200)VERT banks corrupted, 1/4 endcaps missing!

Second production test 25 Nov:Problems with VERT banks, endcaps fixedSame sample as first test - not enough eventsTiming problem for EmC background

Third (“preproduction”) test 20 Feb - 13 Mar:100 pb–1 all_phys, LSF = 0.2 (Runs 39000-39600)• 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

Item Develop Implement

New IR geometry CB CB

Attenuation lengths in EmC endcaps PG CB MM

2002 EmC time resolution adjustments CG MM

2002 cluster efficiency parameters MP TS MM

Nuclear interactions/regeneration CB CB

New secondary decay generators Various CB

LSB (background) insertion MM MM

SQZ (compression) fix MM

Cell/cluster index fix MM

dE/dx simulation VP MM

Confirm/check status of these itemsItem Develop Implement

2004 data quality scan (√s, etc) GV

2004 trigger: quality, DC thresh, DISH maps MP BS

2005 trigger: quality, DC thresh, DISH maps MP BS

2005 data quality scan (√s, etc) GV

Check lsb background insertion MM MP

Check EmC energy scale calibration PG

Check EmC time resolution parameters CG

Check cluster efficiency parameters TS

Correlated noise for charged kaons EDL PDS

dE/dx calibrations VP RV

New generators ee ee0 CG RV, ADS

Check generator KSee CG

Monte Carlo production plans

2001-2002

450 pb-1

2004-2005

2000 pb-1

1.85G evts

8800 B80 days

8.25G evts

39000 B80 days

Averaged over entire MC sample: 0.21M evts/B80 day = 2.4 Hz0.41 s/evt (simulation + reconstruction + DST)

all, scale = 0.2KSKL, scale = 1

KK, scale = 1 radiative, scale = 5Other (1M evts/pb-1)

Total: 3.1M evts/pb-1

(about same as number of decays in data)

2001-2002 MC production Estimated time for 2004-2005 MC

Offline resources: CPU

Nodes CPUs Type B80 CPUs

fibm14-15,17-34 80 P3 80

fibm35-44 40 P4+ 96

fibm45-47 “96” P5 198

All 374

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 estimateReconstruction 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 testDH 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 projects B80 days

Online reconstruction of 2006 data 3000

Reprocessing of 2004 data 16000

MC production for 2004-2005 data 39000

Reprocessing 01-02 data 5000

Reprocessing 02-04-05 DBV<23 22000

Minimum total 58000

Maximum total 85000

Up to ~300 B80 available for offline, leaving 80 to users283 days of offline work iff CPU (and not DH) limiting factor

Impact of DH problems

Nodes CPUs Type B80 CPUs Effective B80

fibm14-15,17-34 80 P3 80 65

fibm35-44 40 P4+ 96 64

fibm45-47 “96” P5 198 135

All 374 264

From a timing analysis of past production and 100 pb-1 test:tCPU(MC) = 210 B80 ms, tCPU(rec) = 180 B80 mstDH = negligible in past, tDH = 90 ms now

Assumes tDH 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 offline425 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 cacheGenerally, 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?