Skip to content

Handle more complex metadata in NWB files #1502

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

apdavison
Copy link
Member

This PR attempts to address the problems in #1413.

It is a work in progress. The first commit lets the example script run through without errors on my machine, but I plan to take more time to check that the Neo data are an accurate representation of the NWB file contents.

@apdavison apdavison added the IO label Jul 2, 2024
@apdavison apdavison added this to the 0.14.0 milestone Jul 2, 2024
@apdavison apdavison marked this pull request as draft July 2, 2024 15:16
@Moritz-Alexander-Kern
Copy link
Member

Hey,
thanks for looking into this.

Indeed, now I can load the .nwb -files from the DANDI archives without errors.

I get some warnings and 542 neo.SpikeTrain and 4 neo.IrregularlySampledSignal objects.

Unfortunately I don't know what to expect, I was trying to inspect the .nwb file using the pynwb package.

See the following .ipynb notebook https://gist.github.com/Moritz-Alexander-Kern/93412334080a1ce021f2df9ec06244c5

@alejoe91 alejoe91 modified the milestones: 0.14.0, 0.15.0 Jan 17, 2025
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants