Calibration

1
Calibration

• Where we are? What to do?
• Yves Schutz

2
Terminology

• Offline condition files are ROOT files
• These are available to applications running on
  the GRID via
• Registration into the AliEn file catalogue
  (logical)
• Storage in a GRID storage element (physical)
• The ensemble above has been dubbed OCDB
  (Offline Condition Data Base)
• This is a logical entity and not a physical
  one!!

3
The framework
This is what we discuss today
From URs Source, volume, granularity, update
frequency, access pattern, runtime environment
and dependencies http//pcaliweb02.cern.ch/Collabo
ration/Boards/Computing/Planning/index.html
Physicsdata
files
calibration procedures
API
ECS
DAQ
calibration files
API
Trigger
API
Calibration classes
AliEnLCG metadata file store
DCS
API
AliRoot
DCDB
API
API
HLT
shuttle
API
API Application Program Interface
4
High-level dataflow
Offline
Online
ALICE File Catalogue
DDL
CAF
Monit.Calib.
WN
Publish in AliEn
DAQ Network
Data files
Publish agent
xrootd
Condition files
DAQ Logbook DB
DAQFES
Run info
Castor cache
Data file
SRM
SRM
FTS
T1s
240TB
Condition files
HLTFES
DCSFES
DCS
CASTOR
Shuttle
DCSDB
5
The SHUTTLE
EoR
ECS
DAQ
DCS
HLT
Pre-Proc
SHUTTLE
Loop over all detectors Registration of condition
files Interfaces with info providers
ACORDE
EMCAL
HMPID
FMD
ITS
MUON
PHOS
PMD
T0
TOF
TPC
TRD
V0
ZDC
Detector processors
6
Implementation strategy

• Two tasks (coordinated by L.Betev)
• Development of offline framework algorithms
• Development of the online-offline framework
  algorithms
• Boundary conditions as soon as a run is finished
  there should be enough information to reconstruct
  it
• We have no time / resources to read the data
  twice
• Initial conditions should allow a reasonable
  quality reconstruction
• Better quality condition parameters are obtained
  during the first pass reconstruction (RAW data)
  or from the resulting ESD
• Most of the Core Offline is involved in this

7
Online-offline framework

• Status
• A prototype of the SHUTTLE connecting to DAQ, DCS
  and ECS exists, not yet for HLT
• A procedure to create calibration files in DCS
  exists and will be validated by SPD
• A testing framework that allows standalone
  development of SHUTTLE algorithms without the
  whole machinery had been developed
• The online algorithms to create calibration
  parameters (called from SHUTTLE or run before it
  under ECS control) are essentially missing
• We have a DAQ File Exchange Server and interfaces
  to DAQ logbook, ECS
• We have a DCS File Exchange Server and AMANDA
  server to access to DCS archive DB
• The discussion on the HLT File Exchange Server
  and interfaces is starting

8
Calibration in the online world

• The objective
• Provide a set of calibration parameters already
  for the first pass reconstruction (synchronous
  with pp data taking, delayed by one month for HI)
• The questions to the detectors
• Which parameters are required by reconstruction
  and what is their size, format and frequency of
  update?
• Where and how are these parameters created?
• How to get hold of them?
• Summary at http//pcaliweb02.cern.ch/Collaboration
  /Boards/Computing/Planning/R.xls
• Six use cases covering all known (!!)
  requirements
• http//aliceinfo.cern.ch/static/Documents/Computin
  g_Board/CalibrationSummary.pdf
• To be implemented (before mid-October)
• This has to be made integral part of the
  commissioning of the detector, and as such go
  into the milestones and planning

9
Description of the use cases

• Abbreviations
• FEE Front End Electronics
• FES File Exchange Server
• FC File Catalogue
• DA Detector Algorithms

10
Use case 1
DAQ
DA
Publish agent
Time stamps
DAQ FES
T0 custodial storage
DAQ Logbook DB
AliEn FC
SHUTTLE
11
Use case 1 online creation in DAQ

• Calibration parameters are computed online in the
  DAQ LDC/GDC/Monitoring machines from physics or
  dedicated data
• Results are made available as ROOT files in the
  DAQ FES
• The path of these files together with the start
  and end of run timestamps is written in the DAQ
  Logbook
• At the end of the run additional processing may
  occur controlled by the ECS
• Upon notification by the ECS, the SHUTTLE queries
  the DAQ Logbook for file name and timestamps and
  fetches the appropriate parameter files
• It stores the files into the CERN storage and
  adds an entry (run validity and unique identifier
  of the files) into the AliEn FC

12
Use case 2
DAQ
HLT
Publish agent
DA
Time stamps
T0 custodial storage
DAQ Logbook DB
HLT FES
AliEn FC
SHUTTLE
13
Use case 2 online creation in HLT

