Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Possible steps to add to DTI pipeline #400

Open
CaseyWeiner opened this issue Sep 30, 2020 · 2 comments
Open

Possible steps to add to DTI pipeline #400

CaseyWeiner opened this issue Sep 30, 2020 · 2 comments

Comments

@CaseyWeiner
Copy link

Possible changes/enhancements to m2g_dwi_pipeline :

Add Conversion Step

  • Many doctors receive their images from the scanner in dicom or .dcm format.
  • I suggest incorporating Rordens dcm2niix here (installs with apt-get)
    • Possibly even better is using dcm2bids (pip installable)
  • Would make m2g more "soup to nuts"
  • Also more effective time-management for clinicians

Add Denoising Steps

Add Option to Perform either eddy_openmp or eddy_cuda

  • Both parallelized, better than eddy_correct
  • See here

Add Bias Field Correction

  • From nipype here, also available in mrtrix3
  • Do this after eddy correction? Or before? I originally thought after
  • ANTs N4BiasField generally considered better than FSL's fast

Streamline Robustness

  • From Dipy here
  • Remove redundant streamlines, evaluate quality of fiber tracking

Connectome Export Format

  • Allow user to choose format of connectome in /outdir/connectomes/atlas_name, including:
    • Edgelist (default)
    • Normalized Edgelist
    • Adjacency Matrix
    • Normalized Adjacency Matrix
  • With these choices, will need to add norm_method parameter to cover the normalization approach the user wants

Customization

  • Allow user to choose steps to be skipped in a run, without checking that step has been run
  • Ex: allowing user to skip eddy_correct without checking for a previous eddy_correct run
    • Some clinicians prefer to skip certain steps to save time
    • This is more personal preference
@CaseyWeiner
Copy link
Author

Any of this sound like a good idea @Lawreros ? I can work on these in my fork if any are of interest

@CaseyWeiner
Copy link
Author

Also I know the lost ROIs are already written to text files, but we could also write one large text file that lists the directories of all the images that are missing ROIs. That way one can immediately see how many subjects lost ROIs instead of looking in each folder.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant