To connect via Zoom: Meeting ID 831-443-820
(See instructions for setting Zoom default to join a meeting with audio and video off: https://larsoft.org/zoom-info)
PC, Mac, Linux, iOS, Android: https://fnal.zoom.us/j/831443820
Phone:
https://fnal.zoom.us/zoomconference?m=SvP8nd8sBN4intZiUh6nLkW0-N16p5_b
H.323:
162.255.37.11 (US West)
162.255.36.11 (US East)
213.19.144.110 (EMEA)
See https://fnal.zoom.us/ for more information
At Fermilab: WH2NW (Black Hole)
Minutes for LArSoft coordination meeting on Jan 29, 2019
Present | Vito Di Benedetto, Lynn Garren, Herb Greenlee, Kyle Knoepfel, Saba Sehrish, Erica Snider|
Remote | Katherine Lato, Paul Russo, Tracy Usher, Anna Mazzacane, Hannah Rogers |
Release and Project status report [Erica Snider]
Conclusion:
Space Charge Implementation [Hannah Rogers]
Conclusion:
Avoid discarding createEngine's returned reference, or "Down with art's getEngine". [Kyle Knoepfel]
art provides RandomNumberGenerator service
Explanation of Proposal: RandomNumberGenerator::getEngine() is confusing and hard to use properly because it uses the concept of “current module†which is confusing when it is used in a library function that is not directly part of any art module. The concept of "current module" is more confusing when multi-threading is being used and multiple events are being processed on different schedules, in that case you can only talk about the of a schedule, and the getEngine() function needs to be told which schedule you are referring to.
The preferred use pattern is to save the returned value from createEngine() as a data member of your class and replace all uses of getEngine() with references to that new data member.
Conclusion: