bryngemark

Results 32 issues of bryngemark

**Is your feature request related to a problem? Please describe.** _Ex. I'm always frustrated when [...]_ ... I try to set something basic like the input collection or input pass...

enhancement
cleanup

**Is your feature request related to a problem? Please describe.** When including vertical bars in some TS geometries, with the new way of attaching sensitive detector volumes (not in the...

trigscint

In the process of ntupling TS collections, I noticed that the functionality of propagating which pad we're on outside of collection names has fallen out in the RecHitProducer: it's simply...

enhancement
trigscint

Currently, the QIE digi code assigns a time stamp to hits which is based on allowing time` t=0` at the start of the first sample out of five, effectively adding...

trigscint

This is an old thing. There is no check in the cluster producer that input digits are actually there, causing it to segfault on occasion. There has also been a...

trigscint

When we designed the first TS digi (in effect, just a sim hit reconstruction layer), we introduced a variable `beamEfrac` to keep track of which fraction of a hit's energy...

trigscint

- the pad default naming has changed so helper function code (in util) needs to be able to deal with setting the collection name - reformatting from event aligned data...

trigscint

In the testbeam data analysis development, we used a separate path for hit and cluster reconstruction (with producers called `TestBeamHitProducer...` etc) compared to in the usual LDMX simulations. It would...

trigscint

**Is your feature request related to a problem? Please describe.** @joyang8caltech has been making standalone Geant4 simulations of a LYSO target geometry, but this won't tell us how a LYSO...

enhancement
help wanted
new detector

**Is your feature request related to a problem? Please describe.** Whenever we change the beam energy, a whole set of filter and biasing thresholds need updating. This is a lot...

cleanup
config