Difference between revisions of "MuonCalib Tutorial"
| Line 21: | Line 21: | ||
==Getting started== | ==Getting started== | ||
In order to get started one should know that this field is prone to many changes over time. Backward compatibility is surely broken since the ntuple format changed a lot in the period of november 2005. The ntuple format is defined by the MuonCalib package (''MuonCalibNtuple''), and the analysis package needs a certain ntuple format to be able to fill the MuonCalib EDM classes offline. In the following sections, recipes will be provided for different kinds of ntuple formats. | In order to get started one should know that this field is prone to many changes over time. Backward compatibility is surely broken since the ntuple format changed a lot in the period of november 2005. The ntuple format is defined by the MuonCalib package (''MuonCalibNtuple''), and the analysis package needs a certain ntuple format to be able to fill the MuonCalib EDM classes offline. In the following sections, recipes will be provided for different kinds of ntuple formats. | ||
| + | |||
| + | Currently, there are two different formats of the Calibration Segment Ntuple, described in the following tables: | ||
| + | * [[CalibSegmentNtupleContentA]Calibration Segment Ntuple Content A]. Information on patterns, segments en Mdt hits. All segments appear twice on the ntuple since a refit-flag is performed during ntuple-writing. This ntuple should be obsolete since release 11.X.0. | ||
| + | * [[CalibSegmentNtupleContentB]Calibration Segment Ntuple Content B]. Information on patterns, segments and hits of all technologies (Mdt's containing extra calibration information, the other technologies are not yet fully implemented). No extra refit is performed, so no double segments. In addition, truth information and event information (run and event number) is available. | ||
| + | * [[CalibSegmentNtupleContentC]Calibration Segment Ntuple Content C]. Is non-existent at the moment. It is sure that one will be defined in the future, the difference with Ntuple Content B will be a better description of the other technology hits, and timing information on event-level. | ||
Revision as of 14:43, 30 November 2005
Muon calibration tutorial
Welcome to the Muon Calibration Tutorial Page! After doing this tutorial, you will be able to run Athena, make your ntuples containing segment information. This ntuple can then be used as input to do analysis with help of the skeleton analysis package provided. This analysis package CalibSegmentAnalysis relies heavily on the Calibration framework but is Athena independent.
Much information on validation, calibration and alignment can be found at the MuonSpectrometer homepage.
Introduction
Calibration
General information about the need of calibration in the MuonSpectrometer.
Calibration framework
A clear Wiki page on the Calibration Framework by Domizia and Niels can be found on the MuonCalibrationFramework Wiki. At this site, the Calibration EDM is explained.
Why segments?
Maybe needed to explain the concept of segments and the calibration EDM, is to be written (work in progress). A starting point of Calibration Segments and its scope in the Reconstruction EDM can be found in a presentation given by Zdenko during the ATLAS Muonweek september-2005 called Calibration Segment Ntuple
Getting started
In order to get started one should know that this field is prone to many changes over time. Backward compatibility is surely broken since the ntuple format changed a lot in the period of november 2005. The ntuple format is defined by the MuonCalib package (MuonCalibNtuple), and the analysis package needs a certain ntuple format to be able to fill the MuonCalib EDM classes offline. In the following sections, recipes will be provided for different kinds of ntuple formats.
Currently, there are two different formats of the Calibration Segment Ntuple, described in the following tables:
- [[CalibSegmentNtupleContentA]Calibration Segment Ntuple Content A]. Information on patterns, segments en Mdt hits. All segments appear twice on the ntuple since a refit-flag is performed during ntuple-writing. This ntuple should be obsolete since release 11.X.0.
- [[CalibSegmentNtupleContentB]Calibration Segment Ntuple Content B]. Information on patterns, segments and hits of all technologies (Mdt's containing extra calibration information, the other technologies are not yet fully implemented). No extra refit is performed, so no double segments. In addition, truth information and event information (run and event number) is available.
- [[CalibSegmentNtupleContentC]Calibration Segment Ntuple Content C]. Is non-existent at the moment. It is sure that one will be defined in the future, the difference with Ntuple Content B will be a better description of the other technology hits, and timing information on event-level.