ALICE Trigger and Event Selection QA

Size: px

Start display at page:

Download "ALICE Trigger and Event Selection QA"

Solomon Francis Edwards
8 years ago
Views:

1 ALICE Trigger and Event Selection QA By: August 9, Michigan REU Student Program Final Presentations 1

2 ALICE A Side C Side Credit: CERN 2

3 Min Bias Trigger Detectors CINT1 Suite = Min Bias Trigger CINT7 Suite = VZERO AND Trigger CINT8 Suite = T0 AND Trigger VZERO A Other rare triggers are used, e.g. EMCal and PHOS, but not used for the purpose of this analysis (only muon production for Period LHC12c) VZERO C T0A T0C SPD 3 Credit: ALICE-TDR-011

4 Physics Selection (PS) PS validates online trigger conditions and rejects background, used offline before any analysis ALICE, due to various reasons (defocused beams, the vacuum, and long time integration window of TPC), has significantly worse signal-to-background ratio than the other LHC experiments Stricter event selection by computing the timing of a signal that passes the triggers to ensure that the event passed occurred at the vertex of ALICE (through the VZERO or T0) Need a high quality data set to do analysis, therefore need to reject background and save actual collisions with high efficiency Use Quality Assurance (QA) to trend the PS to spot bad runs, monitor beam conditions, and reject clear outliers in analysis 4

that passes the triggers to ensure that the event passed occurred at the vertex of ALICE (through the VZERO or T0) Need a high quality data set to do analysis, therefore need to

5 ALICE Physics Selection Quality Assurance (PSQA) Old PSQA done primarily by hand, not automatic Old PSQA needed streamlining and did not meet proper coding conventions Built a new class to automatically generate text output per run to be used for newly designed online interface Same class generates ROOT output of trending QA with TGraphErrors Built a separate class to handle visualization of run by run trending 5

generate text output per run to be used for newly designed online interface Same class generates ROOT

6 QA Example: Quick Notes Plots Naming Convention: Trigger Class Name [Fast or Regular] Trigger Logic # Error bars on plots are smaller than the point size due to zoomed out scale. For ratios that were complete subsets, used binomial errors for error calculation Otherwise, for uncorrelated ratios, used normal error propagation The following plot is an example of data taking period LHC12c (May-June 2012) for a given trigger class (in this case, kmus7) 6

For ratios that were complete subsets, used binomial errors for error calculation Otherwise, for uncorrelated

Accepted/All High BG Run hidden by V0A/All Zoom in for example Special note: Only runs 179678 and

7 Accepted/All High BG Run hidden by V0A/All Zoom in for example Special note: Only runs and use both CINT7 and CINT8. kmus7: Muon trigger; low p T single muon, offline V0 selection, CINT7 suite 7

8 As kmus7 is a CINT7 trigger (V0 AND), V0A sits opposite muon arm, and explains why Acc/All is close to V0A/All. In the same way, V0A/All and Acc/All inversely proportional to V0A BG/All. 8

9 V0A/All Acc/All inversely proportional to V0A BG/All kmus7: Muon trigger; low p T single muon, offline V0 selection, CINT7 suite 9

10 Online Interface: Workflow PS: Trigger Class [Regular or Fast] Trigger # : Name of Plotted Ratio, Value, Error PS: "kmush7 [Regular] Trigger 3":Accepted/Trigger_class, ,

11 Online Interface: Snapshot Note: This is only a preliminary example. All plots produced by the QA run will be instantly viewable on the web. 11

12 Summary 1. New AliPSQA class can produce a ROOT file with TGraphErrors that can then be visualized via the AliPSQAVisualization class. 2. PSQA can be performed automatically by setting just a few input and output parameters. AliPSQA produces text files per run that are automatically processed into trending plots on MonALISA, for immediate access for all ALICE members. 3. Trending plots can easily identify runs that are clear outliers to be rejected for data analysis in a given period. 4. When AliPSQA is used in conjunction with run data, trending details are easily understandable. 5. Results of data taking period LHC12c were presented in ALICE official QA meeting. 12

AliPSQA produces text files per run that are automatically processed into trending plots on MonALISA, for immediate access for all ALICE members. 3.

13 Acknowledgements Advisors: Alexander Kalweit and Michele Floris Lab partner: John Groh Costin Grigoras Zaida Conesa Del Valle CERN, ALICE Collaboration, University of Michigan 13

14 Questions? 14

15 BACKUP SLIDES 15

16 Examples of V0 Timing Run: Production: ESD muons Trigger class: kmus7 16

17 Examples of V0 Timing Run: Production: ESD muons Trigger class: kmus7 17

18 Parameters for QA Runs Analyzed: , , , , , , , , , , , , , , , , , , , , , , , , , , Period: LHC12c 18

180110, 180127, 180129, 180130, 180131, 180132, 180158, 180177,

19 Parameters for QA Explanation of QA Data: Trigger class: Number of events in selected trigger class* Accepted: Accepted events V0A and V0C: Events with signal V0A/V0C in collision time window, recomputed offline over all slabs V0A BG and V0C BG: Events flagged as background from V0 T0: Events with T0 signal in collision time window, computed offline T0BG: Events flagged as background from T0 FO >= 1: Number of events with more than 1 chip hit in pixels, computed offline FO >= 2: Number of events with more than 2 chips hit in pixels, computed offline FO (L1) >= 2: Number of events with more than 2 chip hits in the outer layer of the SPD, computed offline Reference: *For the sake of this presentation, all plots with Trigger class are renamed in the legend with All. 19

T0 FO >= 1: Number of events with more than 1 chip hit in pixels, computed offline FO >= 2: Number of events with more than 2 chips hit in pixels, computed offline FO (L1) >= 2: Number of events with

20 QA Results kmush7: Muon trigger; high p T single muon, offline V0 selection, CINT7 suite 20

21 QA Results kmul7: Muon trigger; like sign dimoun, offline V0 selection, CINT7 suite 21

22 QA Results kmuu7: Muon trigger; unlike sign dimuon, offline V0 selection, CINT7 suite 22

23 QA Results Bad run: already flagged in RCT kmuonsinglelowpt8: Muon trigger; low p T single muon, offline T0 selection, CINT8 suite 23

24 removed. 24

25 Bad run kmuonsinglehighpt8: Muon trigger; high p T single muon, offline T0 selection, CINT8 suite 25

26 removed. 26

27 Bad run kmuonlikelowpt8: Muon trigger; low p T like sign dimuon, offline T0 selection, CINT8 suite 27

28 removed. 28

29 Bad run kmuonunikelowpt8: Muon trigger; low p T unlike sign dimuon, offline T0 selection, CINT8 suite 29

30 removed. 30

31 Online Interface: Parameters 31

32 Online Interface: Notes Class AliPSQA with PSQA.C produce output ROOT file with TGraphErrors and text files for MonALISA TGraphErrors can be visualized with PSQAV.C and AliPSQAVisualization class All cache/output directories made automatically if they do not exist List of trigger classes and partitions can be hardcoded, would require TString manipulation. Current limitations: Size of various data members must be changed by hand if number of trigger classes and/or trigger logic increases 32

Vertex and track reconstruction with the ALICE Inner Tracking System

Vertex and track reconstruction with the ALICE Inner Tracking System The 5th International Nordic "LHC and Beyond" Workshop St.Petersburg, 8-11 June 2010 Leonardo Milano Univ. & INFN, Torino for the ALICE