Software for the CMS Cosmic Challenge Giacomo BRUNO UCL, Louvain-la-Neuve, Belgium On behalf of the CMS Collaboration CHEP06, Mumbay, India February 16, 2006

CHEP06 16/2/ Mumbay, India 2 Software for the CMS Cosmic Challenge G. Bruno Outline CMS and the Magnet Test Cosmic Challenge (MTCC) Detector configuration Running conditions Software architecture Reconstruction and Calibrations at the MTCC Online operation: event selection and monitoring Offline operation

CHEP06 16/2/ Mumbay, India 3 Software for the CMS Cosmic Challenge G. Bruno The CMS detector 100 kHz 40 MHz TRIGGER and DAQ Two event selection systems HLT is a farm of commercial processors  Event selection based on offline software using full event data

CHEP06 16/2/ Mumbay, India 4 Software for the CMS Cosmic Challenge G. Bruno CMS Magnet Test Cosmic Challenge (MTCC) Goals  Commissioning, training and field mapping of the solenoid magnet  Sub-detector installation (~5% of final detector), performance, triggering, alignment (in the presence of a Magnetic field)  Software (completely new offline SW design: project started at the end of 2004) Read out all detectors with Global DAQ Decipher raw data - debug Local Reconstruction in all detectors (clusters, Muon track segments) Calibration and alignment using Database infrastructure Monitoring and Visualization (based on reconstruction) Data transfer to CERN and other CMS GRID sites Global event reconstruction (tracks) Schedule  Insertion and cabling of sub-detectors by April 10  One month magnet test after April 16 Combined data taking with global DAQ immediately  One week of combined data taking at constant field mid-to-end May  Field mapping to follow (June): only with HCAL and Muon

CHEP06 16/2/ Mumbay, India 5 Software for the CMS Cosmic Challenge G. Bruno Muon detectors at the MTCC ME1 ME2 ME3 ME4 ME2 ME3 ME4 ME3 ME4 DT-10 DT - 11 ME1 DT-10 DT - 11 ME2 Drift Tubes  14 stations (5% of final system)  Tracks can cross up to 4 stations  One η-view and two φ-view track segments per station  ~1 kB/ev CSC  36 stations (8% of final system) 36 k channels  Tracks can cross up to 4 stations  One track segment per station  10÷20 kB/ev RPC  5 measuring planes  Participation is still uncertain Hardware Alignment system  Laser based  Measurements of Muon support structures. Also relative to Tracker support structure O(100 μm) accuracy 500 MB of data per day Data taken through DCS

CHEP06 16/2/ Mumbay, India 6 Software for the CMS Cosmic Challenge G. Bruno Silicon Tracker at the MTCC Silicon Strip  133 modules (1% of final Tracker) 80 k channels  <1 kB/ev (200 kB/ev) with (no) zero suppression  Tracks can cross up to 6 detectors  Custom support structures Need special geometry (ready, including survey measurement for initial alignment) Pixel  Not participating IGUANA visualization of Tracker MTCC geometry

CHEP06 16/2/ Mumbay, India 7 Software for the CMS Cosmic Challenge G. Bruno Calorimeters at the MTCC ECAL  Two supermodules  3.6 k channels (~5% of final system)  <5 kB/ev (80 kB/ev) with (no) zero suppression HCAL  11 barrel + 4 endcap wedges  ~1 k channels (10 % of final system)  5 kB/ev (30 kB/ev) with (no) zero suppression  Trigger electronics IGUANA visualization: real cosmics seen at Test Beams

CHEP06 16/2/ Mumbay, India 8 Software for the CMS Cosmic Challenge G. Bruno Trigger and DAQ at the MTCC L1 Trigger  DT or CSC track segments coincidence in one or more stations Expected rate: up to 2÷3 kHz Can require angular or pointing (to Tracker) cuts. –Rate reduced to about O(100 Hz)  HCAL MIP trigger (possibly) Rate adjustable through thresholds Data sizes  <50 KB/ev if Tracker and ECAL in zero suppression mode DAQ  Two stage event building as in final system super fragment building RU building (single slice)  Filter Farm: 16 Dual-Xeon 2.8 GHz 2GB/80GB  50 MB/s max data to disk rate Up to 1 KHz events to disk rate CMS DAQ MTCC DAQ

CHEP06 16/2/ Mumbay, India 9 Software for the CMS Cosmic Challenge G. Bruno Events at the MTCC Acceptance  2.2 kHz: cosmics crossing instrumented Muon chambers (R 0 )  9 Hz: also cross at least one Tracker module (R T0 )  O(100 Hz): average expected event to disk rate (R D ) Online event selection  Scenario 1: only generic L1 trigger R T = R D / R 0 x R T0 ; R T ==“Tracker” events to disk rate  Scenario 2: Muon pointing trigger (R 0 ~100 Hz) R T = 9 Hz, if R D >=100 Hz Inconvenient for Calorimeters and Muons  Scenario 3: generic L1 trigger + HLT selection Maximize L1 rate (up to 2.2 kHz physical one) Do remaining selection in HLT using a simple ADC counts method Get 2 streams out of DAQ: –Tracker stream (ADC count method) ~ 10 Hz –Main stream, e.g. selection based on L1 info and compatible with (R D -10 Hz) Need tracker local reconstruction running online

