[Insight-users] Fwd: [Community] Demons Deformable Registration and Paraview

[Yago Diez]

Tim,

I did a small test visualizing 2D deformation fields in paraview, I used
.vtk files but .mhd files should also work fine.

You can use paraview to visualize deformation fields.  You have a
description on how to do this in the 8.15 section of the itk guide
(Visualizing Deformation fields).

Mainly you have to:

1) open the file with paraview
2) Open a calculator with the following formula:

scalars_X*iHat+scalars_Y*jHat+0*kHat

The idea here is to obtain a 3D vector with z component =0 and the other
components the deformation components. For 3D you probably want to
represent all components using something like (not tested!) ->
scalars_X*iHat+scalars_Y*jHat+scalars_Z*kHat

3) In order to visualize this, you have to use a "gliph", here you can
control the number of points that you represent and so on, you obtain
something like the "campDefDemons" attached file.

Hope this helps
Yago


On Sun, Dec 8, 2013 at 6:07 AM, Matt McCormick
<matt.mccormick at kitware.com>wrote:

> Hi Tim,
>
> On Sat, Dec 7, 2013 at 11:36 PM, Tim Bhatnagar <tim.bhatnagar at gmail.com>
> wrote:
> > Hey Matt,
> >
> > Sorry to re-visit this specific email... in your message, you said:
> >
> > "The displacement fields output of ITK's deformable image registration
> > represent the displacement of a point in the FixedImage to a point in
> > the MovingImage.  Therefore overlaying the displacement field vector
> > glyphs on the FixedImage should give the correct visualization.  The
> > start of the arrow sits on its location in the input FixedImage, and
> > the tip of the arrow glyphs are directed towards where a given pixel
> > in the FixedImage will move to in the MovingImage."
> >
> > However, in the Demons examples that are built with the ITK package, an
> > 'output' image from the registration is produced by passing the
> movingImage
> > into the WarpImageFilter, and utilizing the newly created deformation
> field.
> > This makes it seem like the deformation field actually takes the
> movingImage
> > form into the fixedImage form, not the other way around.
>
> Yes, it is true that the WarpImageFilter takes the movingImage and
> transforms it to the fixedImage space.  Different perspectives could
> be taken on what is moving or how it is moving, but all of the above
> is correct.
>
> Hope this helps,
> Matt
> _____________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Kitware offers ITK Training Courses, for more information visit:
> http://www.kitware.com/products/protraining.php
>
> Please keep messages on-topic and check the ITK FAQ at:
> http://www.itk.org/Wiki/ITK_FAQ
>
> Follow this link to subscribe/unsubscribe:
> http://www.itk.org/mailman/listinfo/insight-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.itk.org/pipermail/insight-users/attachments/20131209/323d3499/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: campDefDemons.png
Type: image/png
Size: 87422 bytes
Desc: not available
URL: <http://www.itk.org/pipermail/insight-users/attachments/20131209/323d3499/attachment-0001.png>