
See the --procstring argument in the TaskAnalysis.sh script currently in the master branch. This functionality isn’t part of the last release (v.4.3.0).
FYI: The changes to TaskAnalysis in the master branch have not been extensively tested.
Cheers,
-MH
--
Michael Harms, Ph.D.
-----------------------------------------------------------
Associate Professor of Psychiatry
Washington University School of Medicine
Department of Psychiatry, Box 8134
660 South Euclid Ave. Tel: 314-747-6173
St. Louis, MO 63110 Email: mha...@wustl.edu
From: Asa Borzabadi <asa.bo...@gmail.com>
Reply-To: "hcp-...@humanconnectome.org" <hcp-...@humanconnectome.org>
Date: Saturday, June 4, 2022 at 8:21 AM
To: "hcp-...@humanconnectome.org" <hcp-...@humanconnectome.org>
Subject: [hcp-users] Re: Input to FSL
|
* External Email - Caution * |
In general, what should be the input file to the FSL?
On Sat, Jun 4, 2022 at 9:20 AM Asa Borzabadi <asa.bo...@gmail.com> wrote:
Dear experts,
I have a question about the input to the FSL step.
I have done the GenericVolume, GenericSurface, IcaFIx, PostFIx, MAMAll, and DeDrift scripts. which culminated in the creation of these files:
(outputs of DeDrifft)
Then I started looking into the generate_level1_fsf files and I found the following explanation:
Image file for which to produce an FSF file will be expected to be found at:
<study-folder>/<subject-id>/MNINonLinear/Results/<task-name>/<task-name>.nii.gz"
My question is if the input for FSL should be <task-name>_hp0_clean.nii.gz
instead of <task-name>.nii.gz. I suppose that this file: <task-name>_hp0_clean.nii.gz, which is the output of DeDrift could be a better option.
Could you please help me with this?
Regards,
Asa Farahani
--
You received this message because you are subscribed to the Google Groups "HCP-Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
hcp-users+...@humanconnectome.org.
To view this discussion on the web visit
https://groups.google.com/a/humanconnectome.org/d/msgid/hcp-users/CA%2Bs6gvmnDC%2BeiyRkETzgB7tOGpydz5bJ0q12jAWwUwme%3DxLwyA%40mail.gmail.com.
The materials in this message are private and may contain Protected Healthcare Information or other information of a sensitive nature. If you are not the intended recipient, be advised that any unauthorized use, disclosure, copying or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this email in error, please immediately notify the sender via telephone or return mail.
To view this discussion on the web visit https://groups.google.com/a/humanconnectome.org/d/msgid/hcp-users/F3CC8815-EAA4-437C-B9F2-D3ECA17463E6%40wustl.edu.
Yes, MSMAll_hp0_clean.dtseries.nii would be good to use.
To view this discussion on the web visit https://groups.google.com/a/humanconnectome.org/d/msgid/hcp-users/CA%2Bs6gvm31w6WZ%2BEBi0MD19%2BBAkpUzmiKxMnnBtJ8Z5SpU%3DomVg%40mail.gmail.com.
You probably would want to use the HCP’s TaskAnalysis pipeline rather than using FEAT directly to do the analysis, but you would still use FEAT to create the appropriate .fsf.
Matt.
To view this discussion on the web visit https://groups.google.com/a/humanconnectome.org/d/msgid/hcp-users/BB70F9F2-9D0B-41DA-99A3-DA3BD38A5662%40wustl.edu.
To view this discussion on the web visit https://groups.google.com/a/humanconnectome.org/d/msgid/hcp-users/40E620BD-7C49-4AA4-BBD3-51A1E6538844%40wustl.edu.
Please let us know how it goes using the version in the master branch. As I said, the current version in the master is relatively new, and hasn’t been extensively tested.
thx
To view this discussion on the web visit https://groups.google.com/a/humanconnectome.org/d/msgid/hcp-users/CA%2Bs6gvm_3y6WgXv5gheBUf2Z2J-5GwV6i%2BCqVakRxDkyFAviwQ%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/a/humanconnectome.org/d/msgid/hcp-users/609ADDA7-3D44-4F32-8813-A42BDD2B1FE4%40wustl.edu.
No need to apologize for asking questions.
Matt.
From: Asa Borzabadi <asa.bo...@gmail.com>
Reply-To: "hcp-...@humanconnectome.org" <hcp-...@humanconnectome.org>
Date: Wednesday, June 8, 2022 at 8:47 AM
To: "hcp-...@humanconnectome.org" <hcp-...@humanconnectome.org>
Subject: Re: [hcp-users] Re: Input to FSL
I really am grateful for your help.
I tried the first level analysis, it worked. I got some activation on the cortex, but when it comes to the subcortical regions it seems too noisy.
However, I still am not sure if the variables that I am setting are optimal, and even in some cases I am not sure what they should refer to.
I have included some questions here for clarification and I would really be grateful if you could help me.
for TaskName in ${TaskNameList}
do
LevelOneTasksList="tfMRI_${TaskName}_AP" #Delimit runs with @ and tasks with space
LevelOneFSFsList="tfMRI_${TaskName}_AP" #Delimit runs with @ and tasks with space
LevelTwoTaskList="NONE" #Space delimited list
LevelTwoFSFList="NONE" #Space delimited list
SmoothingList="2" #Space delimited list for setting different final smoothings. 2mm is no more smoothing (above minimal preprocessing pipelines grayordinates smoothing). Smoothing is added onto minimal preprocessing smoothing to reach desired amount
%%%%% (1) Do you think increasing the SmoothingList can be of any help? in terms of finding something meaningful in subcortical regions?
LowResMesh="32" #32 if using HCP minimal preprocessing pipeline outputs
GrayOrdinatesResolution="2" #2mm if using HCP minimal preprocessing pipeline outputs
OriginalSmoothingFWHM="2" #2mm if using HCP minimal preprocessing pipeline outputes
Confound="NONE" #File located in ${SubjectID}/MNINonLinear/Results/${fMRIName} or NONE
%%%%% (2) What should Confound variable point to? I tried "/100102/MNINonLinear/Results/tfMRI_VISION1" but it gave me errors, I think it should point to a specific file or folder but
what is the name of that file?
HighpassFilter="200" #Use 2000 for linear detrend, 200 is default for HCP task fMRI, NONE to turn off
%%%%% (3) This is the high pass filtering used by fsl right? Should we modify it according to the task paradigm that we have?
VolumeBasedProcessing="NO" #YES or NO. CAUTION: Only use YES if you want unconstrained volumetric blurring of your data, otherwise set to NO for faster, less biased, and more senstive processing (grayordinates results do not use unconstrained volumetric
blurring and are always produced).
%%%%% (4) Is my understanding about this variable correct? if it is set to be "Yes" we will have a volume based processing in the NIFTI space, if set to "NO", we have two streams
of processing one for surface preprocessing and one for subcortical processing. If I am wrong, can you correct me?
RegNames="MSMAll_Test" # Use NONE to use the default surface registration
ProcSTRING="hp0_clean" #Any preprocessing beyond CIFTI mapping and surface registration, e.g. spatial and temporal ICA cleanup or NONE
%%%%% (5) According to the output of DeDrift part, which is as in the figure below, the naming of variables called "RegNames" and "ProcSTRING" should change as above, correct?
To view this discussion on the web visit https://groups.google.com/a/humanconnectome.org/d/msgid/hcp-users/CA%2Bs6gvny5jTiXiEnO5CNi6tdofVGDReM-QGHrgy5a-AN%3Df6Byg%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/a/humanconnectome.org/d/msgid/hcp-users/329C7AEF-25E0-46AE-BD91-25FA15D2C675%40wustl.edu.
To view this discussion on the web visit https://groups.google.com/a/humanconnectome.org/d/msgid/hcp-users/CA%2Bs6gv%3DJwkkXufgWORXoVwb1tP%2BrDjieMB8gxag_rnhc-B2s0Q%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/a/humanconnectome.org/d/msgid/hcp-users/D430CAD9-47E5-4CB5-9928-4499A7B0CBCD%40wustl.edu.