• Calibration parameters are computed online in the
  HLT farm from physics data or dedicated data
• Results are made available, as ROOT files, in the
  HLT FES
• The path of the produced files together with the
  start and end of run timestamps is written in the
  DAQ Logbook or the HLT equivalent
• At the end of the run additional processing may
  occur controlled by the ECS
• Upon notification by the ECS, the SHUTTLE queries
  the DAQ Logbook or the HLT equivalent for file
  name and timestamps and fetches the appropriate
  parameter files
• It stores the files into the CERN storage and
  adds an entry (run validity and unique identifier
  of the files) into the AliEn FC

14
Use case 3
DAQ
Time stamps
Publish agent
DAQ Logbook DB
T0 custodial storage
AliEn FC
SHUTTLE
DCS
DCS FES
DA
15
Use case 3 online creation in DCS

• Calibration parameters are computed online in the
  DCS farm from dedicated data
• Results are made available, as ROOT files, in the
  DCS FES
• The path of the produced files together with the
  start and end of run timestamps is written in the
  DAQ Logbook or equivalent DB
• At the end of the run additional processing may
  occur controlled by the ECS
• Upon notification by the ECS, the SHUTTLE queries
  the DAQ Logbook or the equivalent DB for file
  name and timestamps and fetches the appropriate
  parameter files
• It stores the files into the CERN storage and
  adds an entry (run validity and unique identifier
  of the files) into the AliEn FC

16
Use case 4
DAQ
Time stamps
Publish agent
DAQ Logbook
T0 custodial storage
AliEn FC
SHUTTLE
Amanda
DCS
Archive DB
17
Use case 4 parameters monitored by DCS

• DCS monitored parameters are stored in the DCS
  Archive DB
• At the end of the run additional processing may
  occur controlled by the ECS
• Upon notification by the ECS the SHUTTLE queries
  the DAQ Logbook for the start and end of run
  timestamps and then queries the Archive for the
  relevant parameters
• The SHUTTLE pre-processors evaluates the
  parameters, creating the ROOT files
• It stores the files into the CERN storage and
  adds an entry (run validity and unique identifier
  of the files) into the AliEn FC

18
Use case 5
DAQ
Publish agent
Time stamps
DAQ Logbook
T0 custodial storage
AliEn FC
SHUTTLE
DCS
Configtion DB
DCS FES
19
Use case 5 FEE config file

• The FEE parameters are fed to the electronics
  either trough the DCS or through the DAQ DDL
• DCSfiles are stored in the DCS Configuration DB
  and on the DCS file exchange server, the
  notification is done through the DCS Archive DB
• DAQfiles are stored directly in the DAQ FES and
  their name registered in the DAQ Logbook (back to
  Use Case 1)
• At the end of the run additional processing may
  occur controlled by the ECS
• Upon notification by the ECS the SHUTTLE queries
  the DCS Archive DB for timestamps and file names,
  collects the data and pre-processes them
  (ROOTification,)
• The SHUTTLE stores the files into the CERN
  storage and adds an entry (run validity and
  unique identifier of the files) into the AliEn FC

20
Use case 6
DAQ
DA
Publish agent
Time stamps
DAQ FES
T0 custodial storage
DAQ Logbook DB
AliEn FC
SHUTTLE
Configtion DB
DCS
21
Use case 6 online creation in DAQ

• Calibration parameters are computed online in the
  DAQ LDC/GDC/Monitoring machines from physics or
  dedicated data
• Results are made available as ROOT files in the
  DAQ FES
• The path of these files together with the start
  and end of run timestamps is written in the DAQ
  Logbook
• At the end of the run additional processing may
  occur controlled by the ECS
• Upon notification by the ECS, the SHUTTLE queries
  the DAQ Logbook for file name and timestamps and
  fetches the appropriate parameter files
• It stores the files into the CERN storage and
  adds an entry (run validity and unique identifier
  of the files) into the AliEn FC
• DCS accesses the same file in the DAQ FES,
  compares the value to reference values stored in
  the DCS Configuration DB, calculates new settings
  and updates the FEE values.

22
To do list

• Detectors
• Finalise the requirement document (MS1)
• Implement the online algorithms (not yet started,
  except SPD and T0-TOF combined time zero
  calibration) (MS2)
• Pre-processor detector calibration algorithms
  and ROOTification not started (MS3)
• SHUTTLE
• Framework (Offline) done
• Provide template for pre-processor (MS4)
• File Exchange Server
• File system definition (DAQ done, DCS HLT
  starting) (MS5)
• Online framework (DAQ in progress, DCS HLT
  starting) (MS6)
• HLT Discussion started (MS7)
• Online algorithms
• DAQ, DCS, HLT provides template (MS8)
• All DAQ, DCS, HLT, Detectors
• Provide milestones date NOW