object
ImageIO
Value Members
-
final
def
!=(arg0: Any): Boolean
-
final
def
##(): Int
-
final
def
==(arg0: Any): Boolean
-
-
object
ScalarType extends Enumeration
-
final
def
asInstanceOf[T0]: T0
-
def
clone(): AnyRef
-
final
def
eq(arg0: AnyRef): Boolean
-
def
equals(arg0: Any): Boolean
-
def
finalize(): Unit
-
final
def
getClass(): Class[_]
-
def
hashCode(): Int
-
final
def
isInstanceOf[T0]: Boolean
-
final
def
ne(arg0: AnyRef): Boolean
-
final
def
notify(): Unit
-
final
def
notifyAll(): Unit
-
def
read2DScalarImage[S](file: File)(implicit arg0: Scalar[S], arg1: ClassTag[S], arg2: scala.reflect.api.JavaUniverse.TypeTag[S]): Try[DiscreteScalarImage[_2D, S]]
-
def
read3DScalarImage[S](file: File, resampleOblique: Boolean = false, favourQform: Boolean = false)(implicit arg0: Scalar[S], arg1: scala.reflect.api.JavaUniverse.TypeTag[S], arg2: ClassTag[S]): Try[DiscreteScalarImage[_3D, S]]
-
final
def
synchronized[T0](arg0: ⇒ T0): T0
-
def
toString(): String
-
final
def
wait(): Unit
-
final
def
wait(arg0: Long, arg1: Int): Unit
-
final
def
wait(arg0: Long): Unit
-
def
writeNifti[S](img: DiscreteScalarImage[_3D, S], file: File)(implicit arg0: Scalar[S], arg1: scala.reflect.api.JavaUniverse.TypeTag[S], arg2: ClassTag[S]): Try[Unit]
-
def
writeVTK[D <: Dim, S](img: DiscreteScalarImage[D, S], file: File)(implicit arg0: NDSpace[D], arg1: CanConvertToVtk[D], arg2: Scalar[S], arg3: scala.reflect.api.JavaUniverse.TypeTag[S], arg4: ClassTag[S]): Try[Unit]
Inherited from AnyRef
Inherited from Any
Implements methods for reading and writing D-dimensional images
WARNING! WE ARE USING an LPS WORLD COORDINATE SYSTEM
VTK file format does not indicate the orientation of the image. Therefore, when reading from VTK, we assume that it is in RAI orientation. Hence, no magic is done, the same information (coordinates) present in the VTK file header are directly mapped to our coordinate system.
This is also the case when writing VTK. Our image domain information (origin, spacing ..) is mapped directly into the written VTK file header.
This is however not the case for Nifti files! Nifti file headers contain an affine transform from the ijk image coordinates to an RAS World Coordinate System (therefore supporting different image orientations). In order to read Nifti files coherently, we need to adapt the obtained RAS coordinates to our LPS system :
This is done by mirroring the first two dimensions of each point after applying the affine transform
The same mirroring is done again when writing an image to the Nifti format.
Important for oblique images : The Nifti standard supports oblique images, that is images with a bounding box rotated compared to the world dimensions. Scalismo does not support such images. For such images, we offer the user a possibility to resample the image to a domain aligned with the world dimensions and with an RAI orientation. The integrity of the oblique image will be contained in the resampled one. This functionality can be activated by setting a flag appropriately in the scalismo.io.ImageIO.read3DScalarImage method.
Note on Nifti's qform and sform :
As mentioned above, the Nifti header contains a transform from the unit ijk grid to the RAS world coordinates of the grid. This transform can be encoded in 2 entries of the Nifti header, the qform and the sform. In some files, these 2 entries can both be present, and in some cases could even indicate different transforms. In Scalismo, when such a case happens, we favour the sform entry by default. If you wish instead to favour the qform transform, you can do so by setting a flag appropriately in the scalismo.io.ImageIO.read3DScalarImage method.
Documentation on orientation :
http://www.grahamwideman.com/gw/brain/orientation/orientterms.htm
http://www.slicer.org/slicerWiki/index.php/Coordinate_systems
http://brainder.org/2012/09/23/the-nifti-file-format/