Thanks very much Michael, Its probably not this straightforward, but is it acceptable to keep this value constant across participants? I've played around with extreme values and it doesn't appear to vary much. Best, Garret ________________________________________ From: FSL - FMRIB's Software Library <[log in to unmask]> on behalf of Harms, Michael <[log in to unmask]> Sent: 24 March 2014 13:42 To: [log in to unmask] Subject: Re: [FSL] total voxel number The fmri(totalVoxels) value is used in 'feat' itself as part of its estimation of the allowed upper time limit for how long to let various stages of feat run if the job is submitted to a cluster. I've had to tweak this value in the past to get high spatial resolution, many time point multi-band data to run on our cluster without the stages timing out on our cluster. If you simply want to set the value to what is calculated in 'featlib.tcl', here is the revelant line from 'featlib.tcl': set totalVoxels [ expr [ exec sh -c "$FSLDIR/bin/fslval $thefile dim1" ] * [ exec sh -c "$FSLDIR/bin/fslval $thefile dim2" ] * [ exec sh -c "$FSLDIR/bin/fslval $thefile dim3" ] * [ exec sh -c "$FSLDIR/bin/fslval $thefile dim4" ] ] cheers, -MH -- Michael Harms, Ph.D. ----------------------------------------------------------- Conte Center for the Neuroscience of Mental Disorders Washington University School of Medicine Department of Psychiatry, Box 8134 660 South Euclid Ave. Tel: 314-747-6173 St. Louis, MO 63110 Email: [log in to unmask] On 3/24/14 7:07 AM, "Garret O'Connell" <[log in to unmask]> wrote: >Hello FSLers, > >I am batch running FEAT preprocessing by replacing string values in a >template design.fsf. It occurred to me early on that the volume number >had to be calculated on the fly for every participant. Now I have spotted >the total voxel number entry in the design.fsf. Unlike volume number that >has to be accurate, FEAT will execute regardless of what value is entered >for the total voxel number. Can anyone tell me what this is, how it >affects processing, and how can i similarly estimated it on the fly. I >have compared it to the fslstats -v output, and they are close but >different. > >Best, > >Garret ________________________________ 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.