-
Notifications
You must be signed in to change notification settings - Fork 31
Pulse generation from time-clustered Simcalorimeterhits using a shared template #2004
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?
Pulse generation from time-clustered Simcalorimeterhits using a shared template #2004
Conversation
for more information, see https://pre-commit.ci
…mcalorimeterhits-using
Associations are 3rd party objects that relate to two other objects that they connect. Relations are just fields pointing to another objects. This method works with relations and not associations.
for more information, see https://pre-commit.ci
…d template (fix: iwyu) (#2025) This PR applies the include-what-you-use fixes as suggested by https://github.com/eic/EICrecon/actions/runs/17116586226. Please merge this PR into the branch `2001-pulse-generation-from-time-clustered-simcalorimeterhits-using` to resolve failures in PR #2004. 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>
4698884
to
05fafa1
Compare
…d template (fix: iwyu) (#2030) This PR applies the include-what-you-use fixes as suggested by https://github.com/eic/EICrecon/actions/runs/17146753827. Please merge this PR into the branch `2001-pulse-generation-from-time-clustered-simcalorimeterhits-using` to resolve failures in PR #2004. 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>
for more information, see https://pre-commit.ci
@veprbl I checked in more detail referring to your comments and commits. First, the increased number of hits and contributions are due to the It seems that setting the Could you check if the file size from this change is acceptable? For now, I added No BIC pulses: 27M |
In simulation production campaigns we cannot afford a factor 4 increase in data volume for a single detector (or even in general). I'd suggest removing this data collection from the default output, enable it in a CI test job to exercise the algorithm (ASAN, TSAN), and at some point we have a downstream algorithm that condenses the data volume again. |
Since we now running unit tests on PulseGenerator, we can just disable |
@wdconinc @veprbl Then, regarding the next step, I would like to discuss it including the downstream algorithm at the coming simulation meeting. I would appreciate it if you could join the meeting on Aug 26. By the way, could you let me know up to what factor of data size increase would be acceptable? I think there may still be a possible way to reduce the output size by optimizing both |
As a rule of thumb, we don't want a single detector subsystem to take more than 20% of resources (storage, computing). |
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.
This is in good shape now.
Briefly, what does this PR introduce?
This PR is for pulse generation from time-clustered
SimCalorimeterHit
s. To generate a pulse from the contributions that are close in time, atimeID
is assigned in theSimCalorimeterHitProcessor
. Since bothSimCalorimeterHit
andSimTrackerHit
share a common pulse generation mechanism, a shared template algorithm,PulseGeneration
, has been implemented.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?