Documentation/Nightly/Modules/AstroVolume

For the latest Slicer documentation, visit the read-the-docs.

Introduction and Acknowledgements

Authors: Davide Punzo (Kapteyn Astronomical Institute, University of Groningen) Thijs van der Hulst (Kapteyn Astronomical Institute, University of Groningen) Jos Roerdink (Johann Bernoulli Institute for Mathematics and Computer Science, University of Groningen) Contributors: Jean-Christophe Fillion-Robin (Kitware) Steve Pieper (Isomics) Andras Lasso (PerkLab, Queen's) Acknowledgements: This work was supported by the European Research Council under the European Union's Seventh Framework Programme (FP/2007-2013)/ERC Grant Agreement nr. 291-531. Contacts: Davide Punzo, <email>punzodavide@hotmail.it</email>; <email>D.Punzo@astro.rug.nl</email> Thijs van der Hulst, <email>J.M.van.der.Hulst@astro.rug.nl</email> Jos Roerdink <email>j.b.t.m.roerdink@rug.nl</email> Back to SlicerAstro home

Module Description

The AstroVolume can read/write FITS file (astronomical data format) and handle the color function and display of Astro Volumes.

Panels and their use

Handling the loading and writing of FITS files

The display of the Astronomical World Coordinate (WCS) and Data Probing for 2D views

The control of the display coordinates

The control of the 2D color transfer function

The control of the 3D color transfer function

Tools to convert mask from FITS files (e.g., generated by SoFiA) into segmentations objects and viceversa

Astro segmentation editor effect

This editor effect can create multiple segmentation (3D contours) of the input volume.

Contour Levels info:

The Levels can be specified as a list (e.g., 'VALUE1;VALUE2;VALUE3') or in the following format 'FISRT:LAST:SPACING'. In the case of a list, it is possible also to specify for each Contour both the MIN and MAX intensity values of the level (e.g., 'CONTOUR1MIN,CONTOUR1MAX;CONTOUR2MIN,CONTOUR2MAX'). If the string is preceded by 'RMS', the levels are evaluated in units of RMS of the datacube.

The contours in SlicerAstro are a full 3D segmentation. Therefore it can be computationally heavy to segment (marching cubes algorithm) and visualize around the noise range [-2, 2] RMS for large datacubes.