-
Notifications
You must be signed in to change notification settings - Fork 188
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
Force original_end_frame >= original_start_frame in tracepad #1886
Conversation
@TomBugnon this error also appears for concatenated recordings, right? |
@alejoe91 I got this on a concatenated neuropixel recording (with full preprocessing) |
No no, I think it should work with simple data! |
original_end_frame = max( | ||
original_end_frame, original_start_frame | ||
) # Avoid negative dimensions errors downstream |
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.
I have the feelign that this is hidding a deeper bug.
How we could have this.
Would it be better to raise an error instead no ?
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.
Here's a real life scenario where original_end_frame < original_start_frame in TracePad
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.
(I do think there is an unrelated bug in get_chunk_with_margins , tho): #1885 (comment)
Sam wanted to look at this so I am just writing this for us as a reminder. Also, we are discussing this issue in more generality here: |
@TomBugnon sorry for getting back so late on this. This issue is gone with #1883 right? In that case I'll close this. Feel free to reopen if that's not the case! |
Avoids this error in phase_shift (and possibly other places)