[PYTHON MATRIX-SIG] Efficient data reading
Earl J Spillar
spillar@uwyo.edu
Wed, 06 Mar 1996 16:56:14 -0700 (MST)
Gentlemen- thanks for your answers.
James Hugunin said:
BTW - has anybody heard anything more about the image module discussed
a while back on this list? It sounds like it might be very helpful
here.
Probably will be helpful. A lot of what astronomers call "image processi=
ng"
is actually numerical analysis though, so the other Matrix stuff is very
important.
I explicitly designed the numeric module to not access file objects...
strongly encourage people to use pickling as their "native" format for =
storing arrays which I think is almost always the best choice..."
I agree completely with this philosophy. I will certainly keep my data =
in
pickled format. I do have a need to get the data in and out to use "lega=
cy" apps
though, hence the question.
(Note to experts, this can actually be written as add(a, 2, a) in
which case you don't need that extra memory, but if you want to
write a lot of code like this, then you should probably be working
in C anyway).
Thanks for the trick. I WILL be doing a lot of code like this, but it =
needs to
be "reconfigured" frequently. I want to prototype in the fluid Python =
environment
and then freeze bottlenecks into C.
Konrad said:
There is no difference between the "array module" and the
"numerical module". The module "Numerical" simply imports
objects from the array module. Or are you referring to the old array mod=
ule?
Actually, was thinking about the old array module. I guess when I saw =
the
Numeric.fromString method, I thought C string, and CR/LF etc, NULLs, and =
thought
it wouldn't work... primitive thinking on my part.
Thanks for the help!
Earl Spillar
spillar@uwyo.edu
http://plains.uwyo.edu/~spillar/
=================
MATRIX-SIG - SIG on Matrix Math for Python
send messages to: matrix-sig@python.org
administrivia to: matrix-sig-request@python.org
=================