Found a typo-or-two in my description. #2 and #3 are nnx1 in shape
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Mark Janikas
Sent: Tuesday, February 13, 2007 4:31 PM
To: Discussion of Numerical Python
Subject: Re: [Numpy-discussion] fromstring, tostrin
This is all very good info. Especially, the byteswap. Ill be testing
it momentarily. As far as a detailed explanation of the problem
In essence, I am applying sparse matrix multiplication. The matrix of
which I am dealing with in the matter described is nxn. Generally, this
matrix is 1-20
Sorry for a private e-mail escaping to this list.
Fred Clare
On Feb 13, 2007, at 4:30 PM, Robert Kern wrote:
> Colin J. Williams wrote:
>
>> Could you give the URL please?
>
> http://svn.scipy.org/svn/numpy/trunk/numpy/doc/HOWTO_DOCUMENT.txt
>
> --
> Robert Kern
>
> "I have come to believe tha
Mary,
Do you think we should adopt the "official" SciPy
docstring format? It is pretty simple.
Did you see Konrad Hinson's comment on NetCDF
modules?
Fred
On Feb 13, 2007, at 4:30 PM, Robert Kern wrote:
> Colin J. Williams wrote:
>
>> Could you give the URL please?
>
> http://svn.scipy.org/sv
On Tue, Feb 13, 2007 at 04:02:10PM -0800, Mark Janikas wrote:
> Yes, but does the code have the same license as NumPy? As I work
> for a software company, where I help with the scripting interface, I
> must make sure everything I use is cited and has the appropriate
> license.
Yes, Scipy and Nu
Mark Janikas wrote:
> I don't think I can do that because I have heterogeneous rows of
> data I.e. the columns in each row are different in length.
like I said, show us your whole problem...
But you don't have to write.read all the data at once with from/tofile()
anyway. Each of your "rows"
Mark Janikas wrote:
> Yes, but does the code have the same license as NumPy? As I work for a
> software company, where I help with the scripting interface, I must make sure
> everything I use is cited and has the appropriate license.
The numpy and scipy licenses are the same except for the de
Yes, but does the code have the same license as NumPy? As I work for a
software company, where I help with the scripting interface, I must make sure
everything I use is cited and has the appropriate license.
MJ
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
On Tue, Feb 13, 2007 at 03:44:37PM -0800, Mark Janikas wrote:
> I don't think I can do that because I have heterogeneous rows of
> data I.e. the columns in each row are different in length.
> Furthermore, when reading it back in, I want to read only bytes of the
> info at a time so I can save m
I don't think I can do that because I have heterogeneous rows of
data I.e. the columns in each row are different in length.
Furthermore, when reading it back in, I want to read only bytes of the
info at a time so I can save memory. In this case, I only want to have
one record in mem at once.
Colin J. Williams wrote:
> Could you give the URL please?
http://svn.scipy.org/svn/numpy/trunk/numpy/doc/HOWTO_DOCUMENT.txt
--
Robert Kern
"I have come to believe that the whole world is an enigma, a harmless enigma
that is made terrible by our own mad attempt to interpret it as though it had
Stefan van der Walt wrote:
> Hi Pierre
>
> On Tue, Feb 13, 2007 at 04:10:09PM -0500, Pierre GM wrote:
>> Dear All,
>> Did we come to some kind of agreement about the formatting of docstring ? In
>> any case, where could I find the 'official' format that Travis recommended ?
>
> Travis checked nu
Mark Janikas wrote:
I am finding that directly packing numpy arrays into binary using the
tostring and fromstring methods
For starters, use fromfile and tofile, to save the overhead of creating
an entire extra string.
fromfile is a function (as it is an alternate constructor for arrays):
nu
Hi Pierre
On Tue, Feb 13, 2007 at 04:10:09PM -0500, Pierre GM wrote:
> Dear All,
> Did we come to some kind of agreement about the formatting of docstring ? In
> any case, where could I find the 'official' format that Travis recommended ?
Travis checked numpy/doc/HOWTO_DOCUMENT.txt a couple of d
Yup. It was faster to:
Use lists for the append, then transform into an array, then transform
into a binary string
Rather than
Create empty arrays and use its append method, then transform into a
binary string.
The last question on the output when then be to test the speed of usin
Dear All,
Did we come to some kind of agreement about the formatting of docstring ? In
any case, where could I find the 'official' format that Travis recommended ?
Thanks a lot in advance
P.
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
ht
On 2/13/07, Mark Janikas <[EMAIL PROTECTED]> wrote:
Good call Stefan,
I decoupled the timing from the application (duh!) and got better results:
from numpy import *
import numpy.random as RAND
import time as TIME
x = RAND.random(1000)
xl = x.tolist()
t1 = TIME.clock()
xStringOut = [ str(i) f
Good call Stefan,
I decoupled the timing from the application (duh!) and got better results:
from numpy import *
import numpy.random as RAND
import time as TIME
x = RAND.random(1000)
xl = x.tolist()
t1 = TIME.clock()
xStringOut = [ str(i) for i in xl ]
xStringOut = " ".join(xStringOut)
f = file
On Tue, Feb 13, 2007 at 11:42:35AM -0800, Mark Janikas wrote:
> I am finding that directly packing numpy arrays into binary using the tostring
> and fromstring methods do not provide a speed improvement over writing the
> same
> arrays to ascii files. Obviously, the size of the resulting files is
Hello all,
I am finding that directly packing numpy arrays into binary using the
tostring and fromstring methods do not provide a speed improvement over
writing the same arrays to ascii files. Obviously, the size of the
resulting files is far smaller, but I was hoping to get an improvement
in
On Feb 9, 2007, at 18:33, Christopher Barker wrote:
> hmmm, this page from unidata:
>
> http://www.unidata.ucar.edu/software/netcdf/software.html#Python
>
> Indicates 4-6 different Python netcfd interfaces!
...
> I think it would be ideal if Unidata could be persuaded to adopt an
> maintain one
21 matches
Mail list logo
