You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
... e.g. after separation and energy estimation are done.
Use case: Offer the possibility to cut a data set (meaning both, events and runs group) at any given point of the analysis chain.
For example, if you want to run a part of your analysis only on events of a certain zenith range, It makes sense to apply cuts to the data set in use accordingly, rather the providing each plotting or analysis function with the option to use a certain zd-range.
I guess this can either be a new script or a modification of apply cuts.
However, I think it is important that all data groups (events, runs) in the HDF files are cut.
Curious to hear your oppinon.
The text was updated successfully, but these errors were encountered:
This sound much like the thing already proposed here #49 .
The distinction between selecting events based on analysis results from data selection based on run info is very important has the latter influences the ontime, the former not. So it should be two different scripts.
apply_cuts does eventwise cuts which do not effect the runs group
select_runs does runwise selection of runs, which effects also the runs group
... e.g. after separation and energy estimation are done.
Use case: Offer the possibility to cut a data set (meaning both, events and runs group) at any given point of the analysis chain.
For example, if you want to run a part of your analysis only on events of a certain zenith range, It makes sense to apply cuts to the data set in use accordingly, rather the providing each plotting or analysis function with the option to use a certain zd-range.
I guess this can either be a new script or a modification of apply cuts.
However, I think it is important that all data groups (events, runs) in the HDF files are cut.
Curious to hear your oppinon.
The text was updated successfully, but these errors were encountered: