Thanks, this is pretty much what I ended up doing.
Once I got that into python, I converted it to a narray
-Original Message-
From: cplusplus-sig-bounces+enrico.ng=lmco@python.org
[mailto:cplusplus-sig-bounces+enrico.ng=lmco@python.org] On Behalf Of Jim
Bosch
Sent: Thursday, J
On Thu, 2010-01-21 at 09:10 -0500, Ng, Enrico wrote:
> I had hoped that there was something simple after seeing the numeric part in
> the documentation.
Well, if you're content with a 1-D array and speed isn't a big issue,
you can just copy the elements of your array into a Python list like
this:
That was just my example, I do not require it to go into a numeric array. It
just seemed like the way I was suppose to do it based on the documentation. As
long as I can access the data in any form in python, I'll be happy. And I only
need to read the data, I do not need to modify the array.
Interesting, I changed it to the format you suggest and it seems to work.
However, I changed it back to this way:
global_annotations = {‘return_internal_reference’:’true’}
and it stopped working. I confirmed there was nothing in there before I added
my annotation, so that seems strange to me. On
If you can build a wrapper function which returns a
boost::numeric::ublas::vector, you can use the wrappers into
the mds-utils library (http://code.google.com/p/mds-utils/ ... it's
my library). If you build the doxygen documentation, you'll find a
"Python C++ extensions utilities": use the "vecto
