18 Jan
2010
18 Jan
'10
3:19 p.m.
Is it perhaps the case that Boost MultiArray wasn't designed (or optimised) for numerical calculations?
...
My guess is that the lack of integration with ublas is the usual problem of libraries working in silos, and a (relative) lack of new ublas features in the last few years.
There are probably some stride-related gotchas involved in using shallow_array_adaptors to wrap 1 and 2 dimensional MultiArray implementations. I believe MultiArray concepts/views can handle a more general stride specification than uBlas matrix and vector types may be able to. In particular, the MultiArray 2D storage ordering semantics are not encoded in types the way that uBlas has them. Not insurmountable, just something to be aware of. - Rhys