Andreas Schuh

PS: I thought there was a command similar to IRTK's labelStats, but apparently I didn't migrate it.

Sorry about that, blame it on my PhD! :-)

Thanks for the suggestion. The source code of the [NIfTI library is included](https://github.com/BioMedIA/MIRTK/tree/7390df6f65808571a8f2eb5582e5adabd27e09dd/Modules/IO/src/nifti). Did you maybe set the [WITH_NiftiCLib](https://github.com/BioMedIA/MIRTK/blob/7390df6f65808571a8f2eb5582e5adabd27e09dd/Modules/IO/CMakeLists.txt#L20) option to ON? By default, it is OFF which means that...

Actually, the error was not picked up because it is in an `mirtkAssert` statement which is discarded in `Release` mode.

Or at least resample with y axis corresponding to AC-PC line... not sure if BS cut needs to parallel to this. It's anyway only approximate / somewhat arbitrary for the...

Thanks for pointing out this new library. Looks pretty neat on first glance. The macros in the `mirtk/Options.h` header were always just intended as placeholder for the time being. Still...

Sorry for the late reply. I only recently got my hands on a Windows machine again and gave it a shot. The `DEPENDS_TBB_DIR` should be set to the path where...

IMHO These are different use cases. MITK here is meant as image viewer mainly and for visualizing registration results. The nipype integration is rather for workflow design and execution.

Besides a MITK Plugin, a [3D Slicer](https://www.slicer.org/) [extension](http://wiki.slicer.org/slicerWiki/index.php/Documentation/Nightly/Developers/FAQ#What_is_an_extension_.3F) would be nice as well. EDIT: Slicer has FFD registration modules based on the ANTs/ITK filters and seems to provide a number...

> _Registration plugin_ is quite vague. Therefore the reference to the MIRTK / Viewer ;-)