We're hoping for the extra core allocation to speed up the runs; also Lyon is nearly ready to go.
(Heather) Is the new once-per-run random seed setting in job options? (Richard) Not yet. That needs to be tried. (Toby) Once it's been tested, code should be changed to make it the default.
Experimentally, it seems that requested meta ROOT files are not created unless there is something to put in them - in contrast to other ROOT files which seem to be created even if they end up with zero length. The problem is the staging code expects there to be a file if one is requested (I cannot think of a reliable way to inform the staging code that a particular output file is "optional" or that "we just didn't get one this time" without throwing an exception).
For the moment, we will simply disable the meta ROOT files altogether (they purportedly contain junk in this GlastRelease). Heather is, I think, looking into the possibility of making the meta ROOT output consistent with other ROOT file output.
A new skimmer release has been installed. It can now skim cal/svac/gcr tuples, and in theory you can also use those tuples for the definition of the cut (and not only for the merit tuple). Some low levels tests have been applied, but I am searching for and will support users who could try it with true data. This implies the use of the command-line interface. The web front-end should be upgraded in the coming weeks.[and for this further elucidation from Igor:]
I will upgrade the front end of the skimmer in the next release. This will happen probably just after New Year, given the shutdown and new, not-tested-enough architecture.
Batch submission for the new RM is now in test; it looks ok so far.
Should we move to SLAC's centrally-supported installation of MySQL? There are advantages: for example, they would handle back-ups. He would like a decisition soon. (Richard) The SCS-maintained MySQL dbs will be blocked at the firewall, so probably not suitable for calibration database and MOOT, but ok for RM. (Navid) Installer needs to work through the firewall [command line installer only, I think; gui doesn't talk to db directly.] (Bryson) elogbook needs MySQL 4. (Navid) Central installation offers both 4 and 5, but his preference would be to convert elogbook to use 5 anyway. It is the recommended release and at some point MySQL Central will stop supplying security patches for version 4.
previous | minutes index | next |