CHEP06 16/2/ Mumbay, India 10 Software for the CMS Cosmic Challenge G. Bruno Event Builder Event Processing in new CMS software (online/offline) EVENT DATA: Raw Data Digis Clusters …. Raw2Digi NON EVENT DATA: Cabling calibrations ….. Clusterizer Raw Data Source Offline Conditions DB POOL - Event DB Output Mod Monitor/Filter Details in talks by C. Jones “The new CMS Event Data model” “Access to Non-Event data for CMS”

CHEP06 16/2/ Mumbay, India 11 Software for the CMS Cosmic Challenge G. Bruno Non-Event data: Database model Online DB HLT “Offline” DB Offline DB OMDS (Online DB)  Sub-detector configuration and conditions ORCON (HLT Conditions DB)  Non event data used by the offline software in the HLT ORCOFF (Offline Conditions DB)  Non event data used by the offline software at Tier 0/1/2 Data transfers  Configuration and conditions from OMDS to ORCON and ORCOFF  Offline computed calibrations to ORCOFF and ORCON

CHEP06 16/2/ Mumbay, India 12 Software for the CMS Cosmic Challenge G. Bruno Reconstruction example: Tracker local reco (will be done online for Monitoring and Filtering) RAWDATA  FED buffers DIGIs  Channel ADC counts Clusters  groups of calibrated channel amplitudes Cabling channel bad flag, gain, noise Non-Event DataEvent Data

CHEP06 16/2/ Mumbay, India 13 Software for the CMS Cosmic Challenge G. Bruno Tracker Local Reco: Non-Event data flow Carry out commissioning procedures (see R. Bainbridge’s talk : “Commissioning Procedures and Software for the CMS Silicon Strip Tracker”)  Electronics configured (ready for data taking)  Online DB now contains All detected hardware components and connections pedestals, noise, bad strips, (per channel) Transfer data from Online to Offline DB  program using OCCI libraries for ORACLE access Conditions objects available in Offline DB  Readout connections (needed by Raw2Digi)  Control connections (useful when monitoring)  Noise/bad channels (needed by Clusterizer)

CHEP06 16/2/ Mumbay, India 14 Software for the CMS Cosmic Challenge G. Bruno Filter Farm architecture

CHEP06 16/2/ Mumbay, India 15 Software for the CMS Cosmic Challenge G. Bruno Online : filtering and streaming Filter Unit application  Fully integrated with Event Building and Run Control suite  Fully integrated with offline software (including DQM) and DB infrastructure Can execute an arbitrary set of reconstruction, analysis (monitoring) and filtering (event selection) modules Takes new calibrations at the beginning of every run  Data storage Local output using POOL Forward events to Storage Manager Storage Manager  N to 1 streaming functionality (ROOT based) available  MTCC goals Multi streaming and Event Server functionality (in development) File catalog suitable for export

CHEP06 16/2/ Mumbay, India 16 Software for the CMS Cosmic Challenge G. Bruno Online : monitoring DQM Software architecture (see C. Leonidopoulos’ talk:” Physics and Data Quality Monitoring at CMS ”)  Monitorable Producers Executed in the event loop (access to Event and Non-Event data)  Monitorable Consumers Receive and analyze (comparison with reference, alarms,..) updated monitorables. Have only access to Non-Event data Modes of operation  Online – MonitorConsumer FU nodes book and fill monitorables Can in principle work at the FF input rate Shortest delay Additional load for FU nodes  Online – EventConsumer decoupled from Filter Farm Storage Manager forwards selected events to monitoring dedicated processors  Quasi Online – EventConsumer monitoring applications access event data from “Hot buffers”

CHEP06 16/2/ Mumbay, India 17 Software for the CMS Cosmic Challenge G. Bruno Offline operation Data distribution and access  Disk server (a few TB) available at MTCC site for immediate analysis  Data stored at CERN (CASTOR) and shipped to a number of remote sites using LCG tools Offline analysis  Local reconstruction Understanding and commissioning of all sub-detectors  Alignment corrections computation Use data from the Hardware Alignment system MTCC Goal: have the software that computes corrections and makes them available to reconstruction  Track reconstruction Validation and cross check of Muon Hardware Alignment system data Track reconstruction may not be ready for MTCC. Need to ensure to the best possible extent the quality of data with local reconstruction monitoring

CHEP06 16/2/ Mumbay, India 18 Software for the CMS Cosmic Challenge G. Bruno Conclusions The MTCC is a fundamental milestone for the new CMS software  Global Data Acquisition with (almost) all sub- detectors  Data quality monitoring, event selection and streaming based on local reconstruction  Non-Event Data DB infrastructure  Offline global reconstruction using alignment data CMS is on schedule to achieve these goals