-
Notifications
You must be signed in to change notification settings - Fork 25
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
Automatic File Naming Misses Some Sessions in 000971 #1492
Comments
We would need more information on how you got those file names -- using |
Yes, I believe this came about using DANDI CLI determines these names based on the presence of neurodata types, however this misses some cases where it is possible to determine the data types of the file contents in other ways. Here, there is a processing module named "behavior" that only contains an The solution I think Paul is suggesting here is to have the DANDI CLI parse that the file contains behavioral data if it contains a processing module named "behavior." This type of processing module comes up a lot because it is one of our recommended names for processing modules: "behavior", "ecephys", "ophys", etc. This is indicated in our best practices document here: https://nwbinspector.readthedocs.io/en/dev/best_practices/nwbfile_metadata.html?highlight=processing#processing-module-names The question is, do we want to use these types of heuristics to determine the file contents, or do we want to stick to neurodata types? |
Some of the file names in Dandiset 000971 do not contain the post-fix "behavior" despite containing a processing module named behavior just like all the other sessions.
For example, see sub-89-247_ses-FP-PR-2019-03-08T10-59-10.nwb
The text was updated successfully, but these errors were encountered: