sct_download_data

Download binaries from the web.

usage: sct_download_data -d <dataset> [-o <folder>] [-k] [-h] [-v <int>]
                         [-profile-time [<file>]] [-trace-memory [<folder>]]

MANDATORY ARGUMENTS

-d

Possible choices: default, binaries_linux, binaries_osx, binaries_win, deepreg_models, deepseg_gm_models, deepseg_lesion_models, deepseg_sc_models, exvivo_template, manual-correction, MNI-Poly-AMU, PAM50, PAM50_normalized_metrics, sct_course_data, sct_example_data, sct_testing_data, template-dog

Name of the dataset, as listed in the table below. If ‘default’ is specified, then all default datasets will be re-downloaded. (Default datasets are critical datasets downloaded during installation.)

OPTIONAL ARGUMENTS

-o

Path to a directory to save the downloaded data.

(If not provided, the dataset will be downloaded to the SCT installation directory by default. Directory will be created if it does not exist. Warning: existing data in the directory will be erased unless -k is provided.)

-k

Keep existing data in destination directory.

Default: False

MISC ARGUMENTS

-v

Possible choices: 0, 1, 2

Verbosity. 0: Display only errors/warnings, 1: Errors/warnings + info messages, 2: Debug mode.

Default: 1

-profile-time

Enables time-based profiling of the program, dumping the results to the specified file.

If no file is specified, human-readable results are placed into a ‘time_profiling_results.txt’ document in the current directory (’/home/docs/checkouts/readthedocs.org/user_builds/spinalcordtoolbox/checkouts/stable/documentation/source’). If the specified file is a .prof file, the file will instead be in binary format, ready for use with common post-profiler utilities (such as snakeviz).

-trace-memory

Enables memory tracing of the program.

When active, a measure of the peak memory (in KiB) will be output to the file peak_memory.txt. Optionally, developers can also modify the SCT code to add additional snapshot_memory() calls. These calls will ‘snapshot’ the memory usage at that moment, saving the memory trace at that point into a second file (memory_snapshots.txt).

By default, both outputs will be placed in the current directory (’/home/docs/checkouts/readthedocs.org/user_builds/spinalcordtoolbox/checkouts/stable/documentation/source’). Optionally, you may provide an alternative directory (-trace-memory <dir_name>), in which case all files will be placed in that directory instead. Note that this WILL incur an overhead to runtime, so it is generally advised that you do not run this in conjunction with the time profiler or in time-sensitive contexts.