help
help > RE: Question about the necessity of using field map to do susceptiblity distortion correction
Apr 5, 2023 07:04 PM | Alfonso Nieto-Castanon - Boston University
RE: Question about the necessity of using field map to do susceptiblity distortion correction
Hi Shuai Huang,
That's a good point, thanks, and you are totally right, by default when creating a new secondary dataset it will be typically set with the option 'dataset is implicitly related to functional data', so you would need to change that to 'dataset is explicitly defined' to then be able to specify/enter the associated files explicitly (or, as you did, use the 'copy dataset' option to force that new dataset to be explicitly defined). That is in all likelihood pretty confusing, as implicitly defining secondary datasets is probably not the most common scenario, so I will change this default behavior in the next release so that CONN always starts new dataset with the 'dataset is explicitly defined' option instead, in order to avoid these issues.
Thanks again!
Alfonso
Originally posted by Shuai Huang:
That's a good point, thanks, and you are totally right, by default when creating a new secondary dataset it will be typically set with the option 'dataset is implicitly related to functional data', so you would need to change that to 'dataset is explicitly defined' to then be able to specify/enter the associated files explicitly (or, as you did, use the 'copy dataset' option to force that new dataset to be explicitly defined). That is in all likelihood pretty confusing, as implicitly defining secondary datasets is probably not the most common scenario, so I will change this default behavior in the next release so that CONN always starts new dataset with the 'dataset is explicitly defined' option instead, in order to avoid these issues.
Thanks again!
Alfonso
Originally posted by Shuai Huang:
Hi Alfonso,
Thanks so much, ! This is very helpful.
Just a quick note on creating the new "secondary dataset #2 (fmap)":
1. After I created and labelled it to "fmap", the window that allowed me to import the fieldmap (in Hz) did not show up. Please see the top figure of the attached steps.png
2. I needed to click "copy/exchange dataset" to copy "secondary dataset #1" to "secondary dataset #2" in order to bring up the window "Import other imaging data files". Please see the middle and bottom figures of the attached steps.png
3. I can then import the fieldmap (in Hz) from the window "Import other imaging data files".
I don't know whether it is a bug that the window "Import other imaging data files" did not show up immediately after I created "secondary dataset #2 (fmap)". But here is a workaround in case anyone is also trying to import the fieldmap.
Thanks so much, ! This is very helpful.
Just a quick note on creating the new "secondary dataset #2 (fmap)":
1. After I created and labelled it to "fmap", the window that allowed me to import the fieldmap (in Hz) did not show up. Please see the top figure of the attached steps.png
2. I needed to click "copy/exchange dataset" to copy "secondary dataset #1" to "secondary dataset #2" in order to bring up the window "Import other imaging data files". Please see the middle and bottom figures of the attached steps.png
3. I can then import the fieldmap (in Hz) from the window "Import other imaging data files".
I don't know whether it is a bug that the window "Import other imaging data files" did not show up immediately after I created "secondary dataset #2 (fmap)". But here is a workaround in case anyone is also trying to import the fieldmap.
Threaded View
| Title | Author | Date |
|---|---|---|
| Shuai Huang | Mar 24, 2023 | |
| Alfonso Nieto-Castanon | Mar 29, 2023 | |
| Shuai Huang | Apr 4, 2023 | |
| Alfonso Nieto-Castanon | Apr 5, 2023 | |