Hi Reza,
This case seems similar to the scanner-generated DWI estimates (ADC, FA, trace, etc.). Since the CBF map is derived from the raw data, similar to how the DWI estimates are derived from the raw DWI data, I suggest including and reporting it as ASL-derivative, including the vendor, model, and software version of your scanner.
Please, see the BIDS specification for further guidance on how to store a derived dataset (Common principles) and report a pipeline (Modality agnostic files).
Kind regards,
Tibor
Tibor Auer, MD, PhD, FHEA
Lecturer in Biological Psychology
School of Psychology, Faculty of Health and Medical Sciences
University of Surrey, Guildford GU2 7XH
--
We are all colleagues working together to shape brain imaging for tomorrow, please be respectful, gracious, and patient with your fellow group members.
---
You received this message because you are subscribed to the Google Groups "bids-discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bids-discussi...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bids-discussion/24fcac99-bf9b-4447-869f-cca85c250ecfn%40googlegroups.com.
Hi all,
this is not gonna help Reza, sorry ... but
- for single volume images, the common view is whatever comes out of the scanner is raw, for instance T1w with gradient non linearity correction is raw, yet this is a post-hoc correction, same thing with the UNIT image from MP2RAGE, even the phasediff image in fieldmap is computed post-hoc and it is stored as raw.
- anything that comes from time series tend to be seen as derivative, as Tibor pointed out, FA, ADC, MD for DWI and CBF for ASF
We could keep that distinction single volume vs time series, but
it doesn't seem based on any computational principle -- or we need
to decide as a community and resolve this either all derivatives
(but it would break lots of backward stuff) or we accept 'anything
out of the scanner' as raw, implying you could have FA,ADC,MD,CBF
in raw (out of the scanner) and FA,ADC,MD,CBF in derivatives (out
of a given analysis pipeline) that would be distinguishable only
from the position in the tree and json files (or impose an extra
key-value in the name in the later case).
Cyril
To view this discussion on the web visit https://groups.google.com/d/msgid/bids-discussion/00fb01d99b6d%2424f77d00%246ee67700%24%40gmail.com.
-- Dr Cyril Pernet, PhD, OHBM fellow, SSI fellow Neurobiology Research Unit, Building 8057, Blegdamsvej 9 Copenhagen University Hospital, Rigshospitalet DK-2100 Copenhagen, Denmark wamc...@gmail.com https://cpernet.github.io/ https://orcid.org/0000-0003-4010-4632
Reza,
I re-read the section on ASL in the specification:
As I understand it on my read, ASL is one 4D NIfTI, but it’s just 4D because it’s a result of concatenating the 3D images yourself and providing and “aslcontext.tsv” that says what volume is what in the 4D NIfTI. I hope that helps.
Warm regards,
Eric Earl [C]
Scientist
NIMH IRP Data Science & Sharing Team
Google Scholar Profile
https://scholar.google.com/citations?user=8IwbaOcAAAAJ
Book a meeting
To view this discussion on the web visit https://groups.google.com/d/msgid/bids-discussion/b63210c8-b000-2787-2ad9-595bb221e09d%40gmail.com.
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and are confident the content is safe.
On 12 Jun 2023, at 17:52, 'Earl, Eric (NIH/NIMH) [C]' via bids-discussion <bids-di...@googlegroups.com> wrote:
Reza,
I re-read the section on ASL in the specification:
As I understand it on my read, ASL is one 4D NIfTI, but it’s just 4D because it’s a result of concatenating the 3D images yourself and providing and “aslcontext.tsv” that says what volume is what in the 4D NIfTI. I hope that helps.
To view this discussion on the web visit https://groups.google.com/d/msgid/bids-discussion/BY3PR09MB7284D39ED37635647EEA1138EC54A%40BY3PR09MB7284.namprd09.prod.outlook.com.