Difference between revisions of "Documentation/Nightly/SlicerApplication/SavingData"
(4.1 -> Nightly) |
(Add developer section) |
||
Line 65: | Line 65: | ||
|text=Many file formats are 'lossy' when it comes to saving and restoring image orientation metadata. For example, Analyze format cannot store all image orientations and .vtk format for images does not store orientation information at all. When exporting data to a new format, please reload the data to ensure the correct data has been saved. In general, NRRD, NIfTI, and Meta formats preserve exported information. All meta-information other than image content and image orientation (such as patient name, acquisition-related details) is lost when the image loaded from DICOM is saved into any of the non-DICOM formats! | |text=Many file formats are 'lossy' when it comes to saving and restoring image orientation metadata. For example, Analyze format cannot store all image orientations and .vtk format for images does not store orientation information at all. When exporting data to a new format, please reload the data to ensure the correct data has been saved. In general, NRRD, NIfTI, and Meta formats preserve exported information. All meta-information other than image content and image orientation (such as patient name, acquisition-related details) is lost when the image loaded from DICOM is saved into any of the non-DICOM formats! | ||
}} | }} | ||
+ | |||
+ | =Information for Developers= | ||
+ | Consider reading the [[Documentation/{{documentation/version}}/Developers/IO|Developers/IO]] page for information about programmatically loading and writing files. | ||
<!-- ---------------------------- --> | <!-- ---------------------------- --> | ||
{{documentation/{{documentation/version}}/slicerapplication-footer}} | {{documentation/{{documentation/version}}/slicerapplication-footer}} | ||
<!-- ---------------------------- --> | <!-- ---------------------------- --> |
Revision as of 15:54, 22 April 2013
Home < Documentation < Nightly < SlicerApplication < SavingData
Introduction
It is possible to save the current scene (including all scene snapshots, fiducial lists, etc.) and/or individual datasets. The "Save Data" panel is accessed through the File menu using File->Save, or by using the CTRL-S keyboard shortcut. Note: in order to provide a rich set of options for saving data, the Save Scene and Unsaved Data interface does not behave in the way that Windows data explorer and Gnome file browser behave. The user is encouraged to read this documentation carefully, and be mindful when specifying save options. Consider using this interface in the following three steps:
Select What to SaveWhen invoked, Slicer will select the scene and any modified datasets for saving by default. This set of selections can be overridden by manipulating the checkboxes in the leftmost column. In addition to the checkbox in the 'Node Name column header, two buttons in the panel's upper left provide convenient selection shortcuts for commonly-used selection states arrayed in the interface: Select Save Destinations
Modify Filenames & Formats
Specifying a scene file to save: The Scene Description entry is always listed in the top row of the table. If a scene has already been loaded from a MRML file, then its filename is presented as the default choice. To save the scene into a new MRML file, either provide an alternate file name, or provide a new Data Directory. The GUI panel is shown below: Supported formatsPlease refer to the supported data format page.
Information for DevelopersConsider reading the Developers/IO page for information about programmatically loading and writing files. |