Hello Taylor, the reason to use quaternions is the fact that most tracking device also use this representation. We want to keep the raw tracking data without any conversion inside the NavigationData objects. But you are right, there might be problems with non-normalized Quaternions. At the moment we are working on some improvements of the IGT module which will be merged to the MITK master soon after the september release. We also worked on the problem with quaternion normalization and compatibility to other representations (e.g. mitk::AffineTransform3D) of the NavigationData class. Maybe this is of interest for you.
Greets, Alfred Hello mitk-users, IGT developers - I'm curious about decision to use mitk::Quaternion for the orientation type of mitk::NavigationData. Is there a use case where NavigationData needs to support scale transformations? If not, I would think it's best to use versor (e.g. itk::Versor) so that accidentally non-normalized Quaternion bugs are eliminated. Thoughts? Taylor ------------------------------------------------------------------------------ Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58041391&iu=/4140/ostg.clktrk _______________________________________________ mitk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mitk-users
