ATLAS Offline Software
Loading...
Searching...
No Matches
The InDetTrackValidation package

Validation tools for tracking in the inner detector.

Author
Andre.nosp@m.as.S.nosp@m.alzbu.nosp@m.rger.nosp@m.@cern.nosp@m..ch, Sebas.nosp@m.tian.nosp@m..Flei.nosp@m.schm.nosp@m.ann@c.nosp@m.ern..nosp@m.ch

Introduction

This package contains tools to validate the tracking in the inner detector. This includes tools to fill validation ntuples e.g. with measurement data and a tool for the calculation of SCT residuals and pulls.

Class Overview

The InDetTrackValidation package contains the following classes:

Ntuple variables of the InDet::SCT_ClusterValidationNtupleWriter

SCT_RunNumberrun numberint 
SCT_EventNumberevent number for current PRD vectorint 
SCT_LumiBlockevent lumi block informationint 
SCT_TimeStampevent time stampint 
SCT_BunchCrossingevent bunch crossing IDint 
SCT_nRIOsnumber of RIOs, i.e. SCT clusters, in the event. This variable set the size of the vectors with cluster information.int 
SCT_DriftRadiuslocal x coordinate of stripstd::vector<float>mm
SCT_SurfaceXglobal x coordinate of SCT wafer centerstd::vector<float>mm
SCT_SurfaceYglobal x coordinate of SCT wafer centerstd::vector<float>mm
SCT_SurfaceZglobal x coordinate of SCT wafer centerstd::vector<float>mm
SCT_BarrelEndcapfrom IdHelper: pos/neg barrel (+/-1) and pos/neg endcap (+/-2)std::vector<int>1:bar, 2:ec
SCT_LayerDiskfrom IdHelper: layer/disk indexstd::vector<int> 
SCT_EtaModulefrom IdHelper: module index in etastd::vector<int> 
SCT_PhiModulefrom IdHelper: module index in phistd::vector<int> 
SCT_DeltaPhiplease provide description!std::vector<float> 
SCT_HitErrplease provide description!std::vector<float> 
RDO_SCT_RDO_Group_SizeRDO group sizestd::vector<int> 
RDO_SCT_Layerindex of the SCT-layer in which the SCT wafer is positionedstd::vector<int> 
RDO_SCT_Etaeta of the SCT waferstd::vector<int> 
RDO_SCT_Phiphi of the SCT waferstd::vector<int> 
RDO_SCT_Sideside of the SCT wafer (0 or 1) within the SCT modulestd::vector<int> 
RDO_SCT_Barrelecbarrel/endcap index (barrel: 0, endcap: +/-2)std::vector<int> 
RDO_SCT_FirstStripindex (could be from 0 to 767) of the fired strip within the SCT waferstd::vector<int> 
RDO_SCT_NumHitsInWafernumber of hits in the SCT waferstd::vector<int> 
RDO_SCT_WaferHashindex (could be from 0 to 8175) of the fired SCT waferstd::vector<int> 
RDO_SCT_TotalNumBSErrstotal number of BS errors.int 
RDO_SCT_BCIDErrsbunch crossing(BC) ID error - the ROD sets a bit in the link header if the bunch crossing ID for the event it gets ba ck from the link doesn't match its own bunch crossing IDstd::vector<int> 
RDO_SCT_LVL1Errssame as BCID error, but with the LVL1IDstd::vector<int> 
RDO_SCT_TimeOutErrsthe ROD sent a trigger to the module but got no data back down the link (perhaps the module is dead)std::vector<int> 
RDO_SCT_PreambleErrsthe ROD found something strange in the header from the link, and set a bit to flag itstd::vector<int> 
RDO_SCT_FormatterErrsthe ROD found something strange in the header from the link, and set a bit to flag itstd::vector<int> 
RDO_SCT_TrailerErrsthe ROD found something strange in the link trailer and sets a bit there to flag itstd::vector<int> 
RDO_SCT_HeaderTrailerLimitErrsat high trigger rates and/or big events, where the module can't send events fast enough, so just sends headers and trailers, with no hits inbetweenstd::vector<int> 
RDO_SCT_ABCDErrsone of the ABCD chips on the module flagged an error - these errors take the place of a hit, rather than being in the header or trailerstd::vector<int> 
RDO_SCT_RawErrsthe ROD expected a hit, but the word doesn't match the expected format (e.g. due to opto noise?); this type of error also takes the place of a hitstd::vector<int> 
RDO_SCT_BSParseErrsthe ByteStream decoder found something strange - either a strip out of range or something not in the cabling map, or data words that don't match up with any expected patternstd::vector<int> 

Extra Pages