Difference between revisions of "Tegan's HDGEANT and mcsmear questions"
From GlueXWiki
(→New code) |
|||
| Line 1: | Line 1: | ||
= New code = | = New code = | ||
| + | *What should the nominal overbias and temperature be? I've been working under the assumptions of 1.0 V OB and 10 degrees C. | ||
| + | * Electronic noise/dark hit smearing done with pedestal widths studied recently. | ||
| + | **These were single-sample widths. Do we want to emulate the f250 ADC pedestal algorithm instead (average of four samples)? | ||
| + | **Single sample widths are around 1.2 channels. f250PulsePedestal data output gives about 0.9 channel pedestal widths. | ||
* Poisson statistics smearing still needs a value for the energy of one dark hit. | * Poisson statistics smearing still needs a value for the energy of one dark hit. | ||
**Elton: 0.31 MeV, deposited at the center of the module, per pixel fired. For 10 degrees, 1.0 V OB, and attenuated to the end of the module, 0.11 MeV or so. This is [current code value]/6. | **Elton: 0.31 MeV, deposited at the center of the module, per pixel fired. For 10 degrees, 1.0 V OB, and attenuated to the end of the module, 0.11 MeV or so. This is [current code value]/6. | ||
Revision as of 10:45, 7 May 2015
New code
- What should the nominal overbias and temperature be? I've been working under the assumptions of 1.0 V OB and 10 degrees C.
- Electronic noise/dark hit smearing done with pedestal widths studied recently.
- These were single-sample widths. Do we want to emulate the f250 ADC pedestal algorithm instead (average of four samples)?
- Single sample widths are around 1.2 channels. f250PulsePedestal data output gives about 0.9 channel pedestal widths.
- Poisson statistics smearing still needs a value for the energy of one dark hit.
- Elton: 0.31 MeV, deposited at the center of the module, per pixel fired. For 10 degrees, 1.0 V OB, and attenuated to the end of the module, 0.11 MeV or so. This is [current code value]/6.
- The change to the data structure will be just adding 'incident_id="int"' to 'bcalTruthHit.'
- Should we also add EUP/EDN, tUP/tDN to the data structure?
- If we do not, we'll have to grab C_EFFECTIVE and ATTEN_LENGTH from the ccdb in mcsmear instead of doing it in hdgeant like usual.
- I've changed the data structure and tested the output of the new code. With the old code, a hit would be up to 1 GeV or so, usually around 50 - 300 MeV.
- With the new code, I'm seeing numbers like 0.1 - 5 MeV. I'm trying to figure out where in the code I might have messed up.
Old code
- We need to decide whether or not we want to keep this method available for people to choose to use.
