Hi all, Hi Peter,

I've been using the mitk::FiberBundleXMapper2D and 3D in our program and I found a really strange behavior. I searched all day, to no avail. For the same data (a polydata at the same adress in memory), my lines are at different positions in my mapper (or at least *seen* at different positions). As you can almost see in the screenshot [1] the FiberBundleX is placed perfectly in 3D, but not in 2D. (They fit if you make the FiberBundleX invisible, trust me!) Without any explanation, you can probably already see that the image doesn't make sense.

Either the 2D or 3D mapper is wrong here. I searched in mitk::FiberBundleXMapper?D code to see if the mapper modify its data in some way and, AFAIK, it doesn't. I can't think of any reason why my data in 2D is 2.0 times bigger. I know that the image's spacing is [2.0, 2.0, 2.0] (I use the spacing to generate the FiberBundleX), but the spacing is the same for the 3D mapper... _it's the same data_.

If you have any hints about what's going on, something that explains this bizarre behavior, I'm really interested!
As always, thank you for your time.

[1] http://i.imgur.com/yfEBe1H.png

--
Logo Imeka <http://imeka.ca/>     Nil Goyette, M.Sc.
www.imeka.ca <http://imeka.ca/>

------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
mitk-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mitk-users

Reply via email to