Implementation of TRestEventTimeSelectionProcess to select events by their timeStamp #540
Conversation
This file contains 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
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
AlvaroEzq
force-pushed
the
alvaroezq_timeSelection
branch
from
239630c to
3d272b6
Compare
AlvaroEzq
changed the title
mariajmz
approved these changes
Jan 20, 2025
Anakintana
approved these changes
Jan 20, 2025
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.
Implementation of TRestEventTimeSelectionProcess, a new TRestEventProcess to select the events by their time given a set of active or dead datetime ranges. Although this could be achieved in analysis through cuts to the timeStamp or by using the already existing TRestEventSelectionProcess, this new process will be very useful in the case that the run contains a lot (order of tens or more) of different active/dead time periods, for example, in long background runs with poor detector stability.