 |
 |
Nathan and Kyle, The code that does the trigger verification would need to be modified to make use of these new conditions. What would be the best way to fill the conditions tables? The monitoring code should probably pick up the values automatically from the EVIO banks, if possible. That will avoid errors when the trigger is changed but the database is not also updated. Alternatively, we can have a small utility that uploads the values to the DB, and whoever changes the trigger settings will need to remember to run this utility as well. Best, Maurik > On Mar 5, 2015, at 4:10 PM, McCormick, Jeremy I. <[log in to unmask]> wrote: > > Hi, > > As per discussion in the software meeting this morning, I have made new conditions tables for the ECAL hardware gains and calibrations, so that they can be managed separately from the existing analysis-based/offline conditions. This also means that both types of conditions can be loaded simultaneously in the same job without interfering with each other. > > There is a test in HPS Java which shows how to read these collections from the database ... > > conditions/src/test/java/org/hps/conditions/ecal/EcalHardwareConditionsTest.java > > Basically, you would use the following code to get the hardware calibration collection .... > > EcalCalibrationCollection calibrations = manager.getConditionsData(EcalCalibrationCollection.class, "ecal_hardware_calibrations"); > > And this code would get the gains ... > > EcalGainCollection gains = manager.getConditionsData(EcalGainCollection.class, "ecal_hardware_gains"); > > The classes used for gains and calibrations are the same as before, but there is now an entirely separate table for the hardware values. > > Currently, there are only "run 0" collections in the database for these conditions, which have the gains set to 1.0, pedestals to 120, and the noise to 10. Actual hardware conditions will need to be loaded into the database now. (I think Nathan is planning to do this.) > > I hope that's clear. Let me know if you have any questions. > > --Jeremy > > ######################################################################## > Use REPLY-ALL to reply to list > > To unsubscribe from the HPS-SOFTWARE list, click the following link: > https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=HPS-SOFTWARE&A=1 ######################################################################## Use REPLY-ALL to reply to list To unsubscribe from the HPS-SOFTWARE list, click the following link: https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=HPS-SOFTWARE&A=1