[Add Check]: Check if spike times are increasing #394
Assignees
Labels
category: new check
a new best practices check to apply to all NWBFiles and their contents
Comments
CodyCBakerPhD
added
the
category: new check
|
Reproducible code from nwbinspector.tools import get_s3_urls_and_dandi_paths
from pynwb import NWBHDF5IO
import matplotlib.pyplot as plt
s3_urls = get_s3_urls_and_dandi_paths(dandiset_id="000003")
dandi_paths = {v: k for k, v in s3_urls.items()}
s3_url = dandi_paths["sub-YutaMouse41/sub-YutaMouse41_ses-YutaMouse41-150831_behavior+ecephys.nwb"]
io = NWBHDF5IO(path=s3_url, mode="r", driver="ros3")
nwbfile = io.read()
spike_times = nwbfile.units.get_unit_spike_times(index=1)
plt.plot(spike_times) |
|
@gviejo spotted another one in |
|
@alessandratrapani this would be another good issue to tackle. |
4 tasks
4 tasks
4 tasks
4 tasks
|
Also found by @gviejo in |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What would you like to see added to the NWBInspector?
@gviejo noticed in DANDI set
000003, filesub-YutaMouse41/sub-YutaMouse41_ses-YutaMouse41-150831_behavior+ecephys.nwb, unit ID1The spike times reset to zero about halfway through
Investigating if this is a problem with the conversion code or with the source data itself
But we should probably add a check for this in the Inspector to catch it going forward
Pseudocode or other logic of the check
No response
Do you have any interest in helping implement the check function?
Yes.
Code of Conduct
The text was updated successfully, but these errors were encountered: