Alignment and Calibration Workflows in CMS

Complete: 1

Introduction

In this page we maintain a breakdown of computing-relevant characteristics of the alignment and calibration workflows in CMS.

Table of Alignment Workflows

Subdetector Workflow Facility CPU slots Storage Mem Events Frequency Time Comments
CAF disk AFS local scratch
Tracker Prompt alignment CAF 50 60 GB 20 GB 0 1 dedicated core with 16 GB 1M results daily 24h Running pixel/strips jobs
Full alignment CAF 50 60 GB 60 GB 0 1 dedicated core with 16 GB 5M running daily, results after 2-4 weeks 24h  
Monitoring, DQM CAF 5 2 GB 2 GB       Continuous 24h  
LAS alignment CAF 1 2 GB 2 GB 2 GB 1GB 10k daily <1h  
Muon Beam-halo/cosmics before 1st collisions CAF or private 1           Once    
1 pb-1 wheel/disk CAF or private 1           Once    
10 pb-1 globalMuon CAF 5 400 MB   1 GB 0.1M every 10 pb-1 10h  
100 pb-1 globalMuon CAF 50 400 MB   1 GB 1M every 100 pb-1 10h  

Table of Calibration Workflows

Subdetector Workflow Facility CPU slots Storage Mem Events Frequency Time Comments
CAF disk AFS Posix
ECAL $\pi^0$ HLT/CAF 20 100 GB 10 GB     100M/day daily <1d  
$\Phi$ symmetry HLT/CAF 50 10Gb 1Gb     100M/day up to 1G daily at startup 2-4 hrs  
W -> e $\nu$ , Z->ee             ? ?    
HCAL                    
...                    
Pixel tracker Lorentz Angle CAF                  
Gain CAF 40           when needed (>1d) 3 hours Very frequent at startup, weekly once stable. Data only collected when there is no beam (needs dedicated pulser run)
Strip tracker Lorentz Angle CAF 50 20 GB 10 GB     1M when needed (>1d) 5 hours can be every week
Gain CAF 50 20 GB 10 GB   3GB 1M when needed (>1d) 5 hours frequency will depend on stability... can be every week
Bad Components CAF 1 20 GB 10 GB   ~1.5 GB 100k ~daily 7 hours  
Muon DT ttrig calibration CAF 10 50 500   ? ~50000 each SL every 10 hours 6 hours  
vdrift calibration CAF 10 50 500   ? ~50000 each SL every 10 hours 6 hours  
t0 calibration CAF 1 10 20   ? ~5000 per wire once 3 hours  
noise calibration CAF 1 10 20   ? ~50000 per SL every 10 hours 3 hours  
Muon CSC                      
...                    
Muon RPC                      
...                    

Comments to fields:

Facility: CAF, HLT, Laserfarm, ...

CPU slots: number of CPU cores used in parallel

CAF disk: amount of storage needed in CAF disk pool (Castor)

Posix: amount of storage needed on Posix-type storage (AFS, NFS etc)

Mem: Memory used by the biggest process, only relevant if >1 GB

Events: Number of events needed for execution of this task

Frequency: in which intervals the whole task needs to be run

Time: elapsed time (=wall time) of the whole task on typical CAF CPUs

Review status

Responsible: RainerMankel

Reviewer/Editor and Date (copy from screen) Comments
Last reviewed by: -- StefanoArgiro - 29 Apr 2009 filled Ecal numbers
Last reviewed by: -- SilviaMaselli - 15 Apr 2008 revised DT Calibration numbers
Last reviewed by: -- MartinWeber - 29 Feb 2008 revised tracker alignment numbers
Last reviewed by: -- MartinWeber - 13 Feb 2008 revised tracker alignment numbers
Last reviewed by: -- -- RainerMankel - 16 Jan 2008 created starting page
Last reviewed by: -- -- RainerMankel - 25 Jan 2008 Initial template
Topic attachments
I Attachment History Action Size Date Who Comment
GIFgif cvs.gif r1 manage 0.5 K 2006-10-16 - 09:49 KatiLassilaPerini  
PNGpng doxygen1.png r1 manage 9.4 K 2006-11-06 - 15:20 KatiLassilaPerini  
Edit | Attach | Watch | Print version | History: r21 < r20 < r19 < r18 < r17 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r21 - 2009-05-06 - FreyaBlekman
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    CMSPublic All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2018 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback