Hi,
when you refer to "energy calibration in <MeV * ADC >", do you mean
something like:
- The average cosmic deposition in a crystal is 15 MeV
- Cosmic signals were measured by the FADC in a xxx samples window
width, raw mode. Each of the xxx samples is reported in FADC units (12
bits on 1 V)
- The integration is performed offline, by summing these xxx samples, so
that each signal results in an integral, still in FADC units ("integrated")
- The distribution of FADC integrals was fitted by a Landau distribution.
- The MIP peak was evaluated to be at yyy FADC integrated units.
The conversion factor is then:
Signal(MeV) = Signal(FADC integrated units) * 15 MeV / yyy
Does this make sense?
Andrea
Il 12/12/2014 02:38 AM, McCormick, Jeremy I. ha scritto:
> Hi,
>
> re: conditions
>
> Nathan and I are in the process of loading conditions into the db for the ECAL. We were working on this today...
>
> We have a known good channel map.
>
> Calibrations (pedestal + noise) and gains should be in there soon if not already for a multi-run range covering the Engineering Run.
>
> Nathan indicated that the energy calculation is <MeV * ADC> so we need a Driver that makes the CalHit objects according to that formula. He is going to load gains into the conditions db for that calculation.
>
> —Jeremy
>
> On Dec 11, 2014, at 5:30 PM, Graham, Mathew Thomas <[log in to unmask]> wrote:
>
>> Thanks for the update. Looks like there are some other issues too re: kyle’s latest email.
>>
>> On Dec 11, 2014, at 8:29 PM, Sho Uemura <[log in to unmask]> wrote:
>>
>>> Andrea wrote the EVIO-LCIO conversion and the raw hit-CalorimeterHit conversion code for mode 7. It works, though it hasn't yet been tested on real (not LED) data or with good pedestals.
>>>
>>> But it's not written using LCIO objects, so it needs to be rewritten - otherwise people will run into problems with analysis down the road, and it will be impossible to make mode 7 work in MC. I'm doing a rewrite to fix that. Should be quick, might do it today, will definitely do it tomorrow.
>>>
>>> In short, the classes exist for the monitoring app and one-step EvioToLcio jobs (doing EVIO-LCIO conversion and hit recon in one step, not relying on raw hits being written to LCIO) to use this data. I don't know whether there are good conditions yet, and that might be the blocker.
>>>
>>> On Fri, 12 Dec 2014, Graham, Mathew Thomas wrote:
>>>
>>>> So, do we have the data classes to read this out yet? What?s the plan?
>>>>
>>>> Begin forwarded message:
>>>>
>>>> From: Nathan Baltzell <[log in to unmask]<mailto:[log in to unmask]>>
>>>> Subject: data with beam
>>>> Date: December 11, 2014 at 5:31:33 PM EST
>>>> To: HPS-SOFTWARE <[log in to unmask]<mailto:[log in to unmask]>>
>>>>
>>>> Hi Everyone,
>>>>
>>>> Run 3183 has some first data with beam (no target) if anyone wants
>>>> to take a look. It's on tape and on disk at:
>>>>
>>>> /volatile/hallb/hps/data/notgt
>>>>
>>>> See log entry:
>>>> https://logbooks.jlab.org/entry/3312822
>>>>
>>>> -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
>>>>
>>>>
> ########################################################################
> 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
