bids-specification
bids-specification copied to clipboard
Allow for .nwb standard/file format to be used for "micr"
See https://pynwb.readthedocs.io/en/stable/tutorials/domain/ophys.html for support of various microscopy modalities within NWB. As NWB is already supported for other modalities, there is some support for microscopy in NWB in various tools, and as there are datasets with .nwb -- it makes sense to allow for .nwb to be used for microscopy data as well where appropriate.
this may be more of a question of physiology versus microscopy. in bids micr is focused on anatomy-based info not physiology. and i don't think nwb quite fits into that space. ophys doesn't fit into micr as far as i can tell. in bids ophys would go into func.
or phys if that was to become a new modality.
re "functional vs anatomical"
related discussions to tease apart those two notions of modality (MRI, micr, ...) and data type (anat vs func):
- https://github.com/INCF/neuroscience-data-structure/issues/18
- https://github.com/bids-standard/bids-2-devel/issues/55
Note that nothing in https://bids-specificabtrcitetcjtion.readthedocs.io/en/stable/04-modality-specific-files/10-microscopy.html explicitly restricts to anatomy (in effect - allows for extra), although indeed lacks any annotation for temporal component and events (requires "extending").
Overall the fact that we have anat/ and func/ ATM is an artifact of early days orientation toward MRI, and peculiarity that some modalities are purely functional (e.g. EEG, MEG) thus not even raising the question. But then if we look at PET -- we can have a single volume PET, or "functional PET" for which _events.tsv is then required.
So I could argue about similarity to this case here
re phys vs micr
ATM microscopy is for the modality, and it already supports 2PE which I guess also falls into "phys" domain. As all other "modality/" folders are really instrumentation modality, I would argue that we better not place microscopy data under electrophysiology folder.
has there been a request by a user / a particular group of users to make this happen?
If not, I would wait with introducing such a change, and remain "use case driven".
Especially when an argument of being "consistent" isn't entirely clear (as I get the impression, reading the discussion above)
has there been a request by a user / a particular group of users to make this happen?
it was brought up as a side-topic in discussion of BEP032 (@bep032) .
remain "use case driven".
LGTM. @bendichter, are you aware of any DANDI set with nwb microscopy data which we would run to while approaching conversion of DANDI dandisets to BIDS?
Yes, there are lots of ophys dandisets, including 1p, 2p, and more. Here are some good examples:
- 000037 - Allen Institute Openscope - Responses to inconsistent stimuli in somata and distal apical dendrites in primary visual cortex
- 000054 - Plitt & Giocomo (2021) Experience Dependent Contextual Codes in the Hippocampus. Nat Neuro
- 000711 - Allen Institute - Visual Behavior - Optical Physiology
Among others...
There is an ongoing effort of https://github.com/con/nwb2bids . Not yet sure how we would deal with multimodal nwb files like in https://dandiarchive.org/dandiset/000037/0.240209.1623/files?location=sub-408021&page=1 but I remain of opinion that NWB is a viable and used format for micr... I will rebase and take it out of the draft.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 87.93%. Comparing base (
943c20e) to head (97bd21c).
Additional details and impacted files
@@ Coverage Diff @@
## master #1632 +/- ##
=======================================
Coverage 87.93% 87.93%
=======================================
Files 16 16
Lines 1351 1351
=======================================
Hits 1188 1188
Misses 163 163
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
What benefits does micr/*.nwb have over micr/*.ome.zarr? There is a cost to tool writers to proliferating formats within a modality, hence why we do not support MINC.
That said, I know nothing of this space, and IMO this needs input from microscopy contributors. @jcohenadad do you have thoughts here?