Difference between revisions of "GlueX Level-3 Trigger Meeting, May 27, 2016"
From GlueXWiki
Line 64: | Line 64: | ||
=Minutes= | =Minutes= | ||
− | '' | + | Attendees: David L. (chair), Simon T., Adesh S., Sean D., Mike W., Cristiano F., Justin S., Curtis M. |
+ | |||
+ | == Benchmarking Status == | ||
+ | * Cristiano has started using the ''janadot'' plugin to look at benchmarking various factories using recent data | ||
+ | * David continues work on new event parser | ||
+ | ** Factor of 4 speedup occurs in parsing code if linking of associated object is turned off | ||
+ | ** Some options for optimization there including replacing associated object linking with copying the few needed relevant parameters | ||
+ | |||
+ | == Simulation Status == | ||
+ | * Adesh spoke with Mark I. and concluded that the sim1 run has significant differences from the target priority data set | ||
+ | * This is in addition to the much higher photon energy threshold needed for L3 trigger studies | ||
+ | * Adesh will start producing a dedicated L3 simulated dataset next week. Asked if Justin had any guidance as to how much would be needed | ||
+ | ** Justin suggested starting with 10M events and going down to the 2π production threshold in photon energy | ||
+ | * Sean asked if we could think of any features that could be added to mcsmear that would help with the L3 simulation studies | ||
+ | ** No specific suggestions were given, but we will think about it offline and convey anything we come up with to him offline. He is currently undergoing a significant rewrite of mcsmear so now would be the best time to get additional features put in |
Revision as of 12:04, 27 May 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 19, 2016)
- Benchmarking status
- Simulation Status
- AOT
Minutes
Attendees: David L. (chair), Simon T., Adesh S., Sean D., Mike W., Cristiano F., Justin S., Curtis M.
Benchmarking Status
- Cristiano has started using the janadot plugin to look at benchmarking various factories using recent data
- David continues work on new event parser
- Factor of 4 speedup occurs in parsing code if linking of associated object is turned off
- Some options for optimization there including replacing associated object linking with copying the few needed relevant parameters
Simulation Status
- Adesh spoke with Mark I. and concluded that the sim1 run has significant differences from the target priority data set
- This is in addition to the much higher photon energy threshold needed for L3 trigger studies
- Adesh will start producing a dedicated L3 simulated dataset next week. Asked if Justin had any guidance as to how much would be needed
- Justin suggested starting with 10M events and going down to the 2π production threshold in photon energy
- Sean asked if we could think of any features that could be added to mcsmear that would help with the L3 simulation studies
- No specific suggestions were given, but we will think about it offline and convey anything we come up with to him offline. He is currently undergoing a significant rewrite of mcsmear so now would be the best time to get additional features put in