Hi Everyone,
I wrote a preliminary running pedestal average for mode-7 data. For the moment I just added it
to EcalRawConverter for testing in my local build because that's where the pedestal subtraction
is done and I saw direct access to the raw data, but maybe it should go somewhere else. For
example, we want to be able to plot the time-dependence of this running pedestal in the
monitoring-app too. And maybe also persisted in LCIO? From a design standpoint, should it
instead be in the ecal-conditions class (although that looks like all static stuff from the db now),
or its own new class, or else? I'm still getting familiar with this framework ….
-Nathan
########################################################################
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
|