Skip to content

[WIP] Write interfaces for MRTrix3 #1126

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

Merged
merged 37 commits into from
Sep 7, 2015
Merged

Conversation

oesteban
Copy link
Contributor

List of executables in new MRTrix3:

  • In bin/:
    • 5tt2gmwmi
    • 5tt2vis
    • 5ttedit
    • 5ttgen
    • afdconnectivity
    • amp2sh
    • dcmedit
    • dcminfo
    • dirflip
    • dirgen
    • dirmerge
    • dirorder
    • dirsplit
    • dirstat
    • dwi2adc
    • dwi2fod
    • dwi2mask
    • dwi2noise
    • dwi2qbi
    • dwi2response
    • dwi2tensor
    • dwiextract
    • fixel2sh
    • fixel2voxel
    • fixelmult
    • fixelthreshold
    • fod2fixel
    • gen_planar_ROI
    • label2colour
    • labelconfig
    • maskfilter
    • mesh2pve
    • mrcalc
    • mrcat
    • mrclusterstats
    • mrconnect
    • mrconvert
    • mrcrop
    • mrfilter
    • mrinfo
    • mrmath
    • mrresize
    • mrstats
    • mrthreshold
    • mrtransform
    • mrview
    • peaks2amp
    • sh2amp
    • sh2peaks
    • sh2power
    • sh2response
    • shbasis
    • shconv
    • shview
    • tck2connectome
    • tck2vtk
    • tckedit
    • tckfixcount
    • tckgen
    • tckimport
    • tckinfo
    • tckmap
    • tcknodeextract
    • tcknormalise
    • tcksample
    • tcksift
    • tckstats
    • tensor2metric
    • transformcalc
    • tsfdivide
    • tsfinfo
    • tsfmult
    • tsfthreshold
    • warpinit
  • In scripts/:
    • act_anat_prepare_freesurfer
    • act_anat_prepare_fsl
    • average_response
    • blend
    • convert_bruker
    • data
    • dwibiascorrect
    • foreach
    • fs_parc_replace_sgm_first
    • lib
    • revpe_distcorr
    • revpe_dwicombine

@oesteban
Copy link
Contributor Author

@chrisfilo @satra I was wondering your opinion about this new set of interfaces for MRTrix3. I'd also need your opinion about the new interfaces.mrtrix3 module, to live besides the former mrtrix 0.2.

Regarding the features it currently contains, I think it covers enough part of MRTrix3 to merge already. What do you think of maintaining the list of binaries in the wiki and update there the ones supported?

@oesteban
Copy link
Contributor Author

oesteban commented Sep 1, 2015

May I ask for your revision? @satra, @chrisfilo (or anyone interested in having MRTrix3 interfaces...)

Thanks a lot! 👍

@satra
Copy link
Member

satra commented Sep 2, 2015

@oesteban - i think it's fine for mrtrix3 to live beside mrtrix2. would it be possible for you to encourage the mrtrix folks to generate slicer execution model like xml files? then we could automatically generate interfaces for these tools.

http://www.slicer.org/slicerUncyclo/index.php/Documentation/Nightly/Developers/SlicerExecutionModel

i'm also fine with incrementally adding mrtrix tools and having a wiki to show support. we could start doing this for the big packages in general. over the next few years, i would like to instrument external software to automatically generate specs on how to run them. that's the most scalable option.

@oesteban
Copy link
Contributor Author

oesteban commented Sep 7, 2015

Great, thanks!

I have created a new wiki page for this: https://github.com/nipy/nipype/wiki/Status-of-interfaces

I will post an issue on the github of MRTrix3 to suggest the xml descriptions 👍

oesteban added a commit that referenced this pull request Sep 7, 2015
[ENH] Write interfaces for MRTrix3
@oesteban oesteban merged commit 726870e into nipy:master Sep 7, 2015
@oesteban oesteban deleted the enh/MRTrix3 branch September 7, 2015 16:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants