Preprocessing specifically refers to anything that is done to the data prior to computing a standard deviation, but can also include various other things (eg, computing masks). In FS-FAST, these are the preprocessing steps:

* 1. Brain Mask BR * 2. Motion CorrectionBR * 3. Spatial SmoothingBR * 4. Intensity Normalization (inorm)BR

It is not necessary to perform all these stages. Slice timing correction is possible in FS-FAST but is currently experimental (see stc-sess). Note that B0 correction is not yet avaialble in FS-FAST. Most of these stages are self-explanatory. Brain Mask does a quick segmentation of the brain from the rest of the volume. Intensity normalization is the processes of rescaling all intensity values within a 4D data set so that the in-brain mean is 1000. Intensity normalization is actually done in two stages. The first stage (above) just computes the in-brain mean; the second stage is actually perfromed during the analysis.

The FS-FAST program "preproc-sess" will perform all of these stages. You can run it something like:

["preproc-sess"] -smout fmcsm5 -fwhm 5 -s sessidBR

There are a lot of things going on "under the hood", so I'll explain each one.By default, preproc-sess will perform brain masking, motion correction, and inorm. The other stages have to be specified explicitly. -s sessid tells preproc-sess the name of the session as created with unpacksdcmdir. Once it has the session, it can find the raw data in sessid/bold/RRR as f.bhdr (RRR is a run number). It will use the first time point of the first run as a template for both motion correction and brain masking. The brain mask is created using FSL's bet program. The result is stored in bold/masks/brain.bhdr. This is a "binary" mask, ie, each voxel is either 0 (not in the brain) or 1 (in the brain). preproc-sess will then perform motion correction (using AFNI) on each run that it finds in the bold directory using the first time point of the first run as the template. In each run, it will create a volume called fmc.bhdr. In addition, there will be fmc.mcdat with the motion correction parameters. It will also create mcextreg_000.bfloat, which can be used as a motion-related nuisance regressors at the time of analysis (discussed later). There is no answer to the question of "how much motion is too much?". Basically, you would like to avoid motion that is stimulus correlated as well as any sharp head jerks. The invocation to preproc-sess above instructs the program to perform volumetric (ie, 3d cartesian) smoothing with a full-width-half-max (fwhm) of 5mm. It will automatically use the motion corrected volume (fmc.bhdr) as the input. The output will be saved in fmcsm5.bhdr. This will be peformed for each run. There are several philosophies about how much to smooth, but usually 1.5-2 voxels is acceptible.