BinaryMask3DMeshSource output mesh in physical space also cause a bug in SNAP, which I noticed before. In SNAP, the scalpel tool works on the 3D mesh view window. However it is working in image space. So the bug behaviour is, when I draw a line with scalpel tool in the mesh view, it showed correctly under my mouse. But when the drawing finished, the mesh view window show the division plane at a different place. After I fix the BinaryMask3DMeshSource to output mesh in image space, this behavior is gone.
<br><br>
<div><span class="gmail_quote">On 12/29/05, <b class="gmail_sendername">Quan Chen</b> <<a href="mailto:quanchen@gmail.com">quanchen@gmail.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div>I was using itk1.80 until recently shift to itk2.20. However, my previous code behave incorrectly.</div>
<div>I just noticed that the BinaryMask3DMeshSource output mesh in physical space. Wouldn't it make the DeformableMesh3DFilter working incorrectly? I assume that the Gradient image used by the DeformableMesh3DFilter is still in image coordinate, and the DeformableMesh3DFilter will place the mesh in the image coordinate.
</div>
<div>I believe it is a nice feature to output the mesh in physical space but in many circumstance, we need the mesh in image space so that we can draw it in the image directly, or work with other images. Can we restore the old behaviour of output the mesh in image coordinate and have two member function of Mesh, one called ConvertToPhysicalSpace(DstImagePointer)
</div>
<div>and ConvertToImageSpace(DstImagePointer). The second function is used to restore the physical coordinate representation back to image coordinate. Probably we should have some flags and functions to return whether the mesh is currently in PhysicalSpace or ImageSpace.
</div></blockquote></div><br>