Difference between revisions of "GlueX Level-3 Trigger Meeting, Jun 10, 2016"
From GlueXWiki
Line 65: | Line 65: | ||
=Minutes= | =Minutes= | ||
− | + | Attendees: David L., Adesh S., Mike W., Cristiano F., Sean D. | |
+ | |||
+ | == EVIO Parsing == | ||
+ | * David Showed some benchmarking results for the EVIO parsing code with various levels of associated object linking enabled | ||
+ | * Mysterious rate drop observed when no linking is done from 12kHz to 8kHz. | ||
+ | * Mike noted that they had to empirically determine the optimal number of threads for the LHCb HLT | ||
+ | * David will work on mapping our the performance for various settings in the parsing threads and processing threads (benchmarking was always done with both set to 32) | ||
+ | |||
+ | == sim-recon algorithm benchmarking == | ||
+ | * Cristiano continues to work on mapping the performance of various algorithms using janadot | ||
+ | * Some discrepancies between real data and simulated data performance | ||
+ | * Will look into effect of LED triggers on results (particularly time spent matching tracks to calorimeter clusters) | ||
+ | * Sean noted that there are lots of PS triggers in the real data that should be filtered | ||
+ | |||
+ | == Simulation == | ||
+ | * Adesh is currently running 10M bggen events with incident γ energy down to %pi; threshold (global use sim1 data set only goes down to 3GeV) | ||
+ | * Farm jobs expected to be done by Monday morning | ||
+ | * Size of REST files produced is about 10 times smaller than "normal" | ||
+ | ** Justin told Adesh this is expected due to the dominance of low energy events | ||
+ | * Wiki documentation is forthcoming |
Revision as of 10:00, 16 June 2016
Contents
Meeting Info.
Meeting Time And Location
11:00 EST (JLab time)
CC F326-327
Connecting
You can connect using BlueJeans Video conferencing (ID: 198 332 417). (Click "Expand" to the right for details -->):
- Make sure you have created a BlueJeans account via your JLab CUE account using this link:
- http://jlab.bluejeans.com (You should only need to do this once)
- Meeting ID: 198 332 417
- (you may need to type this in, depending how you connect)
- If connecting via Web Browser: click this link (no passcode is needed):
- If connecting via iOS or Android App:
- Use your JLab e-mail address to log in and then enter the meeting ID given above to join the meeting
- If connecting via Phone: Dial one of the following numbers and then enter the meeting ID above and hit "#" or "##"
- Dial: 1 888 240 2560 (US or Canada only)
- or, List of International Numbers
- If connecting via Polycom unit:
- Dial 199.48.152.152 or bjn.vc
- Enter meeting ID above
Background Information
(Click expand for some links to background information -->)
Informational Links:
Justin's collaboration meeting talks:
Agenda
- Announcements
- Previous Meeting (May 27, 2016)
- EVIO Parsing
- Benchmarking status
- Simulation Status
- AOT
Minutes
Attendees: David L., Adesh S., Mike W., Cristiano F., Sean D.
EVIO Parsing
- David Showed some benchmarking results for the EVIO parsing code with various levels of associated object linking enabled
- Mysterious rate drop observed when no linking is done from 12kHz to 8kHz.
- Mike noted that they had to empirically determine the optimal number of threads for the LHCb HLT
- David will work on mapping our the performance for various settings in the parsing threads and processing threads (benchmarking was always done with both set to 32)
sim-recon algorithm benchmarking
- Cristiano continues to work on mapping the performance of various algorithms using janadot
- Some discrepancies between real data and simulated data performance
- Will look into effect of LED triggers on results (particularly time spent matching tracks to calorimeter clusters)
- Sean noted that there are lots of PS triggers in the real data that should be filtered
Simulation
- Adesh is currently running 10M bggen events with incident γ energy down to %pi; threshold (global use sim1 data set only goes down to 3GeV)
- Farm jobs expected to be done by Monday morning
- Size of REST files produced is about 10 times smaller than "normal"
- Justin told Adesh this is expected due to the dominance of low energy events
- Wiki documentation is forthcoming