hcal dpg in ls1

7
HCAL DPG in LS1 Olga Kodolova and Sunanda Banerjee

Upload: pepin

Post on 19-Jan-2016

40 views

Category:

Documents


0 download

DESCRIPTION

HCAL DPG in LS1. Olga Kodolova and Sunanda Banerjee. From Lucia. Re-reconstruction of data and simulated events The massive re- reco of all data (2.1 billions) is foreseen during 2013. - PowerPoint PPT Presentation

TRANSCRIPT

Page 1: HCAL DPG in LS1

HCAL DPG in LS1

Olga Kodolova and Sunanda Banerjee

Page 2: HCAL DPG in LS1

From Lucia

• Re-reconstruction of data and simulated events The massive re-reco of all data (2.1 billions) is foreseen during 2013. CMS also has “parked” data (1.2 billions which were not reconstructed during 2012 year but just kept at the mass storage). Part of the parked data (depending on the available resources) will be reconstructed in 2013-2014. (Requires certification?!)• Preparation for post-LS1 and post-LS2Samples will be produced assuming the capacity of 1B/month for MC digi–reco at Tier1 sites and 400M/month for MC Gen-SIM at Tier2 sites.

Page 3: HCAL DPG in LS1

5.1 Detector Performance

• 5.1 Detector Performance Tasks 5.1.2 Stability Monitoring and Tool developments (in 2012 – 12 months) 5.1.3 Prompt feedback (in 2012 - 30 m) 5.1.4 Shift tools dev/support (2012-30m) 5.1.5* Offline shifts (2012-24m) 5.1.6 Anomalous events filters (2012-24m)

Page 4: HCAL DPG in LS1

5.2 Monitoring and Data certification

• 5.2 Monitoring and data certification 5.2.2 Online DQM (2012-6m) 5.2.3 Offline DQM (2012-6m) 5.2.4 Data Certification (2012-6m)

Page 5: HCAL DPG in LS1

5.3 Database

• 5.3 Database 5.3.2 Online database (3m) 5.3.3 Offline database (6m) 5.3.4 Interface Tools (6m) 5.3.5 WBM infrastructure (4.8)

Page 6: HCAL DPG in LS1

5.4 CMS Software

• 5.4 CMS Software 5.4.2 Simulation, Geometry and Material model (6m) 5.4.3 Digitization (8.4) 5.4.4 Reconstruction (9.6) 5.4.5 Validation (9) 5.4.6 Upgrades: Reconstruction and simulation(2.4)

Page 7: HCAL DPG in LS1

5.5 Calibration and conditions

• 5.5 Calibration and conditions 5.5.2 Calibration methods (9) 5.5.3 Trigger, AlCaReco and Monitoring (12) 5.5.4 Conditions updates and Validation (12)

We have a real problem here-all our paths are strongly pre-scaled and we do not have enough events – should we report to management?