tiff): can read/write single/series of frames Not well suited as a general-purpose 3D image file format (use NRRD format instead). For brain imaging, use Nifti format instead. img.gz): Image orientation is specified ambiguously in this format, therefore its use is strongle discouraged. Important limitation: image axis directions cannot be stored in this file format.Īnalyze (.hdr. mhd): Coordinate system: LPS (AnatomicalOrientation in the file header is ignored). To load an image file as segmentation (also known as label image, mask, region of interest) see Segmentations module documentation Coordinate system: as defined in the file header (usually LPS). nhdr): General-purpose 2D/3D/4D file format. Support of writing DICOM Segmentation Objects is provided by the Reporting extension
#Metaimage volume series
Limited support for writing image volumes in DICOM format is provided by the Create DICOM Series module. can be exported using DICOM module’s export feature. Image volumes, RT structure sets, dose volumes, etc. SlicerHeart extension: 2D/3D/4D ultrasound (GE, Philips, Eigen Artemis, and other)įor a number of dMRI formats we recommend use of the DICOM to NRRD converter before loading the data into Slicer. SlicerRT extension: DICOM RT Structure Set, RT Dose, RT Plan, RT Image Quantitative Reporting extension: DICOM Segmentation objects, Structured reports Slicer core: CT, MRI, PET, X-ray, some ultrasound images secondary capture with Slicer scene (MRB) in private tag Coordinate system: LPS (as defined by DICOM standard). Readers may support 2D, 3D, and 4D images of various types, such as scalar, vector, DWI or DTI, containing images, dose maps, displacement fields, etc.ĭICOM (.dcm, or any other): Slicer core supports reading and writing of some data types, while extensions add support for additional ones.
Saving happens with the Save Data toolbar button. Loading can happen in two ways: drag&drop file on the application window, or by using the Load Data button on the toolbar. Non-DICOM data, covering all types of data ranging from images (nrrd, nii.gz, …) and models (stl, ply, obj, …) to tables (csv, txt) and point lists (json). More details are provided in the DICOM module documentation. ĭata in the scene can be saved to DICOM files in two steps:Įxport to database: save data from the scene into the application’s DICOM databaseĮxport to file system: copy DICOM files from the database to a chosen folder in the file system The DICOM browser is accessible from the toolbar using the DICOM button. Load: get data objects into the scene, by double-clicking on items in the DICOM browser.
Import: add files into the application’s DICOM database, by switching to DICOM module and drag-and-dropping files to the application window DICOM data ¶ĭICOM is a widely used and sophisticated set of standards for digital radiology.ĭata can be loaded from DICOM files into the scene in two steps: There are two major types of data that can be loaded to Slicer: DICOM and non-DICOM.
0 kommentar(er)
