1 / 16

Overview of Fast-OR Trigger Conditions and Simulation Methods in ALICE

This presentation provides an in-depth overview of Fast-OR trigger conditions and the simulation techniques used within the ALICE experiment at CERN. It details the configuration for the pixel trigger system during specific runs, highlighting the active chips, output algorithms, and associated parameters. The document also covers the simulation of Fast-OR signals and their integration into real raw data, emphasizing the significance of trigger conditions in data acquisition. The insights are aimed at researchers and engineers involved in the ALICE project and trigger systems.

hallam
Télécharger la présentation

Overview of Fast-OR Trigger Conditions and Simulation Methods in ALICE

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. Fast OR Trigger simulation Alsoshown 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. Pixel Trigger Conditions - Transfer Scheme RO Electronics Fast-OR Signals CTP Inputs OCDB ECS SOR, run number Pixel Trigger System (PIT) CTP Trigger conditions (Text Format) DCS FXS Offline network Trigger conditions (OCDB Format) Shuttle Trigger Preprocessor AliITSTriggerConditions(ITS/Calib/PITConditions) Slidesfrom H. Tydesjovailable at http://amastros.home.cern.ch/amastros/doc/PitOffline/ A. Mastroserio - Weekly Offline meeting

  3. Generaloverview AliRootsimulation ALICE Note: At this stage no reconstructionhasbeenperformedyet i.e.: Fast Or signals are generated once &“forever” at the simulation stage A. Mastroserio - Weekly Offline meeting

  4. OCDB (simulation) Simulated FO firedmap ITS.Digits.root SPD Digits [readytobe dead and noisypixelsaware (notby default) ] (simulatedmaps) AliITSFONoiseSPDAliITSFOEfficiencySPD (ITS/Calib/SPD/FONoise) (ITS/Calib/SPD/FOEfficiency) AliITSFOGeneratorSPD AliITSFOsignalsSPD ( Stored in the sameDigits file) Ifraw data are simulated: AliITSFOsignalsSPD are propagatedto the data word as FO bit In realraw data : FO bits in raw data file carry information on firedchips A. Mastroserio - Weekly Offline meeting

  5. Pixel Trigger Conditions - Transfer Scheme RO Electronics Fast-OR Signals CTP Inputs OCDB ECS SOR, run number Pixel Trigger System (PIT) CTP Trigger conditions (Text Format) DCS FXS Offline network Trigger conditions (OCDB Format) Shuttle Trigger Preprocessor AliITSTriggerConditions(ITS/Calib/PITConditions) Slidesfrom H. Tydesjovailable at http://amastros.home.cern.ch/amastros/doc/PitOffline/ 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=123456 PROCESSING_FIRMWARE_VERSION =1 INPUT_CONDITIONS_VERSION =0 PARAMETERS_VERSION =0 VERSION_REGISTER_VALUE =264 GLOBAL_DESCRIPTION = 'Firmware implementing Pixel Trigger multiplicity algorithms' [Outputs] # Lines describing the algorithms implemented on the Pixel Trigger outputs by the active firmware 0 = '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', valueN 0 = '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 = 0000000001 0,A,0=0000000000 #(not plugged) 0,A,1=0000000000 #(not plugged) 0,A,4=0000000000 #(not plugged) […..] brandnewTrigger conditionstxt file @ DSF from Cesar Algorithms Parameters Activechips A. Mastroserio - Weekly Offline meeting

  7. PIT conditions in OCDB (->tobeupdated) root [1] c = (AliITSTriggerConditions *)AliCDBEntry->GetObject() (classAliITSTriggerConditions*)0x11021c0 root [2] c->DumpAll() [Header] RUN_NUMBER = 0 PROCESSING_FIRMWARE_VERSION = 0 GLOBAL_DESCRIPTION = conditionsgenerated offline VERSION_REGISTER_VALUE = 0 INPUT_CONDITIONS_VERSION = 0 PARAMETERS_VERSION = 0 [Outputs] 11 = 'SPD_GFO_L0', 'geometrytriggers' 12 = 'SPD_HMULT_L0', 'multiplicitytriggers' [Output_parameters] 11 = 'total_threshold', 1; 12 = 'total_threshold', 150; [Active_chips] root [3] c->GetNumAlgo() (constunsigned short)2 A. Mastroserio - Weekly Offline meeting

  8. OCDB PIT simulation AliITSTrigger(procedure performedbyAliITSTriggerFOProcessor) AliITSFOsignalsSPD AliITSTriggerConditions(ITS/Calib/PITConditions) TObjArray AliITSTrigger AliTriggerInput AliITSTriggerFOProcessor AliTriggerInput AliCentralTrigger AliTriggerInput Trigger Inputs take into account inactivechips A. Mastroserio - Weekly Offline meeting

  9. Fast-OR Bits - Reconstruction OCDB Digits Raw Data AliITSFOSignalsSPD FO Bits AliITSClusterFinderV2SPD AliITSTriggerConditions(ITS/Calib/PITConditions) AliITSDetTypeRec Remove in-active chipsfrom fast-or fired map Fast-OR Fired Map ESD AliMultiplicity A. Mastroserio - Weekly Offline meeting

  10. PIT simulationsummary • Preliminaryversion in svn • FO fired chip maps are ok. • Default settingsretrievesameoutputs in simulation and reconstructionfrombothDigits or raw data (simulated)) • Consistencyifapplying FO efficiency and noise • To Do list • PIT conditionstobeupdated • Introductionof0SCO algorithm(= cosmic trigger) • Code tocreate OCDBobjectfrom PIT conditionstxt file (on svn once the frameworkisdeveloped) A. Mastroserio - Weekly Offline meeting

  11. ….somecomments… • CTP inputsconsider FO signalswithoutinactivechips, butifDigits are not “dead pixel aware” the FO signals are overestimated • Ifsimulated FO signals are builtstartingfrom a specific dead/noisy pixel configuration and OCDB objectschangefor SPD, then the full simulationshouldberunagaintoretrieveconsistent trigger outputs. • Givensuch a scenario, MC production can consideronly onespecific SPD configuration A. Mastroserio - Weekly Offline meeting

  12. 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) Trigger meeting / CERN 13.5.2009

  13. Extra slides A. Mastroserio - Weekly Offline meeting

  14. Scenario A Scenario B Equipment forDigits IdealEquipmentforDigits dead HS FO signals ‘ FO signals Inactivechipsremoval Inactivechipsremoval New FO signals ‘ New FO signals CTP inputs CTP inputs SPD Digits (simulatedfiredpixels) can beawareof dead / noisypixels . SPD clustersare alwaysawareofboth. Possibleclusters/FO mapsinconsistencyifusers do notknowhow the simulationhasbeenperformed. A. Mastroserio - Weekly Offline meeting

  15. List of Algorithms • I := number of active FO on Inner layer • O := number of active FO on Outer layer Implement algorithmsfor each label in AliITSTriggerFOProcessor A. Mastroserio - Weekly Offline meeting

  16. Pixel Trigger Simulation Scheme TObjArray AliTriggerInput AliTriggerInput OCDB AliTriggerInput Raw Data Digits AliITSFOSignalsSPD FO Bits AliITSFONoiseSPD(ITS/Calib/SPDFONoise) AliITSFOEfficiencySPD(ITS/Calib/SPDFOEfficiency) AliITSTriggerConditions(ITS/Calib/PITConditions) AliITSDetTypeSim AliITSTrigger AliITSsimulationSPD AliITSTriggerFOProcessor AliITSFOGeneratorSPD AliCentralTrigger AliITSDDLRawData A. Mastroserio - Weekly Offline meeting

More Related