Add algorithm to generate SiPM waveforms #1761
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Moving my (meager) WIP from my fork to a branch for easier tracking/collaborating. |
Capybara summary for PR 1761
|
for more information, see https://pre-commit.ci
wdconinc
force-pushed
the
add-sipm-waveform-generator
branch
from
eca036b to
d1d45e9
Compare
for more information, see https://pre-commit.ci
|
Rebased to pick up json.gz efficiencies for capybara. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Briefly, what does this PR introduce?
This PR introduces the
SiPMWaveformGeneratoralgorithm, which -- as the name suggests -- generates a waveform from inputedm4hep::SimCalorimeterHits using the SimSiPM package (TBD).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?
No.
Does this PR change default behavior?
No.