Batch Processing Using the GUI

DSI Studio provides GUI batch functions for common multi-subject workflows. Test a batch operation on a small subset before running it on an entire study, especially when files will be renamed or moved.

Step B0: XNAT Download

Use Batch Processing → Step B0: XNAT Download to connect to an XNAT server, select project data, and choose a local download directory.

image

Step B1: Rename and organize DICOM

The DICOM rename functions move and rename files. Keep a backup of the original data and test the operation first.

For command-line batch organization, see Rename DICOM CLI.

Step B2: Create SRC files

Use the input route that matches the source data:

Current DSI Studio source files use the .sz extension.

After source creation, run SRC quality control before reconstruction or group analysis.

Step B3: Batch reconstruction

Use Step B3: SRC to FIB to reconstruct multiple .sz files. The normal reconstruction settings and quality checks still apply; batch processing should not be used to bypass visual QC.

Current reconstructed files use .fz.

See Step T2: Reconstruction for reconstruction choices.

For population/connectometry analysis, reconstruct the cohort with QSDR using the same template space and resolution, then create a .dz database using Correlational Tractography.

For longitudinal or cross-sectional differential analysis, follow the study-specific workflow in Differential Tractography.

Step B4: Automatic fiber tracking

Use Step B4: Automatic Fiber Tracking when named pathways should be mapped across many subjects.

image

  1. Select the .fz files to process.
  2. Select the tract or tract groups.
  3. Keep the FIB/template-derived defaults initially.
  4. Run a small subset and inspect the anatomy in Step T3.
  5. Only change tolerance, track density, pruning, or other tracking parameters when the anatomical results justify the change.
  6. Apply the finalized settings consistently to the study cohort.

AutoTrack tolerance and track-to-voxel ratio are derived from the loaded FIB/template when not explicitly fixed; avoid copying old universal numeric defaults into new studies.

See Automatic Fiber Tracking for the current workflow and troubleshooting guidance.

Troubleshooting batch AutoTrack

If many subjects produce no result or implausible anatomy:

Do not solve a systematic acquisition or reconstruction problem by repeatedly relaxing AutoTrack constraints.

Command-line alternatives

For automated pipelines or cluster processing, the corresponding command-line actions are: