Still waiting are updates from Zach affecting CAL and Trigger, Martin's changes to Trigger and Michael's update to GlastRandomSvc as discussed last week. Since Michael is out of town Toby has volunteered to look it over and verify it's ready to be promoted.
(Toby) raised the subject of celestial sources. It's somewhat disconnected from GR code generally, but we do need it and it's not easy to keep it in sync with what ScienceTools is using. (Richard) We won't need a new sky model for about a month.
(Toby) We also need to be thinking about incorporating Bill's new stuff. It affects at least AnalysisNTuple and probably some additional packages.
We can use v13r1p1 for initial muon run and sample run but would like the GEM mods for the background run. There will be two significant changes to backgrounds: 1) new neutron component and 2) modified geomagnetic cut-offs. And we need to decide what to do about Earth10. (Toby) Note the new magnetic latitude calculation is unsigned; this will affect anyone binning this quantity.
Do we need the CAL and SVAC tuples? They're very large. If we do, Tom will have to arrange for them.
Would like to make use of CELs for Interleave output, which means the CEL code needs to be fully verified and ready to go in about a month.
FastMon guys (from C & A) have provided a tool for diagnostic plots. It was already used for digi and recon monitoring; will now extend to MC.
Resources Richard has requested a double size batch allocation for the next few weeks; no answer yet. However on the definite plus side, Tom and Claudia have got the Pipeline running in Lyon! There are just a few remaining details to be handled, such as fetching log files back to SLAC.
As far as I can tell there is no standard system sleep routine; unix has a couple and Windows has something different. As a first step in implementing the retry scheme above I propose to make a wrapper in facilities::Util like this:
void Util::gsleep(unsigned milli)
previous | minutes index | next |