Difference between revisions of "Documentation/3.6/ReleaseNotes"
From Slicer Wiki
| Line 5: | Line 5: | ||
* Multiple 3D View mode is only partially supported in version 3.6 (see [[Modules:MainApplicationGUI-Documentation-3.6#Notes_about_Multiple_3D_Views|this page]]). A more complete implementation is on the list for [[Slicer4]]. | * Multiple 3D View mode is only partially supported in version 3.6 (see [[Modules:MainApplicationGUI-Documentation-3.6#Notes_about_Multiple_3D_Views|this page]]). A more complete implementation is on the list for [[Slicer4]]. | ||
* Due to a bug in the earlier implementation of hierarchical transform trees, multi-level nested transforms loaded from scenes created in version 3.4 won't behave as expected. Reversing the order of the transforms is required. | * Due to a bug in the earlier implementation of hierarchical transform trees, multi-level nested transforms loaded from scenes created in version 3.4 won't behave as expected. Reversing the order of the transforms is required. | ||
| + | * Due to limitations in ITK's gdcm DICOM handling, Slicer is unable to output DICOM format data. We recommend saving new datasets in [http://teem.sourceforge.net/nrrd/format.html NRRD format] using the extension '''.nrrd''' from Slicer's save interface. Note that this currently impacts Slicer's remote I/O as well; multi-file DICOM volumes uploaded to a remote repository using the webservices infrastructure will be collapsed into in a single DICOM file upon upload; however DICOM header information will be preserved. This behavior will be addressed in a software patch subsequent to the 3.6 release. | ||
== Platform Specific Notes == | == Platform Specific Notes == | ||
Revision as of 14:03, 10 June 2010
Home < Documentation < 3.6 < ReleaseNotesKnown Issues
- Multiple 3D View mode is only partially supported in version 3.6 (see this page). A more complete implementation is on the list for Slicer4.
- Due to a bug in the earlier implementation of hierarchical transform trees, multi-level nested transforms loaded from scenes created in version 3.4 won't behave as expected. Reversing the order of the transforms is required.
- Due to limitations in ITK's gdcm DICOM handling, Slicer is unable to output DICOM format data. We recommend saving new datasets in NRRD format using the extension .nrrd from Slicer's save interface. Note that this currently impacts Slicer's remote I/O as well; multi-file DICOM volumes uploaded to a remote repository using the webservices infrastructure will be collapsed into in a single DICOM file upon upload; however DICOM header information will be preserved. This behavior will be addressed in a software patch subsequent to the 3.6 release.
