[vtk-developers] A new way to look at images

[cartik sharma]

Hi David,

Interesting functionality and perspective. I like the way the mapper
implicitly handles
image reslicing and event callbacks.

Could we implement this so we have the same mapper for reslicing of multiple
datasets or would this imply creating one mapper for each dataset.

Best regards,
Cartik

On Sat, Jan 22, 2011 at 9:52 AM, David Gobbi <david.gobbi at gmail.com> wrote:

> Hi Dean,
>
> Thanks for the feedback! I'll add the tcl example to my branch.
>
> The background issue is what I'm working on right now.  Early next
> week you should see an option for whether to fill the viewport (the
> current behavior) or to clip at the image bounds.
>
> For the interactor, I can add key bindings for "X", "Y", and "Z" to
> select the view direction.  And "R" for re-centering the view.
>
> Did you notice that the example didn't need window/level observers?
> The new InteractorStyleImage automatically finds the "property" object
> and does the adjustment.  With the old vtkImageActor, the users had to
> write window/level observers to adjust an external
> vtkImageMapToWindowLevelColors object.
>
>  - David
>
> On Sat, Jan 22, 2011 at 8:15 AM, Dean Inglis <dean.inglis at camris.ca>
> wrote:
> > Hi David,
> >
> > truly amazing! Very easy to scroll or oblique slice.  I couldnt see
> > the colored background in the renderer: it seems like the new
> > vtkImage/Mapper
> > takes up the whole viewport?  It would be nice to have a reset in the
> > interactor style
> > to reposition the image slice along one of the orthogonal data axes of a
> 3D
> > image,
> > but this should be easy to do with a callback.
> > Attached is the tcl version for anyone who wants it.
> >
> > Dean
> >
> > ----- Original Message -----
> > From: Will Schroeder
> > To: David Gobbi
> > Cc: VTK Developers
> > Sent: Saturday, January 22, 2011 9:32 AM
> > Subject: Re: [vtk-developers] A new way to look at images
> > David this is very clever and seems pretty intuitive to use (I did not
> > actually try it).
> > I think my initial (minor) concern is naming, while I think what you've
> come
> > up is pretty good I can see how a novice might get confused.  Did you
> > consider something like "ImageResliceActor", "ResliceActor" or simply
> > "Reslice"?
> > W
> >
> >
> > On Fri, Jan 21, 2011 at 6:53 PM, David Gobbi <david.gobbi at gmail.com>
> wrote:
> >>
> >> Hi All,
> >>
> >> I've been experimenting with a new way of rendering 3D images in VTK.
> >> So far, it is working fairly well.  Here is a rough description of the
> >> new VTK classes I've written:
> >>
> >> vtkImage - a new prop for image viewing, analogous to vtkVolume and
> >> vtkActor
> >> vtkImageProperty - holds the lookup table, window/level, etc.
> >> vtkImageMapper3D - a new mapper that does image reslicing and texturing
> >>
> >> Using these classes is very simple: just set up the camera, and the
> >> vtkImage object will automatically display the slice at the camera
> >> focal point.  To show a different slice, just move the focal point so
> >> that it lies at a different position in the 3D image.  To slice in a
> >> different orientation, rotate the camera around the focal point.  In
> >> other words, the slicing is completely controlled by the camera.  This
> >> makes everything work nicely with the VTK interactors, and also
> >> simplifies the intermixing of images and geometry.
> >>
> >> My reason for making this class is that I've seen plenty of users on
> >> the list who struggle with vtkImageReslice and with vtkImageViewer.  I
> >> wanted to make it as easy to view an image in VTK as it is to view an
> >> actor. I have the code on my github account
> >> git://github.com/dgobbi/VTK.git in the branch "image-prop"
> >> http://github.com/dgobbi/VTK/tree/image-prop
> >>
> >> The code includes a modified vtkInteractorStyleImage class that has
> >> new interactions for rotating the camera with shift-leftbutton (for
> >> oblique slicing) and for adjusting the focal point with
> >> shift-middlebutton (for slicing through the image).  There is also a
> >> python example in Examples/ImageProcessing/Python/ImageMapper3D.py.
> >> All of this is still preliminary development, but so far I haven't
> >> encountered any show-stopping bugs.
> >>
> >> Please let me know what you think.  I'll try to make a wiki page with
> >> more details next week.
> >>
> >>  - David
> >> _______________________________________________
> >> Powered by www.kitware.com
> >>
> >> Visit other Kitware open-source projects at
> >> http://www.kitware.com/opensource/opensource.html
> >>
> >> Follow this link to subscribe/unsubscribe:
> >> http://www.vtk.org/mailman/listinfo/vtk-developers
> >>
> >
> >
> >
> > --
> > William J. Schroeder, PhD
> > Kitware, Inc.
> > 28 Corporate Drive
> > Clifton Park, NY 12065
> > will.schroeder at kitware.com
> > http://www.kitware.com
> > (518) 881-4902
> >
> > ________________________________
> >
> > _______________________________________________
> > Powered by www.kitware.com
> >
> > Visit other Kitware open-source projects at
> > http://www.kitware.com/opensource/opensource.html
> >
> > Follow this link to subscribe/unsubscribe:
> > http://www.vtk.org/mailman/listinfo/vtk-developers
> >
> >
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Follow this link to subscribe/unsubscribe:
> http://www.vtk.org/mailman/listinfo/vtk-developers
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/vtk-developers/attachments/20110122/051e66c3/attachment.html>