-
I would like to include a new submodule `Trigger` in ldmx-sw. The submodule would include sub-directories for two types of algorithm implementations. The first is pure software, which can be compile…
-
By default, we are only including entries that are interesting for electrons and photons. This leads to most entries in the particle tables to be marked as "unkown" which has caused confusion for some…
-
**Describe the bug**
After having a succesful build and upload of #65 I tried running
```
ldmx use dev iss65-split-packages
Digest: sha256:ceea385c30998e97d04d44fa681584c942e3a5f88895308c84eca430…
-
**Describe the bug**
Running on current `trunk` (which is v3.2.1 + updated gold histograms) with high verbosity, we see in the basic simulation that there is no line for `Attaching trigscint_sp` to a…
-
**Is your feature request related to a problem? Please describe.**
Connected to https://github.com/LDMX-Software/ldmx-sw/pull/1191, the validation config shows a lot of warnings, which triggered th…
-
**Describe the bug**
I was looking a bit at the output of the PR jobs and half of the output is just
```sh
[ ElectronCounter ] 4 : Attemping to use non-existing input collection TriggerPadTracks_…
-
## Description
This was initially observed when studying the signal generation using this filter. What I observed through some extra debug printouts (and using the `StepPrinter` user action) was that…
-
We would like the option for the parameters used in a processing run to be automatically shared with RUCIO so that ldmx-sw is more easily integrated with LDCS. This feature would require a few things:…
-
Throwing exceptions from certain functions in a processor either are ignored (like in `onNewRun` or `beforeNewRun` becuase of the `try-catch` tree around them) or cause seg-faults (like in `configure`…
-
**Describe the bug**
I am trying to incorporate conditions for the input gain, pedestal and mip calibration parameters. In order to take into account interval of validity for the processing, I notice…