-
Notifications
You must be signed in to change notification settings - Fork 3
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
Question about microscopy data types and modalities #18
Comments
Hi Joe, I think your question is really related to the BIDS specifications themselves, and therefore, I would re-post it there: https://github.com/bids-standard/bids-specification/issues (and I'll answer there with what I know ;) ) Cheers, Sylvain |
FWIW, an example of BIDS dataset with |
FWIK, there was no functional data around when the BEP microscopy was put together and when it was integrated officially in the BIDS specs... so it's lacking, and @JoeZiminski , your post reflects this... the official specs for microscopy are here now: https://bids-specification.readthedocs.io/en/stable/04-modality-specific-files/10-microscopy.html, and correspond to what @yarikoptic explains: different suffixes are used for func (e.g 2PE) and anat (e.g CONF) data types; but indeed, this seperation between func and anat (using suffixes) is not consistent with how it's done for MRI (with different "BIDS modalities" sitting in different directories)... |
@JoeZiminski this indeed an inconsistency between modalities my suggestion to help keep them separate would be to use different session folders
|
Hi Everyone,
We have a question about microscopy data, apologies if this is the wrong place for this discussion (if so it would be much appreciated if someone could point us to the correct place).
We are currently thinking about how to store microscopy data of histological type (i.e. post-mortem) and what we call 'functional' imaging, such as 2-photon with calcium indicators. Currently we have the data-type names
histology
andfuncimg
although we would like to movehistology
tomicr
to align with BEP031. However, in this case it is not entirely clear what data should go undermicr
, from reading the specification, any 2-photon data should be stored inmicr
. However, it seems unintuitive to mix both functional imaging and post-mortem histology within the same data-type. Similarly this would not reflect the distinction made in neuroimaging BIDS, that hasanat
andfunc
to distinguish between anatomical and functional imaging.Does anyone have any further insight as to this question? We are considering using
micr
for histology andfuncimg
for functional microscopy. However, this naming is somewhat confusing (asfuncimg
is a form of microscopy), and we do not want to break BIDS compatibility if indeedmicr
is intended to contain functional microscopy.Thanks!
Joe (from the SWC Neuroinformatics Unit working on NeuroBlueprint)
The text was updated successfully, but these errors were encountered: