 |
 |
Jeremy, Yes, first is to 100% confirm that (x,y)<->channel_id<->FADC(crate,slot,channel) are absolutely correct in the db. I already did this before Thanksgiving, and the convention you posted last week is the same as I used at that time, but apparently there is a possibility there is a mistake somewhere and it needs to be done again. If you can do it that would be great. -Nathan On Dec 8, 2014, at 1:41 PM, "McCormick, Jeremy I." <[log in to unmask]> wrote: > Hi, Nathan. > > Today I'm going to work on better integrating user selected run numbers and conditions configuration into the monitoring app. I hope to have that completed by the end of the week at the latest. This should allow one to easily select and "freeze" a run number for the monitoring session through the GUI rather than the XML steering file. > > I also think we should work on getting better calibrations (pedestals and noise) into the database. What is in there for the JLab database I think has mismatched channel numbers and so should probably just be replaced. Do you want me to just do this? It seems like maybe that would be most efficient at the moment, since I know the procedure best. I have an LCSim Driver that I can run which will generate what I think are adequate calibration values by crystal for a run. At least, I'm using these calibrations successfully for my own analysis on the cosmic data. The question would be whether we want a "default" conditions set for the calibrations that covers run 2000+ in general or individual runs. I'm not really sure if there is any significant pedestal drift such that we would need individual run calibrations. You said no, but we should verify this. > > Currently, the conditions system doesn't handle overlapping conditions sets all that well so if we put in a multi-run conditions set along with individual runs it might break things, though it shouldn't be too hard to fix this so it picks one. (Probably the one with the latest date would be an okay default.) > > Thanks. > > --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