Hi,
1) I'd like to get it going so that we can push out an electronic issue
after the SciPy conference (in September)
That would be great for the "fame" of numpy and scipy :)
2) I think it's scope should be limited to papers that describe
algorithms and code that are in NumPy / SciPy / Sci
On 31/05/07, Travis Oliphant <[EMAIL PROTECTED]> wrote:
> 2) I think it's scope should be limited to papers that describe
> algorithms and code that are in NumPy / SciPy / SciKits. Perhaps we
> could also accept papers that describe code that depends on NumPy /
> SciPy that is also easily availa
Hi everybody,
I'm sorry for the cross posting, but I wanted to reach a wide audience
and I know not everybody subscribes to all the lists.
I've been thinking more about the "SciPy Journal" that we discussed
before and I have some thoughts.
1) I'd like to get it going so that we can push out
Christopher Hanley wrote:
> Hi,
>
> Could someone please re-create the numpy-1.0.3.tar.gz file that is
> currently being distributed from sourceforge? That tar file includes
> the following:
>
I've fixed the tar-ball. It is named numpy-1.0.3-2.tar.gz
-Travis
__
On Thu, May 31, 2007 at 02:32:21AM +0200, Albert Strasheim wrote:
> Hello all
>
> - Original Message -
> From: "David M. Cooke" <[EMAIL PROTECTED]>
> To: "Discussion of Numerical Python"
> Sent: Thursday, May 31, 2007 2:08 AM
> Subject: Re: [Numpy-discussion] build problem on Windows (wa
Hello all
- Original Message -
From: "David M. Cooke" <[EMAIL PROTECTED]>
To: "Discussion of Numerical Python"
Sent: Thursday, May 31, 2007 2:08 AM
Subject: Re: [Numpy-discussion] build problem on Windows (was: build
problemon RHE3 machine)
> On Wed, May 30, 2007 at 03:06:04PM +0200,
On Wed, May 30, 2007 at 03:06:04PM +0200, Albert Strasheim wrote:
> Hello
>
> I took a quick look at the code, and it seems like new_fcompiler(...) is too
> soon to throw an error if a Fortran compiler cannot be detected.
>
> Instead, you might want to return some kind of NoneFCompiler that thro
Take that back, unsetting LDFLAGS did work!!!
Thanks
Brian
On 5/30/07, Brian Granger <[EMAIL PROTECTED]> wrote:
> > This looks like numpy.distutils has found ATLAS's FORTRAN BLAS library but
> > not
> > its libcblas library. Do you have a correct site.cfg file? From Chris
> > Hanley's
> > earl
> This looks like numpy.distutils has found ATLAS's FORTRAN BLAS library but not
> its libcblas library. Do you have a correct site.cfg file? From Chris Hanley's
> earlier post, it looks like the tarball on the SF site mistakenly includes a
> site.cfg. Delete it or correct it.
I will look at this.
Brian Granger wrote:
> Hi,
>
> I am building numpy on a 32 bit Linux system (Scientific Linux).
> Numpy used to build fine on this system, but as I have moved to the
> new 1.0.3 versions, I have run into problems building. Basically, I
> get lots of things like:
>
> undefined reference to `cblas
Hi,
I am building numpy on a 32 bit Linux system (Scientific Linux).
Numpy used to build fine on this system, but as I have moved to the
new 1.0.3 versions, I have run into problems building. Basically, I
get lots of things like:
undefined reference to `cblas_sdot'
and
undefined reference to `
Jesper Larsen wrote:
> Here is my solution for calculating the correlation coefficients for masked
> arrays. Comments are appreciated:
>
> def macorrcoef(data1, data2):
> """
> Calculates correlation coefficients taking masked out values
> into account.
>
> It is assumed (but not checke
On 30/05/07, Matthew Brett <[EMAIL PROTECTED]> wrote:
> I think the point is that you can have several different situations
> with byte ordering:
>
> 1) Your data and dtype endianess match, but you want the data swapped
> and the dtype to reflect this
>
> 2) Your data and dtype endianess don't mat
Hi,
Could someone please re-create the numpy-1.0.3.tar.gz file that is
currently being distributed from sourceforge? That tar file includes
the following:
/data/sparty1/dev/tmp/numpy-1.0.3
sparty> ls -al
total 44
drwxr-sr-x3 chanley science 4096 May 23 18:30 ./
drwxr-sr-x4 chanle
Matthew, this is a very clear description of all the issues, and I now
see why it can be useful to keep the two methods separate. I think an
update to the doc string for byteswap() with this description would be
useful. Or perhaps a keyword to byteswap() in which one could specify
the behavior re
Hi,
> > This doesn't make any sense. The numbers have changed but the dtype
> > is now incorrect. If you byteswap and correct the dtype the numbers
> > have still changed, but you now can actually use the object.
>
> By "numbers have still changed" I mean the underlying byte order is
> still dif
Suppose you get data, but it is byte-swapped. Calling this method would
yeild a correct array. If the type is changed too, it would not be useful :(
Matthieu
2007/5/30, Erin Sheldon <[EMAIL PROTECTED]>:
On 5/30/07, Francesc Altet <[EMAIL PROTECTED]> wrote:
> El dt 29 de 05 del 2007 a les 14:17
On 5/30/07, Erin Sheldon <[EMAIL PROTECTED]> wrote:
> On 5/30/07, Francesc Altet <[EMAIL PROTECTED]> wrote:
> > El dt 29 de 05 del 2007 a les 14:17 -0400, en/na Erin Sheldon va
> > escriure:
> > > Hi all -
> > >
> > > I have read some big-endian data and I want to byte swap it to little
> > > endia
On 5/30/07, Francesc Altet <[EMAIL PROTECTED]> wrote:
> El dt 29 de 05 del 2007 a les 14:17 -0400, en/na Erin Sheldon va
> escriure:
> > Hi all -
> >
> > I have read some big-endian data and I want to byte swap it to little
> > endian. If I use
> > a.byteswap(True)
> > the bytes clearly get swap
Hello
I took a quick look at the code, and it seems like new_fcompiler(...) is too
soon to throw an error if a Fortran compiler cannot be detected.
Instead, you might want to return some kind of NoneFCompiler that throws an
error if the build actually tries to compile Fortran code.
Cheers,
Al
On Friday 25 May 2007 19:18, Robert Kern wrote:
> Jesper Larsen wrote:
> > Hi numpy users,
> >
> > I have a masked array of dimension (nvariables, nobservations) that
> > contain missing values at arbitrary points. Is it safe to rely on
> > numpy.corrcoeff to calculate the correlation coefficients
El dt 29 de 05 del 2007 a les 14:17 -0400, en/na Erin Sheldon va
escriure:
> Hi all -
>
> I have read some big-endian data and I want to byte swap it to little
> endian. If I use
> a.byteswap(True)
> the bytes clearly get swapped, but the dtype is not updated to reflect
> the new data type. e.
22 matches
Mail list logo
