Hello,
This number is used purely for estimating the run-time when submitting to a cluster - you can safely set it to an arbitrary default value in your template.
Hope this helps,
Kind Regards
Matthew
> On 25 Sep 2016, at 22:41, SUBSCRIBE FSL Anonymous <[log in to unmask]> wrote:
>
> Hi,
>
> I would like to create a script for performing MELODIC analysis in a batch; i.e. on multiple subjects datasets, each with different-sized 4D files (e.g. some files have 300 volumes, others 1500 volumes, with everything in between)
>
> To do so I will be working with a template MELODIC design.fsf file. So far as I can tell, the only variables I need to create in the design.fsf are for; the "total volumes"; the path to the input folder; the path to the skull-stripped structural scan; and the "total voxels", as everything else will be the same.
>
> My questions are:
>
> (1) with respect to the "total volumes", is this something I need to create a variable for? When I use the MELODIC GUI, once FSL reads the input file, it checks the .hdr file and knows the number of volumes; when using a design.fsf file, will MELODIC not be able to identify the # of volumes once it reads the input file? Otherwise I will have to create a list specifying the # of volumes for each input dataset (100 or so separate datasets with different #s of volumes for each)
>
> (2) What is the design.fsf file referring to by "total voxels"? I can only assume it is referring to the total # of voxels contained in the input files. If so, must I then create another list which specifies the total # of voxels for each separate input file? This seems unnecessary, again given that FSL can identify this information once it has read the inputs files.
>
> Thanks very much!
|