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.

Sign up for GitHub

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

Jump to bottom

Native DICOM tractography #12

Open
ljod opened this issue Jan 6, 2016 · 1 comment
Open

Native DICOM tractography #12

ljod opened this issue Jan 6, 2016 · 1 comment
Labels
feature request

Comments

@ljod
Copy link
Member

ljod commented Jan 6, 2016

  • DICOM contains more information than we currently support, which must not be lost
  • Currently this information is in MRML (visualization) and vtkPolyData (data).
  • Should visualization information changes really modify the input tractography file? In the case of images, DICOM data are not usually modified and are considered more read-only from the scanner. However in this case, saving the data with a color change would change the tractography file.
@ljod ljod added this to the Slicer DMRI refactoring milestone Jan 6, 2016
@ljod ljod changed the title re-architect internal tractography data structures to better correspond to DICOM tractography Native DICOM tractography Jun 8, 2016
@ljod
Copy link
Member Author

ljod commented Jun 8, 2016

The need for native DICOM tractography will be reviewed when DICOM import/export of tractography are ready, as this is the first step.

@ljod ljod removed this from the Slicer DMRI refactoring milestone Jun 8, 2016
kellygwang pushed a commit to kellygwang/SlicerDMRI that referenced this issue Aug 8, 2023
@jhlegarreta
DOC: Remove non-existing section tag in ORG atlas link (SlicerDMRI#12)
60f19f9 
Remove non-existing section tag in ORG atlas link.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ljod