Warning, /CondTools/Ecal/doc/ReprocessEcalPedestals.README is written in an unsupported language. File is not indexed.
0001 ReprocessEcalPedestals.cc README
0002 ================================
0003
0004 ReprocessEcalPedestals is a module for completing incomplete sets of
0005 pedestals from one tag and writing complete sets using
0006 channel-by-channel IOVs to another tag
0007
0008 On the first iteration the "append" parameter MUST be false. There
0009 should be an "endfile" parameter too. In this processing run, an
0010 object is fetched from the first run of the EmptySource. The
0011 number of SMs used in this object are counted, and based on this
0012 each cystal in each SM is checked to see if data is available. If
0013 data is not available, nominal values are filled in. Then the run
0014 is iterated and if there is a change of data from the source tag,
0015 the cached value is written with the IOV (till time) of the run
0016 just before the change. The newly fetched data is written to the
0017 cache, which already contains a complete set of pedestals so that
0018 if any runs are missing from this set the values from the previous
0019 object are used. Again, every time a new object is fetched from
0020 the source tag, the cached object is written to the target tag.
0021 When all the runs are finished, the cached object is written to the
0022 target tag with an infinite IOV and the cache is dumped to the
0023 "endfile"
0024
0025 When further pedestal objects are available for reprocessing, this
0026 module should be run with the EmptySource specifying to start at
0027 one greater than the run the last reprocessing finished on.
0028 "append" should be true, and both "startfile" and "endfile" should
0029 be provided, with "startfile" being the "endfile" of the previous
0030 reprocessing. "startfile" will be loaded into the cache before any
0031 pedestals are fetched from the source tag. In this way, if the
0032 very first object is missing channels the channels from the
0033 previous IOV will be used ("endfile" from before) instead of
0034 nominal values. Reprocessing happens the same as before with each
0035 change of object in the source tag resulting in the cached object
0036 being written to the DB.
0037
0038 test/test_reprocess_1.cfg shows an example of a first-time reprocessing
0039 test/test_reprocess_2.cfg shows an example of a subsequent reprocessing