I agree that looks like a bug.  The reason this is here is incase one has an 
${fMRIName} that can be analyzed two different ways using different designs 



 on behalf of Andrew Poppe <poppe...@gmail.com<mailto:poppe...@gmail.com>>
Date: Tuesday, September 20, 2016 at 11:06 AM
To: "hcp-users@humanconnectome.org<mailto:hcp-users@humanconnectome.org>" 
Subject: [HCP-Users] Possible Typo in task fmri script


I was recently adapting some of your great tfMRI analysis pipeline scripts for 
use with newly collected HCP-compliant data, and I noticed a line that I can't 
understand. In TaskfMRIAnalysis.v2.0.sh<http://TaskfMRIAnalysis.v2.0.sh> 
(called by TaskfMRIAnalysis.sh when "new" FSL versions are detected) on line 
126 it says:

LevelOnefsfNames=`echo $LevelOnefMRINames | sed 's/ /@/g'`

I may be misunderstanding something, so I thought I'd ask, but it seems to me 
that second variable should be $LevelOnefsfNames. Most likely, it won't cause a 
problem because by default the two variables are set to be identical in the 
TaskfMRIAnalysisBatch.sh script.

Thanks for any input about this line.


Andrew Poppe, Ph.D.
Postdoctoral Researcher
Olin Neuropsychiatry Research Center
Institute of Living
Hartford Hospital

HCP-Users mailing list

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.

HCP-Users mailing list

Reply via email to