Comments for Nicola Candussi @ FluidInteractive http://www.fluidinteractive.com/blog/wordpress This this my blog. You'll find a little bit of everything. Sun, 20 May 2012 05:45:35 +0000 http://wordpress.org/?v=2.7.1 hourly 1 Comment on About OpenMVL by nicola http://www.fluidinteractive.com/blog/wordpress/?p=26&cpage=1#comment-3 nicola Tue, 24 Feb 2009 16:27:28 +0000 http://www.fluidinteractive.com/blog/wordpress/?p=26#comment-3 Hi vicviper, Thanks for the feedback. I agree it would be nice if there was a standardized Matrix/Vector library... Regarding the sharing of data, there is an expression in OpenMVL, called cmat, that allows you to take a pointer to raw data and use it directly in your matrix/vector expressions. If you take a look at tutorial.hpp, there is an example of how to use it. - Nicola Hi vicviper,
Thanks for the feedback. I agree it would be nice if there was a standardized Matrix/Vector library… Regarding the sharing of data, there is an expression in OpenMVL, called cmat, that allows you to take a pointer to raw data and use it directly in your matrix/vector expressions. If you take a look at tutorial.hpp, there is an example of how to use it.

- Nicola

]]> Comment on About OpenMVL by vicviper http://www.fluidinteractive.com/blog/wordpress/?p=26&cpage=1#comment-2 vicviper Tue, 24 Feb 2009 12:08:01 +0000 http://www.fluidinteractive.com/blog/wordpress/?p=26#comment-2 I've been taking a look at openVML and looks very promising, also a good step in the direction of having a standarised (and very much needed) math/vector/matrix library. As many others, I programmed my own matrix libraries, and also used several external libraries, and found quite troublesome that for example, using a graphics engine and a physics engine, both coming with its own matrix implementation, and being totally incompatible, that is, when you want to copy data from one to the other, you have to copy the elements one by one. At some point, I found a solution that might be interesting for you to explore, although I think it will be very difficult to implement at this point: latest revision of C++ comes with a template called std::array, which is basically a very basic fixed size array, with no memory allocation and no overhead at all. What I do in my library is that my vector and matrix types extend std::array , and I try that my other libraries that receive vector and matrix input, use std::array as input, instead of my own types. That way, you can make the data interoperable between libraries without having to perform any kind of conversion, since the libraries read the data at std::array level. Unfortunately, this trick is useful only if everybody uses it on their libraries. I’ve been taking a look at openVML and looks very promising, also a good step in the direction of having a standarised (and very much needed) math/vector/matrix library.

As many others, I programmed my own matrix libraries, and also used several external libraries, and found quite troublesome that for example, using a graphics engine and a physics engine, both coming with its own matrix implementation, and being totally incompatible, that is, when you want to copy data from one to the other, you have to copy the elements one by one.

At some point, I found a solution that might be interesting for you to explore, although I think it will be very difficult to implement at this point: latest revision of C++ comes with a template called std::array, which is basically a very basic fixed size array, with no memory allocation and no overhead at all. What I do in my library is that my vector and matrix types extend std::array , and I try that my other libraries that receive vector and matrix input, use std::array as input, instead of my own types.

That way, you can make the data interoperable between libraries without having to perform any kind of conversion, since the libraries read the data at std::array level.

Unfortunately, this trick is useful only if everybody uses it on their libraries.

]]>