There are two ways to get fMRIPrep installed:
- within a Manually Prepared Environment (Python 3.7+), also known as bare-metal installation; or
- using container technologies (RECOMMENDED).
Once you have your bare-metal environment set-up (first option above),
the next step is executing the fmriprep
command-line.
The fmriprep
command-line options are documented in the :ref:`usage`
section.
The fmriprep
command-line adheres to the BIDS-Apps recommendations
for the user interface.
Therefore, the command-line has the following structure:
$ fmriprep <input_bids_path> <derivatives_path> <analysis_level> <named_options>
On the other hand, if you chose a container infrastructure, then
the command-line will be composed of a preamble to configure the
container execution followed by the fmriprep
command-line options
as if you were running it on a bare-metal installation.
The command-line structure above is then modified as follows:
$ <container_command_and_options> <container_image> \ <input_bids_path> <derivatives_path> <analysis_level> <fmriprep_named_options>
Therefore, once specified the container options and the image to be run
the command line is the same as for the bare-metal installation but dropping
the fmriprep
executable name.
fMRIPrep is a NiPreps application, and therefore follows some overarching principles of containerized execution drawn from the BIDS-Apps protocols. For detailed information of containerized execution of NiPreps, please visit the corresponding Docker or Singularity subsections. The NiPreps portal also containes extended details of execution with the Docker wrapper.
Warning
This method is not recommended! Please checkout container alternatives.
Make sure all of fMRIPrep's External Dependencies are installed.
These tools must be installed and their binaries available in the
system's $PATH
.
A relatively interpretable description of how your environment can be set-up
is found in the Dockerfile.
As an additional installation setting, FreeSurfer requires a license file (see :ref:`fs_license`).
On a functional Python 3.7 (or above) environment with pip
installed,
fMRIPrep can be installed using the habitual command
$ python -m pip install fmriprep
Check your installation with the --version
argument
$ fmriprep --version
fMRIPrep is written using Python 3.7 (or above), and is based on nipype_.
fMRIPrep requires some other neuroimaging software tools that are
not handled by the Python's packaging system (Pypi) used to deploy
the fmriprep
package:
- FSL_ (version 5.0.9)
- ANTs_ (version 2.2.0 - NeuroDocker build)
- AFNI_ (version Debian-16.2.07)
- C3D (version 1.0.0)
- FreeSurfer_ (version 6.0.1)
- ICA-AROMA (commit e8d7a58, post v0.4.4-beta)
- bids-validator (version 1.4.0)
- connectome-workbench (version Debian-1.3.2)
If you intend to run fMRIPrep on a remote system, you will need to make your data available within that system first.
For instance, here at the Poldrack Lab we use Stanford's :abbr:`HPC (high-performance computing)` system, called Sherlock. Sherlock enables the following data transfer options.
Alternatively, more comprehensive solutions such as Datalad will handle data transfers with the appropriate settings and commands. Datalad also performs version control over your data.