I've been looking into the run variable in various places - Essentially I wanted it accessible via the FLOW + CAF files, such that we can tell Event 5 in 2 files are different, to make debugging events simpler - either analysers looking into their selection, or reco people looking into weird artifacts.
I can't see the run info being set in the FLOW files at all, but I've not managed to track that down yet (I could also just be missing it in the HDF5 file, there is a fairly large number of values...). It is of course set correctly in the spill builder, so it seems to go wandering between those two places. I'll update if I find where exactly. (This was looking at 5P1 FLOW files - If some newer files are accessible outside NERSC I can also check them).
I can see many values of it in the CAFs, but they are seemingly all set to 1 or -1. I have checked meta.run, and the various values of cafTree.rec.meta.XXX.run. -1 seems to be the default value, and the single 1 seems to be set based on the default value in the NDCAFMaker.fcl, which is not overwritten by gen_cafmaker_cfg.py. (This is looking at the 5P3 files from the "homework" for the LBL/ND July 26 Workshop).
It would be good to get it fully hooked up, such that when analysers say "The result is weird I wonder why", we can look into individual events.
I've been looking into the
runvariable in various places - Essentially I wanted it accessible via the FLOW + CAF files, such that we can tell Event 5 in 2 files are different, to make debugging events simpler - either analysers looking into their selection, or reco people looking into weird artifacts.I can't see the run info being set in the FLOW files at all, but I've not managed to track that down yet (I could also just be missing it in the HDF5 file, there is a fairly large number of values...). It is of course set correctly in the spill builder, so it seems to go wandering between those two places. I'll update if I find where exactly. (This was looking at 5P1 FLOW files - If some newer files are accessible outside NERSC I can also check them).
I can see many values of it in the CAFs, but they are seemingly all set to 1 or -1. I have checked
meta.run, and the various values ofcafTree.rec.meta.XXX.run.-1seems to be the default value, and the single1seems to be set based on the default value in theNDCAFMaker.fcl, which is not overwritten bygen_cafmaker_cfg.py. (This is looking at the 5P3 files from the "homework" for the LBL/ND July 26 Workshop).It would be good to get it fully hooked up, such that when analysers say "The result is weird I wonder why", we can look into individual events.