Usage

Neuroscout-CLI executes models built using Neuroscout by acting as a lightway layer that fetches the data required for the model, and runs it using FitLins. After the model is run, the results are outputs as BIDS Derivatives, and uploaded to NeuroVault (by default).

Containerized execution

Note that depending on your Installation method, the exact command will differ.

For Docker, you must prepend the command with docker run -it and map relevant local directories from the host to the container using -v. Instead of `euroscout, the command will be neuroscout/neuroscout-cli to reference a specific image. For example:

docker run -it -v LOCAL_DIR:OUT_DIR neuroscout/neuroscout-cli run ANALYSIS_ID OUT_DIR

For Singularity, you must prepend the command with singularity run --cleanenv and refer to a specific pre-downloaded image:

singularity run --cleanenv neuroscout-cli-<version>.simg ANALYSIS_ID OUT_DIR

For a complete guide, see Portable Docker Execution and Singularity for HPCs in the offical Neuroscout Docs.

Command-Line Arguments

neuroscout

Runs analyses created on neuroscout.org.

Neuroscout-CLI downloads the required data, configures outputs, and uses FitLins to execute analyses. Results are automatically uploaded to NeuroVault, facilitating data sharing.

In most use cases, the “run” command will handle all of the above, although the “get” and “upload” command are available for piecemeal execution.

Note: If using Docker, remember to map local volumes to the container using “-v” (such as OUT_DIR).

neuroscout [OPTIONS] COMMAND [ARGS]...

get

Fetch analysis inputs.

Downloads the analysis bundle, preprocessed fMRI inputs, and configures output directory.

Inputs are downloaded to the output directory under sourcedata. If you run many analyses, you may wish to provide an –download-dir where datasets can be cached across analyses.

Note: run automatically calls get prior to execution, by default.

neuroscout get [OPTIONS] ANALYSIS_ID OUT_DIR

Options

--datalad-jobs <datalad_jobs>

Number of parallel jobs for DataLad when fetching files

--download-dir <download_dir>

Directory to cache input datasets, instead of OUT_DIR

--bundle-only

Only fetch analysis bundle, not imaging data

Arguments

ANALYSIS_ID

Required argument

OUT_DIR

Required argument

run

Run an analysis.

Automatically gets inputs and uploads results to NeuroVault by default.

This command uses FitLins for execution. Thus, any valid options can be passed through in [FITLINS_OPTIONS].

Note: –model, –derivatives and –ignore and positional arguments are automatically configured.

Example:

neuroscout run –force-upload –n-cpus=3 a54oo /out

If using Docker, remember to map local volumes to save outputs:

docker run –rm -it -v /local/dir:/out neuroscout/neuroscout-cli run a54oo /out

neuroscout run [OPTIONS] [FITLINS_OPTIONS]... ANALYSIS_ID OUT_DIR

Options

--download-dir <download_dir>

Directory to cache input datasets, instead of OUT_DIR

--datalad-jobs <datalad_jobs>

Number of parallel jobs for DataLad when fetching files

--no-get

Don’t automatically fetch bundle & dataset

--upload-first-level

Upload first-level results, in addition to group

--no-upload

Don’t upload results to NeuroVault

--fitlins-help

Display FitLins help and options

Arguments

FITLINS_OPTIONS

Optional argument(s)

ANALYSIS_ID

Required argument

OUT_DIR

Required argument

upload

Upload results.

This command can be used to upload existing results to NeuroVault.

Note: run automatically calls upload after execution, by default.

neuroscout upload [OPTIONS] ANALYSIS_ID OUT_DIR

Options

--force-upload

Force upload even if a NV collection already exists

--upload-first-level

Upload first-level results, in addition to group

Arguments

ANALYSIS_ID

Required argument

OUT_DIR

Required argument

Optional FitLins arguments

Under the hood Neuroscout-CLI uses FitLins to execute the model. As such, Neuroscout-CLI will forward any arguments passed as [FITLINS_OPTIONS] to __FitLins__.

For details on valid FitLins arguments, please see Usage.