Upload
hallam
View
27
Download
0
Embed Size (px)
DESCRIPTION
Fast OR Trigger simulation. Also shown at trigger meeting (13 May 2009) http ://indico.cern.ch/getFile.py/access?resId=3&materialId=slides&confId=56747. Pixel Trigger Conditions - Transfer Scheme. RO Electronics. Fast-OR Signals. CTP Inputs. OCDB. ECS. SOR, run number. Pixel Trigger - PowerPoint PPT Presentation
Citation preview
A. Mastroserio - Weekly Offline meeting 1
Fast OR Trigger simulation
14/05/2009
Also shown at trigger meeting (13 May 2009) http://indico.cern.ch/getFile.py/access?resId=3&materialId=slides&confId=56747
A. Mastroserio - Weekly Offline meeting 2
Fast-OR
Signals
OCDB
RO Electronics
Offline network
Shuttle Trigger Preprocessor
Pixel Trigger Conditions - Transfer Scheme
ECS
SOR, run number
Pixel Trigger System (PIT)
DCS FXS
CTP Inputs CTP
AliITSTriggerConditions(ITS/Calib/PITConditions)
Trigger conditions(Text Format)
Trigger conditions(OCDB Format)
Slides from H. Tydesjo vailable at http://amastros.home.cern.ch/amastros/doc/PitOffline/
14/05/2009
A. Mastroserio - Weekly Offline meeting 3
General overviewALICE AliRoot simulation
Note: At this stage no reconstruction has been performed yet i.e.: Fast Or signals are generated once &“forever” at the simulation stage
SPD Raw Data ->FO bit on/off (trailer in data word)
Data from SPD in:• ITS.Digits.root• ITS Raw Data
(produced from simulated Digits)->AliITSFOsignalsSPD
PIT gets 1200 FO pulses and processes its logical functions (mask, parameters, algorithms)
PIT sends 10 outputs to the CTP
AliITSTrigger: reads the AliITSFOsignals , returns 10 AliTriggerInputs
14/05/2009
A. Mastroserio - Weekly Offline meeting 4
Simulated FO fired mapITS.Digits.root
SPD Digits[ready to be dead and noisy
pixels aware (not by default) ]
AliITSFOGeneratorSPD
OCDB (simulation)(simulated maps)
AliITSFONoiseSPD AliITSFOEfficiencySPD(ITS/Calib/SPD/FONoise) (ITS/Calib/SPD/FOEfficiency)
AliITSFOsignalsSPD
If raw data are simulated : AliITSFOsignalsSPD are propagated to the data word as FO bit
In real raw data : FO bits in raw data file carry information on fired chips
( Stored in the same Digits file)
14/05/2009
A. Mastroserio - Weekly Offline meeting 5
Fast-OR
Signals
OCDB
RO Electronics
Offline network
Shuttle Trigger Preprocessor
Pixel Trigger Conditions - Transfer Scheme
ECS
SOR, run number
Pixel Trigger System (PIT)
DCS FXS
CTP Inputs CTP
AliITSTriggerConditions(ITS/Calib/PITConditions)
Trigger conditions(Text Format)
Trigger conditions(OCDB Format)
Slides from H. Tydesjo vailable at http://amastros.home.cern.ch/amastros/doc/PitOffline/14/05/2009
A. Mastroserio - Weekly Offline meeting 6
# This file was automatically generated.# It describes the configuration of the Pixel Trigger active during a specified ALICE run[Header]RUN_NUMBER=123456PROCESSING_FIRMWARE_VERSION =1INPUT_CONDITIONS_VERSION =0PARAMETERS_VERSION =0VERSION_REGISTER_VALUE =264GLOBAL_DESCRIPTION = 'Firmware implementing Pixel Trigger multiplicity algorithms'
[Outputs]# Lines describing the algorithms implemented on the Pixel Trigger outputs by the active firmware0 = '0SMB','Minimum bias trigger. Ntot > total_threshold and Nin > inner_threshold and Nout > outer_threshold'1 = '0SH1','High multiplicity. Nin > inner_threshold and Nout > outer_threshold'2 = '0SH2','High multiplicity. Nin > inner_threshold and Nout > outer_threshold'3 = '0SH3','High multiplicity. Nin > inner_threshold and Nout > outer_threshold'4 = '0SH4','High multiplicity. Nin > inner_threshold and Nout > outer_threshold'5 = '0SPF','Past future protection. Ntot > total_threshold and Nin > inner_threshold and Nout > outer_threshold'6 = '0SX1','Spare background. Nin > Nout + background_offset_inner'7 = '0SX2','Spare background. Nout > Nin + background_offset_outer'8 = '0SBK','Background. Ntot > background_threshold_both'9 = '0SCO','Programmable cosmic algorithm'
[Output_parameters]# Lines listing the numeric parameters for each of the 10 outputs# Pairs of parameter name and value pairs are separated by semi-colon. There can be a avariable number of parameters# Example:# output number='parameterName0', value; 'parameterName1', value1; 'parameterNameN', valueN0 = 'total_threshold',255;'inner_threshold',5;'outer_threshold',25;1 = 'inner_threshold',273;'outer_threshold',68;2 = 'inner_threshold',273;'outer_threshold',68;3 = 'inner_threshold',273;'outer_threshold',68;4 = 'inner_threshold',273;'outer_threshold',68;5 = 'total_threshold',10;'inner_threshold',273;'outer_threshold',68;6 = 'offset',273;7 = 'offset',68;8 = 'total_threshold',10;9 =
[Active_chips]# This section lists the chips with their fastor actively used in the trigger logic# There are as many lines as halfstaves with masked chips.# If an halfstave is not listed by default all its chips are active # The format of each line is: # sector number(0-9), side(A|C), halfstave number(0-5) = fastor mask (string of '0' if masked, '1' if active; leftmost is chip 9, rightmost is chip 0)# Example: 5, C, 5 = 00000000010,A,0=0000000000 #(not plugged)0,A,1=0000000000 #(not plugged)0,A,4=0000000000 #(not plugged) […..]
brand new Trigger conditions txt file @ DSF from Cesar
Algorithms
Parameters
Active chips14/05/2009
A. Mastroserio - Weekly Offline meeting 7
PIT conditions in OCDB (->to be updated)
root [1] c = (AliITSTriggerConditions *)AliCDBEntry->GetObject()(class AliITSTriggerConditions*)0x11021c0root [2] c->DumpAll()[Header]RUN_NUMBER = 0PROCESSING_FIRMWARE_VERSION = 0GLOBAL_DESCRIPTION = conditions generated offlineVERSION_REGISTER_VALUE = 0INPUT_CONDITIONS_VERSION = 0PARAMETERS_VERSION = 0
[Outputs]11 = 'SPD_GFO_L0', 'geometry triggers'12 = 'SPD_HMULT_L0', 'multiplicity triggers'
[Output_parameters]11 = 'total_threshold', 1;12 = 'total_threshold', 150;
[Active_chips]root [3] c->GetNumAlgo()(const unsigned short)2
14/05/2009
A. Mastroserio - Weekly Offline meeting 8
PIT simulation AliITSTrigger (procedure performed by AliITSTriggerFOProcessor)
AliITSFOsignalsSPD OCDBAliITSTriggerConditions
(ITS/Calib/PITConditions)
AliITSTrigger
AliITSTriggerFOProcessor
TObjArrayAliTriggerInput
AliTriggerInputAliTriggerInput
AliCentralTrigger
14/05/2009
Trigger Inputs take into account inactive chips
A. Mastroserio - Weekly Offline meeting 9
ESD
AliITSDetTypeRec
Digits
AliITSFOSignalsSPD
AliITSClusterFinderV2SPD
Raw Data
FO Bits
AliMultiplicity
Fast-OR Fired Map Remove in-active chipsfrom fast-or fired map
OCDBAliITSTriggerConditions(ITS/Calib/PITConditions)
Fast-OR Bits - Reconstruction
14/05/2009
A. Mastroserio - Weekly Offline meeting 10
PIT simulation summary• Preliminary version in svn
• FO fired chip maps are ok.– Default settings retrieve same outputs in simulation and reconstruction from both Digits
or raw data (simulated))– Consistency if applying FO efficiency and noise
• To Do list
– PIT conditions to be updated
– Introduction of 0SCO algorithm (= cosmic trigger)
– Code to create OCDB object from PIT conditions txt file (on svn once the framework is developed)
14/05/2009
A. Mastroserio - Weekly Offline meeting 11
….some comments… • CTP inputs consider FO signals without inactive chips, but if
Digits are not “dead pixel aware” the FO signals are over estimated
• If simulated FO signals are built starting from a specific dead/noisy pixel configuration and OCDB objects change for SPD, then the full simulation should be run again to retrieve consistent trigger outputs.
• Given such a scenario, MC production can consider only one specific SPD configuration
14/05/2009
Trigger meeting / CERN 13.5.2009 12D. Elia (INFN Bari)
Simulation - generate SPD digits: RemoveDead OFF AddNoisy OFF
- generate FO signal: according to SPD digits (so by default NO dead, NO noisy)
- generate FO TriggerInputs: takes into account FO in-active chips (by default NO in-active chips)
Reconstruction - in the clusterfinder: yes, here remove dead and noisy!
- propagate FO bits to the ESD: takes into account FO in-active chips (by default NO in-active chips)
A. Mastroserio - Weekly Offline meeting 13
Extra slides
14/05/2009
A. Mastroserio - Weekly Offline meeting 1414/05/2009
Ideal Equipment for Digits
FO signals
Inactive chips removal
New FO signals
CTP inputs
Equipment for Digits
FO signals ‘
New FO signals ‘
CTP inputs
Inactive chips removal
dead HS
Scenario A Scenario B
SPD Digits (simulated fired pixels) can be aware of dead / noisy pixels . SPD clusters are always aware of both. Possible clusters/FO maps inconsistency if users do not know how the simulation has been performed.
A. Mastroserio - Weekly Offline meeting 1514/05/2009
1 0SMB Minimum Bias (I+O)thIO,mb and IthI,mb and OthO,mb
2 0SH1 High Multiplicity 1 IthI,hm1 and OthO,hm1
3 0SH2 High Multiplicity 2 IthI,hm2 and OthO,hm2
4 0SH3 High Multiplicity 3 IthI,hm3 and OthO,hm3
5 0SH4 High Multiplicity 4 IthI,hm4 and OthO,hm4
6 0SPF Past Future Prot (I+O)thIO,pfp and IthI,pfp and OthO,pfp
7 0SBK Background(0) I O+ offsetI
8 0SX1 Background(1) O I+ offsetO
9 0SX2 Background(2) (I+O) th(I+O),bnd
10 0SCO Cosmic Selectable coincidence
I := number of active FO on Inner layer
O := number of active FO on Outer layer
List of Algorithms
Implement algorithmsfor each label in AliITSTriggerFOProcessor
A. Mastroserio - Weekly Offline meeting 1614/05/2009
AliITSDetTypeSim
AliITSDDLRawData
AliITSTrigger
OCDB
Pixel Trigger Simulation Scheme
AliITSFOGeneratorSPD AliITSTriggerFOProcessor
AliITSTriggerConditions(ITS/Calib/PITConditions)
AliCentralTrigger
TObjArray
AliTriggerInputAliTriggerInputAliTriggerInput
AliITSFONoiseSPD(ITS/Calib/SPDFONoise)
AliITSFOEfficiencySPD(ITS/Calib/SPDFOEfficiency)
Digits
AliITSFOSignalsSPD
Raw Data
FO Bits
AliITSsimulationSPD