Switches we use include the following.

Per the specification:

• Task. 'Each task has a unique label MUST only include of letters and/or numbers (other characters including spaces and underscores are not allowed). Those labels MUST be consistent across subjects and sessions.
• Acq. 'The OPTIONAL “acq-” key/value pair corresponds to a custom label one may use to distinguish different set of parameters used for acquiring the same task. For example this should be used when a study includes two resting state images - one single band and one multiband. In such case two files could have the following names: sub-01_task-rest_acq-singleband_bold.nii.gz and sub-01_task-rest_acq-multiband_bold.nii.gz, however the user is MAY choose any other label than “singleband” and “multiband” as long as they are consistent across subjects and sessions and consist only of the legal label characters.
• Rec. Similarly the optional “rec-” key/value can be used to distinguish different reconstruction algorithms (for example ones using motion correction).'
• Run. If several scans of the same modality are acquired they MUST be indexed with a suffix: _run-1, _run-2, _run-3 etc. (only integers are allowed as run labels). In the context of functional imaging a run is defined as the same task, but in some cases it can mean different set of stimuli (for example randomized order) and participant responses.' As recommended in the conventions we zero-pad run number; i.e., run-01 not run-1.

Note also, multi-echo data is treated differently (see specification), and a paired JSON file is required. The metadata in the file contains a number of required fields.