sct_dmri_display_bvecs¶
Display scatter plot of gradient directions from bvecs file. If you have multi-shell acquisition,you can provide also bvals file to display individual shells in q-space.
usage: sct_dmri_display_bvecs -bvec <file> [-bval <file>] [-h] [-v <int>]
[-profile-time [<file>]]
[-trace-memory [<folder>]]
MANDATORY ARGUMENTS¶
- -bvec
Input bvecs file. Example:
sub-001_dwi.bvec
OPTIONAL ARGUMENTS¶
- -bval
Input bval file (for multi-shell acquisition). Example:
sub-001_dwi.bval
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 assnakeviz
).- -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 additionalsnapshot_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.