-
Notifications
You must be signed in to change notification settings - Fork 32
Plugging in Pulsecombiner and Pulsenoise for BIC #2076
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Plugging in Pulsecombiner and Pulsenoise for BIC #2076
Conversation
for more information, see https://pre-commit.ci
This PR applies the include-what-you-use fixes as suggested by https://github.com/eic/EICrecon/actions/runs/17684050541. Please merge this PR into the branch `2075-plugging-in-pulsecombiner-and-pulsenoise-for-bic` to resolve failures in PR #2076. Auto-generated by [create-pull-request][1] [1]: https://github.com/peter-evans/create-pull-request Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Based on the Slides presented at the simulation meeting, the followings were updated.
In the slides, it is expected that this PR reduces the data size even though the BIC pulse data types are added, but I added one more pulse data, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Briefly, what does this PR introduce?
This PR is to plug in PulseCombiner and PulseNoise for BIC. For the PulseCombiner, pulses from different particles were combined for each SiPM channel. For the PulseNoise, a specific pedestal distribution was reproduced so that it gives the same pedestal mean and sigma when the amplitudes are measured every 25 ns. To reproduce the specific pedestal model, an offset was added to the
PulseNoiseConfig.h
. Since the order of the arguments in theFalphaNoise
was swapped, it was modified.What kind of change does this PR introduce?
Please check if this PR fulfills the following:
Does this PR introduce breaking changes? What changes might users need to make to their code?
Does this PR change default behavior?