Skip to content
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

[ENH] Add FA images #1831

Closed
wants to merge 17 commits into from
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -667,7 +667,7 @@ The definitions of these fields can be found in
and a guide for using macros can be found at
https://github.com/bids-standard/bids-specification/blob/master/macros_doc.md
-->
{{ MACROS___make_suffix_table(["ADC", "TRACE"]) }}
{{ MACROS___make_suffix_table(["adc", "trace", "fa", "colfa"]) }}

<!--
This block generates a filename templates.
Expand Down Expand Up @@ -696,9 +696,9 @@ In such a case, two files could have the following names:
The user is free to choose any other label than `singleband` and
`multiband`, as long as they are consistent across subjects and sessions.

Scanner-generated TRACE and ADC volumes MAY be included using the
`TRACE` and `ADC` suffixes.
If TRACE or ADC volume filenames match a diffusion series with all applicable entities,
Scanner-generated trace, ADC and fractional anisotropy (fa and colfa) volumes MAY be included
using the `trace`, `adc`, `fa` and `colfa` suffixes, respectively.
If trace, adc, fa, or colfa volume filenames match a diffusion series with all applicable entities,
such volumes SHOULD be computed from that series.
Otherwise, some entity, such as [`acq-<label>`](../appendices/entities.md#acq),
SHOULD be used to indicate that the files are unrelated.
Expand Down
20 changes: 16 additions & 4 deletions src/schema/objects/suffixes.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -6,8 +6,8 @@ TwoPE:
display_name: 2-photon excitation microscopy
description: |
2-photon excitation microscopy imaging data
ADC:
value: ADC
adc:
value: adc
display_name: Apparent diffusion coefficient (ADC)
description:
Apparent diffusion coefficient (ADC) map
Expand Down Expand Up @@ -42,11 +42,23 @@ DIC:
display_name: Differential interference contrast microscopy
description: |
Differential interference contrast microscopy imaging data
colfa:
value: colfa
display_name: Colored Fractional Anisotropy image
description: |
Diffusion images reflecting the directionality of the diffusion tensor color-coded in red for
left-right oriented fibers, in blue for superior-inferior oriented fibers and green for
anterior-posterior oriented fibers.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry to chime in here. I may have missed other related discussions, but I'd dare to say that these are usually referred to as DEC (diffusion-encoded colormaps). Most commonly they contain FA information, but could be other information. They are referred to as DECFA in BEP016.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thx for the info! If DECFA is preferred we can just as easily use that, I have no preference but what expert people tell me we should do.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think BEP016 ever uses "DECFA" specifically. The fact that the nature of orientation encoding across volumes is directionally-encoded colour, and that the quantitative parameter encoded in the image is FA, are treated very deliberately as two separate dimensions. The distinction between scanner-generated derivatives and pipeline-generated BIDS Derivatives nevertheless means that there doesn't actually need to be correspondence between the two. Indeed a colour FA image generated by a pipeline will not use this suffix, even though the information encoded is identical.

I maybe have a slight preference for "colFA" just because it's consistent with data being emitted by many scanners that are intended to be encoded in this way.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the explanation.

The distinction between scanner-generated derivatives and pipeline-generated BIDS Derivatives nevertheless means that there doesn't actually need to be correspondence between the two.

Interesting. Did not know about the distinction.

Ad for the label itself, maybe I had a look at the wrong location then: the BEP016 gdocs does mention DECFA when talking about <map_label> fields on page 8: https://docs.google.com/document/d/1cQYBvToU7tUEtWMLMwXUCB_T8gebCotE1OczUpMYW60/edit#heading=h.mqkmyp254xh6
Linked from:
https://bids-specification.readthedocs.io/en/v1.2.1/06-extensions.html

Maybe the google doc should not be linked from the BIDS specification website to avoid confusion?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That BEP016 Google doc is highly outdated; development work on that project transitioned to GitHub some time ago. Maybe that should be flagged near the top of the document, and the website link should be changed. Here's the current status:
bids-standard/bids-bep016#24

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe that should be flagged near the top of the document, and the website link should be changed

Done!

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 thanks for doing this.

DF:
value: DF
display_name: Dark-field microscopy
description: |
Dark-field microscopy imaging data
fa:
value: fa
display_name: Fractional Anisotropy image
description: |
Diffusion images reflecting the directionality of the diffusion tensor
FLAIR:
value: FLAIR
display_name: Fluid attenuated inversion recovery image
Expand Down Expand Up @@ -465,8 +477,8 @@ TEM:
display_name: Transmission electron microscopy
description: |
Transmission electron microscopy imaging data
TRACE:
value: TRACE
trace:
value: trace
display_name: Trace diffusion weighted image
description: |
Diffusion images proportional to the trace of the diffusion tensor
Expand Down
6 changes: 3 additions & 3 deletions src/schema/rules/files/deriv/imaging.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -26,10 +26,10 @@ dwi_volumetric:
density: optional
description: optional

dwi_isotropic:
$ref: rules.files.raw.dwi.isotropic
dwi_scannerderivatives:
$ref: rules.files.raw.dwi.ScannerDerivatives
entities:
$ref: rules.files.raw.dwi.isotropic.entities
$ref: rules.files.raw.dwi.ScannerDerivatives.entities
space: optional
resolution: optional
density: optional
Expand Down
8 changes: 5 additions & 3 deletions src/schema/rules/files/raw/dwi.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -40,10 +40,12 @@ sbref:
chunk: optional

# Common scanner-generated derivatives need raw names
isotropic:
ScannerDerivatives:
suffixes:
- ADC
- TRACE
- adc
- colfa
- fa
- trace
extensions:
- .nii.gz
- .nii
Expand Down