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
I am doing the Reimer Lab conversion and we have a timestamps array that contains NaNs. I just decided to leave them in. Then when running the inspector, this triggers the check_timestamps_ascending check, even though all the non-NaN values are ascending. I think the timestamps array should be flagged by the inspector, but this should be its own check, and if the defined values are ascending it should not trigger the check_timestamps_ascending check.
Have you ensured this bug was not already reported?
To the best of your ability, have you ensured this is a bug within the code that checks the NWBFile, rather than a bug in the NWBFile reader (e.g., PyNWB or MatNWB)?
The text was updated successfully, but these errors were encountered:
What happened?
I am doing the Reimer Lab conversion and we have a timestamps array that contains NaNs. I just decided to leave them in. Then when running the inspector, this triggers the check_timestamps_ascending check, even though all the non-NaN values are ascending. I think the timestamps array should be flagged by the inspector, but this should be its own check, and if the defined values are ascending it should not trigger the check_timestamps_ascending check.
Operating System
macOS
Python Version
3.9
Were you streaming with ROS3?
No
Package Versions
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: