Monitoring Trigger Tracking Using Hlt Raw Data @ LHCb

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

0 comments

Post a comment

    Post a comment
    Embed Video
    Edit your comment Cancel

    Favorites, Groups & Events

    Monitoring Trigger Tracking Using Hlt Raw Data @ LHCb - Presentation Transcript

    1. PC L H C b farms Farmers: Chun-Min (Mindy) Jen & Tomasz Skwarnicki Syracuse U i S University, NY US it NY, 2/16/2009 Syracuse Uni.@LHCb by Mindy Jen 1 Tracking & Alignment Workshop
    2. Perform simple monitoring checks on tracking algorithms run in Hlt, based on information saved in Hlt Raw Data banks: Do not rely on the ability to rerun Hlt in offline (and getting all the same calibration and alignment constants) Not intend to eliminate the latter, but to complement it Need feedback from you: We are not tracking experts Will you find this kind of monitoring code useful? What kind of other checks/plots would you like to see? Your feedbacks are quite welcome!!! 2/16/2009 Syracuse Uni.@LHCb by Mindy Jen 2 Tracking & Alignment Workshop
    3. We W are interested i producing monitoring codes which can b run on i d in di ii d hi h be real data: No MC truth information Evaluate the trigger tracking with respect to offline tracks Such codes could be run in: Monitoring Farm (MF) t see th t th M it i F to that there i nothing unexpected h is thi t d happening i i in the Event Filtering Farm (EFF) In the true offline processing after better alignment constants are found to see hhow much worse on-line calibrations were h li lib ti TriggerTisTos tool Offline HltObjectSummaries Environment Online Environment RAW D t Data “READ” TES classes: Hlt RAW Banks HltSelReports HltDataSVC HltSelReports E F F HltDecReports M F HltDecReports “WRITE” WRITE HltVertexReports HltVertexReports 2/16/2009 Syracuse Uni.@LHCb by Mindy Jen 3 Tracking & Alignment Workshop
    4. HltSelReports Raw Bank and TES class contain relevant information for tracks We also use HltVertexReports when looking at the Impact Parameter (IP) resolution All reconstructed objects are saved as LHCb::HltObjectSummary class For “tracks”, HltObjectSummary contains: All LHCbIDs: We use these via TriggerTisTos tool to match trigger- and off-line tracks (more details later) Numerical information: on the FirstState in the single precision with no error matrices: We use these to compare with offline FirstState values (more details later) 2/16/2009 Syracuse Uni.@LHCb by Mindy Jen 4 Tracking & Alignment Workshop
    5. X , tx StdInfo: .firstState Y , ty Track LHCbIDs LHCbID X Z , q/P .position RecVertex Y .particleID.pid particleID pid Z .measuredMass X numericalInfo Particle .referencePoint Y .slopes How Large? Z 1/.p p Single Tracks Si l T k Hlt1 SubStructure RecVertex -- Multiple Tracks H gh t High Pt & H gh IP High Particles Proto-Particles Proto Particles Tracks Hlt2 2/16/2009 Syracuse Uni.@LHCb by Mindy Jen 5 Tracking & Alignment Workshop
    6. In the default mode HltSelReports contains only candidates selected by Hlt1 and Hlt2 Decision algorithms Hlt Raw Data size ~2 kB ( 5% of total event size) 2 (~5% We are working to see what can be accomplished from this information alone, but not yet in position to show anything useful Debug setting: Can save outputs from intermediate Hlt algorithms registered with HltDataSvc: Right now limited to all Hlt1 algorithms but can be extended to Hlt2 in the future Includes general track reconstructions: RZVelo, Velo, Forward1 Can be run pre-scaled in co-existence with the default mode: pre scaled co existence No big penalty in data storage Because of high trigger rate (2kHz) even heavy pre-scaling accumulates debug events quickly 2/16/2009 Syracuse Uni.@LHCb by Mindy Jen 6 Tracking & Alignment Workshop
    7. HltSelReports Raw Bank Size for “Forward1” & “StdInfo” (Info Level = 1) saved in “debug” setting Hlt Raw Data size ~8 5 kB ~8.5 (~21.25% of total event size) KB KB 2/16/2009 Syracuse Uni.@LHCb by Mindy Jen 7 Tracking & Alignment Workshop
    8. Today we will only show comparison between Hlt1 “Forward1” tracks and type=3 (i.e. Long) offline tracks from Rec/Tracks/Best Run on Minimum Bias events (DC06 data) and look only at events passing Hlt2. Run on ~3k events (~1.5s of data without pre-scaling the Debug mode). g ) Use HltObjectSummaries() method of the TriggerTisTos tool to obtain “TOS” trigger tracks for given offline tracks passed as “signal”: TOS criteria encoded in the TriggerTisTos tool: > 70% of hits on the trigger track must be among the offline-track hits. This has to be satisfied separately for VELO (vertex locator), OT (outer tracker) + IT ( inner tracker) and TT (tracker turicensis) (if any) 2/16/2009 Syracuse Uni.@LHCb by Mindy Jen 8 Tracking & Alignment Workshop
    9. X X Pt φ Z Proton beam Proton beam Y Z Transverse X-Y Plane Transverse Momentum Pt h/2 Azimuthal Scattering Angle φ σ 2/16/2009 Syracuse Uni.@LHCb by Mindy Jen 9 Tracking & Alignment Workshop
    10. Calculate IP with respect to a primary vertex (PV) using HltUtils::impactParameter (RecVertex,Track) Use primary vertices from HltVertexReports for ‘PV2D’ If more than one PV, choose the one that minimizes IP of the offline track. Create LHCb::Track f C t LHCb T k from the Fi tSt t i f on HltObj tS th FirstState info HltObjectSummary tto calculate IP of the trigger track with respect to the same PV. M Plot ΔIP = IPoffline-IPtrigger B Z Hlt N Flight Distance Secondary Vertex X Y B hits Impact Parameter ( ) (IP) γ μ ν P P Z Primary Vertex (PV) ( PP Collision/Interaction Point ) 2/16/2009 Syracuse Uni.@LHCb by Mindy Jen 10 W Tracking & Alignment Workshop
    11. IPmin Δ IP Primary Vertex (Collision Point) Proton beam Proton beam 2/16/2009 Syracuse Uni.@LHCb by Mindy Jen 11 Tracking & Alignment Workshop
    12. Δ 2/16/2009 Syracuse Uni.@LHCb by Mindy Jen 12 Tracking & Alignment Workshop
    13. 2/16/2009 Syracuse Uni.@LHCb by Mindy Jen 13 Tracking & Alignment Workshop
    14. All Offline Tracks With a Match to a Trigger Track ε of trigger tracking 2/16/2009 Syracuse Uni.@LHCb by Mindy Jen 14 Tracking & Alignment Workshop
    15. With a Match to a Trigger All Offline Track Tracks T k ε of trigger tracking 2/16/2009 Syracuse Uni.@LHCb by Mindy Jen 15 Tracking & Alignment Workshop
    16. All Offline Tracks ε of trigger tracking With a Match to a Trigger Track 2/16/2009 Syracuse Uni.@LHCb by Mindy Jen 16 Tracking & Alignment Workshop
    17. All Trigger Tracks With a Match to ε of offline tracking an Offline Track 2/16/2009 Syracuse Uni.@LHCb by Mindy Jen 17 Tracking & Alignment Workshop
    18. With a Match to an Offline All Trigger Track Tracks T k ε of offline tracking 2/16/2009 Syracuse Uni.@LHCb by Mindy Jen 18 Tracking & Alignment Workshop
    19. With a M t h Match to an Offline Track ε of offline tracking All Trigger Tracks 2/16/2009 Syracuse Uni.@LHCb by Mindy Jen 19 Tracking & Alignment Workshop
    20. Feedback welcome About things to look at and way to present Would monitoring Velo (RZVelo) with respect to offline tracks be useful? Should we use any cuts on offline tracks before using them? 2/16/2009 Syracuse Uni.@LHCb by Mindy Jen 20 Tracking & Alignment Workshop
    SlideShare Zeitgeist 2009

    + renjmrenjm Nominate

    custom

    199 views, 0 favs, 1 embeds more stats

    More info about this document

    © All Rights Reserved

    Go to text version

    • Total Views 199
      • 194 on SlideShare
      • 5 from embeds
    • Comments 0
    • Favorites 0
    • Downloads 0
    Most viewed embeds
    • 5 views on http://physmindy.blogspot.com

    more

    All embeds
    • 5 views on http://physmindy.blogspot.com

    less

    Flagged as inappropriate Flag as inappropriate
    Flag as inappropriate

    Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

    Cancel
    File a copyright complaint
    Having problems? Go to our helpdesk?

    Categories