Closed FaroutYLq closed 1 year ago
Trying to solve this issue
Maybe we should do this in Events
https://github.com/XENONnT/straxen/blob/master/straxen/plugins/events/events.py?
We currently allow peaks to be overlapping but not events.
We currently allow peaks to be overlapping but not events.
@dachengx sorry I am confused. In the linked Events
script there is no abs_time_to_prev_next_interval
?
@dachengx sorry I am confused. In the linked
Events
script there is noabs_time_to_prev_next_interval
?
Yes, you are correct. I was wondering whether we should completely prohibit overlapping events in straxen. Then the warning related to this will not appear. abs_time_to_prev_next_interval
in VetoProximity
also just test whether events
are overlapping.
Oh I see the argument. I think what you said is fully sensible. So a better place to do this is in events
.
But I would suggest we keep doing what this PR did for now, since right now I just want to make sure we are not missing any functionality from the straxPR. Let's do one thing each time
But I would suggest we keep doing what this PR did for now, since right now I just want to make sure we are not missing any functionality from the straxPR. Let's do one thing each time
No objection, my friend.
How's this now @FaroutYLq
Sorry is there something you want me to update here?
Sorry is there something you want me to update here?
I moved the dingoes directly to Event
plugin. Do you think it is OK?
No objection from me
What does the code in this PR do / what does it improve?
Manually check event overlapping, since we are skipping such assertion in the updated
strax.abs_time_to_prev_next_interval
.Can you briefly describe how it works?
Did what
strax.abs_time_to_prev_next_interval
did before modification:Can you give a minimal working example (or illustrate with a figure)?