To follow-up on #40
While I don't know the history of the project and the specific use cases it is trying to address, I wonder if effort associated with this project should be coordinated with the team actively working on http://dmri.slicer.org/
From a technical stand-point, I anticipate this could benefit both projects.
Note that this wouldn't prevent the creation of standalone tools independent of Slicer. For example, part of SlicerDMRI are independent of Slicer (see vtkDMRI)
Cc: @ihnorton @ljod @juanprietob @styner @fbudin69500
To follow-up on #40
While I don't know the history of the project and the specific use cases it is trying to address, I wonder if effort associated with this project should be coordinated with the team actively working on http://dmri.slicer.org/
From a technical stand-point, I anticipate this could benefit both projects.
Note that this wouldn't prevent the creation of standalone tools independent of Slicer. For example, part of SlicerDMRI are independent of Slicer (see vtkDMRI)
Cc: @ihnorton @ljod @juanprietob @styner @fbudin69500