-
Notifications
You must be signed in to change notification settings - Fork 29
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
Validation errors out with pynwb 3.0.0 #1582
Comments
Hi @h-mayorquin, could you please look into this issue? Perhaps this might be an issue with cc @bendichter |
Hi, can you share the files that break validation? Are they stored somewhere where we can access them? This is to reproduce the error on my side. |
@h-mayorquin Please see above. |
My bad, thanks, I will take a look. |
Hi, @kabilar . I opened the file with the latest version pynwb and inspected it with the last version of the inspector and both of them worked fine. No error thrown. I can reproduce this locally: dandi validate --ignore "(NWBI|DANDI)" HardwareBasic-NI_11-V2.nwb
2025-02-28 15:39:31,579 [ INFO] NumExpr defaulting to 16 threads.
/home/heberto/miniconda3/envs/work/lib/python3.11/site-packages/pynwb/core.py:56: UserWarning: Use of icephys_filtering is deprecated and will be removed in PyNWB 4.0. Use the IntracellularElectrode.filtering field instead
warn(error_msg)
[pynwb.GENERIC] /home/heberto/Downloads/HardwareBasic-NI_11-V2.nwb — not enough values to unpack (expected 2, got 0)
2025-02-28 15:39:32,517 [ INFO] Logs saved in /home/heberto/.local/state/dandi-cli/log/2025.02.28-21.39.30Z-96539.log So I think th error is on dandi cli indeed but I can't track where that error is originated. |
Perhaps you could follow the advice on the warning if you have control over the nwbfile creation? Must be some hardcoded return expectation at the dandi cli python API. For the record this is the output of the inspector:
NWBInspector Report SummaryTimestamp: 2025-02-28 15:40:55.745717-06:00 Platform: Linux-6.8.0-54-generic-x86_64-with-glibc2.39 NWBInspector version: 0.6.3 Found 24 issues over 1 file: 4 - BEST_PRACTICE_VIOLATION 20 - BEST_PRACTICE_SUGGESTION BEST PRACTICE VIOLATIONS (4)0.0 HardwareBasic-NI_11-V2.nwb: check_intracellular_electrode_cell_id_exists - 'IntracellularElectrode' object with name 'electrode_1' Message: Please include a unique cell_id associated with this IntracellularElectrode. BEST PRACTICE SUGGESTIONS (20)1.4 HardwareBasic-NI_11-V2.nwb: check_description - 'Subject' object at location '/general/subject' Message: Description is missing. |
Thanks for investigating, @h-mayorquin. That was very helpful. Hi @jwodder, next week, could you please look into why the dandi client is throwing the error with |
Fix support for pynwb v3 which has changed API slightly
🚀 Issue was released in |
@kabilar Thanks for the quick fix. Works now like a charm! |
dandi version: 0.66.7
OS: Debian bookworm x64
I'm about to update pynwb and dandi for our MIES CI 1.
But I'm hitting an issue with the new pynwb 3.0.0 version:
breaks
but if I do
it works with
I'm attaching the example file in case it's relevant:
HardwareBasic-NI_11-V2.nwb.zip
This also reproduces in fresh environment in a docker image.
The text was updated successfully, but these errors were encountered: