CalDetPID

Contents

Contact Name

Mike Kordosky + Tricia Vahle.

Overview

CalDetPID uses the read-out of the external particle identification detectors to decide what type of particle produced a given event. The nomenclature for the particle types is defined in CalDetParticleType and is also given in the following table

Table: Particle type nomenclature
Particle Type Enum name value
Undetermined kUnknown 0x00
e kElectron 0x01
mu kMuon 0x02
pi kPion 0x04
K kKaon 0x08
p kProton 0x16

CalDetPID is also responsible for using the hit timing and the timing of the PID readout to determine whether or not the event was an ``overlapping event''. CalDetPID produces a Candidate, which can then be passed to other job modules. There is also an associated class called NtpCalDetPID, which eventually gets written to the CalDetDST tree. The methods of CandCalDetPIDHandle are given in the following table:



Table: Methods of CandCalDetPIDHandle
Method Ntp variable Description
NoOverlap() nov Non-zero if all but specified number of hits in time
InCerTime() inct Non-zero if CER(s) signal time is in time
GetPIDType() cpid Bit field describing particle type
GetOLChi2() olchi2 Chi2 from comparison of event timing to template

Input/Output

Input Objects

CalDetPIDModule requires a CandCalDetSIHandle and a CandRecord

Output Objects

Produces a CandCalDetPID candidate

Database Access

The following tables list the requisite database tables and their fields. Currently the data for these tables are stored in text files in CalDetPID/data and are loaded into a temporary database at the start of a job.

Table: TOFRange Database Table
CALDETTOFRANGE  
PARTICLETYPE Enum. particle type to which the row applies
TDC0LOW Low end of acceptable TDC0 values
TDC0HIGH High end of acceptable TDC0 values
TDC1LOW Low end of acceptable TDC1 values
TDC1HIGH High end of acceptable TDC1 values
TDC2LOW Low end of acceptable TDC2 values
TDC2HIGH High end of acceptable TDC2 values
TDC2MINUSTDC0LOW Low end of acceptable TDC2-TDC0 values
TDC2MINUSTDC0HIGH High end of acceptable TDC2-TDC0 values
TDC2MINUSTDC1LOW Low end of acceptable TDC2-TDC1 values
TDC2MINUSTDC1HIGH High end of acceptable TDC2-TDC1 values



Table: CERRange Table
CALDETCERRANGE  
PARTICLETYPE Enum. particle type to which the row applies
CER0LOW Low end of acceptable CER0 ADC values
CER0HIGH High end of acceptable CER0 ADC values
CER1LOW Low end of acceptable CER1 ADC values
CER1HIGH High end of acceptable CER1 ADC values
CER2LOW Low end of acceptable CER2 ADC values
CER2HIGH High end of acceptable CER2 ADC values



Table: OverLapWin Table
CALDETOVERLAPWIN  
PARTICLETYPE Enum. particle type to which the row applies
WINLOW Low end of acceptable hit time window
WINHIGH High end of acceptable hit time window



Table: CERRange Table
CALDETCERTIMEWIN  
PARTICLETYPE Enum. particle type to which the row applies
WIN0LOW Low end of acceptable CER0 time
WIN0HIGH High end of acceptable CER0 time
WIN1LOW Low end of acceptable CER1 time
WIN1HIGH High end of acceptable CER1 time
WIN2LOW Low end of acceptable CER2 time
WIN2HIGH High end of acceptable CER2 time


Configuring & Running

The module to determine the PID of an event is called RealCalDetPID. See the macro uber-all.C for more details. CalDetPID also provides another utility, that of comparing the hit times of an event to a template histogram in order to determine the likelihood of an event being an overlapper. This algorithm requires the existence of template histograms stored in root files within the CalDetPID/data directory. The particle ID package is run using the JobModule ``RealCalDetPIDModule''. The overlapping event identifier algorithms may be configured via RealCalDetPIDModule. The appropriate parameters are listed in Table

Table: Configuration parameters for RealCalDetPIDModule
Name Description Default
NAllowedBefore Number of hits allowed before WINLOW 1
NAllowedAfter Number of hits allowed after WINHIGH 1
NAllowedOut Total number of hits allowed out of WIN range 2
NRequiredIn Number of hits required to be in WIN range 1
TimeFileNum Number of file with template timing histograms to use 0
  (see example macro for details)  



Further Links


Mike Kordosky Last Modified: $Date: 2004/05/27 17:50:37 $