This repository has been archived by the owner on Jun 5, 2024. It is now read-only.
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.
The fix introduced in PR#75 created some issues for mc_chain because we pass the actual G4 eventid to wfsim in order to add some offset to event times according to the specified rate. However, in epix this cut refers to indices of G4 events, not to G4 eventids. Since
cut_by_eventid
was set to True in epix configuration, all simulations, except for the one where G4 eventid started at 0, had zero events in the epix output after PR#75 had been propagated tomontecarlo-development
.I did more thorough tests and updated
cut_by_eventid
treatment again, here's the test notebook:/project2/lgrandi/pkavrigin/2024-01-21_test_epix/2024-01-21_TestEPIX.ipynb
In the notebook "expected" means the number of events from G4 file which we expect to see in the epix output with the given parameters, and "result" is what we actually get.
Output with the current epix master branch:
Output with
fix_evtid_again
branch: