1 / 5

Status of the calibration framework

Status of the calibration framework. CDB access in AliSimulation/Reconstruction. CDB access: detector by detector overview. CDB access for the PDC. CDB access in AliSimulation/Reconstruction. CDB storage initialization:. void AliSimulation::SetDefaultStorage(const char* uri)

pduncan
Download Presentation

Status of the calibration framework

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Status of the calibration framework • CDB access in AliSimulation/Reconstruction • CDB access: detector by detector overview • CDB access for the PDC

  2. CDB access in AliSimulation/Reconstruction • CDB storage initialization: • void AliSimulation::SetDefaultStorage(const char* uri) • void AliSimulation::SetSpecificStorage(const char* detName, const char* uri • Default storage automatically initialized to $ALICE_ROOT in AliSimulation::Run, if not yet set • AliCDBManager’s run number set in AliSimulation::RunSimulation(), just after gAlice is initialized • what about AliReconstruction?

  3. CDB access detector by detector • MUON, FMD, TOF, ZDC, TPC, TRD: • Calibration objects in cvs (DET/Calib) • Decalibration/calibration framework ready • Latest upgrades in AliCDBManager (Get(), usage of central run number) not always implemented • T0, ITS: • Calibration objects in cvs (DET/Calib) • Decalibration/calibration framework ready • CDB access in AliDET constructor, before the run number is set in gAlice! • RICH: • Calibration objects in cvs (RICH/RICHConfig/RefIdxC6F14) • Decalibration/calibration framework ready • CDB access in AliDET constructor, before the run number is set in gAlice! • but calibration parameter is C6F14 ref index, it is probably needed in simulation…

  4. CDB access detector by detector • PHOS, PMD: • Calibration objects not yet in cvs! • Decalibration/calibration framework ready • V0, EMCAL: • Calibration objects not yet in cvs! • Decalibration/calibration framework: still at first stages (container classes) • CRT: • nothing done yet!

  5. CDB access in PDC • Strategy • Different sets of calibration and alignment objects, in order to account for “ideal” geometry/detector response, “full” mis[align/calib], “residual” mis[align/calib] • Different Grid storages for each align/calib set. • Example of setting a particular calibration/alignment storage pair: AliCDBManager::Instance()-> SetDefaultStorage(“alien://A_DB”); AliCDBManager::Instance()-> SetSpecificStorage(“align”,“alien://Another_DB”); • Question: how to prepare the different calibration sets?

More Related