BIDS-Apps/BrainSuite

Name: BrainSuite

Owner: BIDS Apps

Description: null

Created: 2017-09-06 17:15:14.0

Updated: 2017-09-06 23:20:01.0

Pushed: 2018-02-23 18:07:30.0

Homepage: null

Size: 105

Language: Python

GitHub Committers

UserMost Recent Commit# Commits

Other Committers

UserEmailMost Recent Commit# Commits

README

BrainSuite BIDS-App (Light-weight)

This is the BIDS-App version of BrainSuite17a (http://brainsuite.org/).

Description

BrainSuite is an open-source collection of software for processing structural and diffusion MRI, with planned enhancements to support functional MRI. This BIDS-App version of BrainSuite provides a portable, streamlined method of performing primary BrainSuite analysis workflows. These stages include:

Usage
Data input requirements

This App requires at least one T1w image. If no corresponding DWI data is found, the App will only run CSE and SVReg on the T1w(s). If there are corresponding DWI data (DWI image data, bval file, and bvec file), the App will grab the nearest DWI data (i.e. within sub-ID/ directory or sub-ID/ses directory) and will perform CSE, SVReg, and BDP.

If there are unequal number of T1w data and DWI data, the App will process the T1w and DWI data in pairs until there are no matched pairs left. The pairs will be matched according to the run numbers (i.e. run-01).

Command line arguments
e: run.py [-h]
          [--participant_label PARTICIPANT_LABEL [PARTICIPANT_LABEL ...]]
          [--stages {CSE,SVREG,BDP} [{CSE,SVREG,BDP} ...]]
          [--atlas {BSA,BCI}] [--singleThread] [-v]
          bids_dir output_dir {participant}

nSuite17a BIDS-App (T1w, dMRI)

tional arguments:
ds_dir              The directory with the input dataset formatted
                    according to the BIDS standard.
tput_dir            The directory where the output files should be stored.
                    If you are running group level analysis this folder
                    should be prepopulated with the results of
                    theparticipant level analysis.
articipant}         Level of the analysis that will be performed. Multiple
                    participant level analyses can be run independently
                    (in parallel) using the same output_dir.

onal arguments:
, --help            show this help message and exit
participant_label PARTICIPANT_LABEL [PARTICIPANT_LABEL ...]
                    The label of the participant that should be analyzed.
                    The label corresponds to sub-<participant_label> from
                    the BIDS spec (so it does not include "sub-"). If this
                    parameter is not provided all subjects should be
                    analyzed. Multiple participants can be specified with
                    a space separated list.
stages {CSE,SVREG,BDP} [{CSE,SVREG,BDP} ...]
                    Processing stage to be run. Space delimited list.
atlas {BSA,BCI}     Atlas that is to be used for labeling in SVReg.
                    Default atlas: BCI-DNI. Options: BSA, BCI.
singleThread        Turns on single-thread mode for SVReg.
, --version         show program's version number and exit

To run it in participant level mode:

er run -ti --rm \
 /path/to/local/bids/input/dataset/:/data \
 /path/to/local/output/:/output \
ainsuitebids \
ata /output participant --participant_label 01

Where 01 is the “sub-01”. User can supply multiple participant labels by listing them delimited by space (i.e. –participant_label 01 02). If ` --stages`stages is not specified, the default is to run all stages.

User can remove ` --participant_label <ids-list>` argument to have all subjects processed.

All sessions will be processed. The output files will be located in the output folder specified.

Support

Questions about usage can be submitted to http://forums.brainsuite.org/. Issues or suggestions can be directly submitted as an issue to this Github Repository.

FYI

This work is supported by the National Institutes of Health's National Center for Advancing Translational Sciences, Grant Number U24TR002306. This work is solely the responsibility of the creators and does not necessarily represent the official views of the National Institutes of Health.