On Sat, Aug 14, 2010 at 6:11 AM, Ralf Gommers
wrote:
> Installing into a local virtualenv (with either of the methods that work)
> looks good. Into /Library/Frameworks/..., nose refuses to run any tests, due
> to the files being executable. But I think that's normal. Changing
> permissions to 644
David,
> You should instead specificaly link the GOTO library to
> numpy, by customizing the site.cfg,
That was one of the many things I tried came to the list.
Peter Ashford
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.sci
On 08/17/2010 01:58 PM, ashf...@whisperpc.com wrote:
> I'm having problems getting the GotoBLAS library (Nehalem optimized BLAS -
> "http://www.tacc.utexas.edu/tacc-projects/gotoblas2/";) working properly under
> the Python NumPy package ("http://numpy.scipy.org/";) on a quad-core Nehalem
> under F
I'm having problems getting the GotoBLAS library (Nehalem optimized BLAS -
"http://www.tacc.utexas.edu/tacc-projects/gotoblas2/";) working properly under
the Python NumPy package ("http://numpy.scipy.org/";) on a quad-core Nehalem
under FC10.
The command used to build the library is:
make BINA
On Tue, Aug 17, 2010 at 12:13 AM, Alex Ter-Sarkissov wrote:
> hi, this is probably a very silly question, but I can't get my hear
> around it unfortunately(
>
> I have an array (say, mat=rand(3,5)) from which I 'pull out' a row
> (say, s1=mat[1,]). The problem is, the shape of this row s1 is not
>
hi, this is probably a very silly question, but I can't get my hear
around it unfortunately(
I have an array (say, mat=rand(3,5)) from which I 'pull out' a row
(say, s1=mat[1,]). The problem is, the shape of this row s1 is not
[1,5], as I would expect, but rather [5,], which means that I can't,
fo
Hi All,
I just added support for Legendre polynomials to numpy and I think the
numpy.polynomial name space is getting a bit crowded. Since most of the
current functions in that namespace are just used to implement the
Polynomial, Chebyshev, and Legendre classes I'm thinking of only importing
those
> I don't really see how to make that works (that is running gfortran
> code in a spawned process), but if you know how to, please go ahead.
I didn't debug this code examples so there might be typos, but this is
just to illustrate the general idea:
Say we have a Fortran function with this inte
On Tue, Aug 17, 2010 at 2:24 AM, Sturla Molden wrote:
>
> Thank for the information, David.
>
>> I think the right solution is to build our own libgfortran, but
>> against the MSVC C runtime instead of the mingw runtime. THis is not
>> as crazy as it sounds because scipy does not rely so much on t
> After using time.clock, running f2py with the REPORT_ON_ARRAY_COPY enabled
> and
> passing arrays as np.asfortranarray(array) to the fortran routines I still
> get a
> slow performance on f2py. No copied arrays are reported.
That is not any better as np.asfortranarray will make a copy instead.
Sturla Molden molden.no> writes:
>
>
> > It looks like the gain in performance is
> > rather low compared to tests i have seen elsewhere.
> >
> > Am I missing something here..?
> >
> > Cheers...Vasilis
>
> Turn HTML off please.
>
> Use time.clock(
On 08/16/2010 07:36 AM, Sturla Molden wrote:
>
>> Sturla,
>>
>> Have you tried the Equation Solution versions of the gcc tools?
>> http://www.equation.com/servlet/equation.cmd?fa=fortran
>>
>> Eric
>
>
> It does not matter which mingw-w64 build we use. The import libraries will
> still be missing,
To explain:
A has shape (2,1), meaning it's a 2-D array with 2 rows and 1 column.
The transpose of A has shape (1,2): it's a 2-D array with 1 row and 2
columns. That's not the same as what you want, which is an array with
shape (2,): a 1-D array with 2 entries.
When you take A[:,0], you're pullin
You can also do:
y = x[:,0]
On Mon, Aug 16, 2010 at 11:28 AM, Skipper Seabold wrote:
> On Mon, Aug 16, 2010 at 2:25 PM, gerardob wrote:
> >
> > I have a numpy array A , such that when i print A it appears:
> >
> > [[ 10.]
> > [ 20.]]
> >
> > I would like to have a one dimensional array B (obta
On Mon, Aug 16, 2010 at 2:25 PM, gerardob wrote:
>
> I have a numpy array A , such that when i print A it appears:
>
> [[ 10.]
> [ 20.]]
>
> I would like to have a one dimensional array B (obtained from A) such that
> B[0] = 10 and B[1]=20. It could be seen as the transpose of A.
>
> How can i ob
I have a numpy array A , such that when i print A it appears:
[[ 10.]
[ 20.]]
I would like to have a one dimensional array B (obtained from A) such that
B[0] = 10 and B[1]=20. It could be seen as the transpose of A.
How can i obtain B = [10,20] from A? I tried transpose(1,0) but it doesn't
se
> Sturla,
>
> Have you tried the Equation Solution versions of the gcc tools?
> http://www.equation.com/servlet/equation.cmd?fa=fortran
>
> Eric
It does not matter which mingw-w64 build we use. The import libraries will
still be missing, and the issies with libgfortran are still there. Also,
AVG
Thank for the information, David.
> I think the right solution is to build our own libgfortran, but
> against the MSVC C runtime instead of the mingw runtime. THis is not
> as crazy as it sounds because scipy does not rely so much on the
> fortran runtime. Just faking the library (by putting func
On Tue, Aug 17, 2010 at 1:53 AM, Eric Firing wrote:
> On 08/15/2010 11:14 PM, Sturla Molden wrote:
>> Two criticial import libraries for mingw-w64 are missing (libpython26.a
>> and msvcr90.a). We cannot build C extensions for Python with mingw-w64. If
>> you can build with disutils, your are not u
On 08/15/2010 11:14 PM, Sturla Molden wrote:
> Two criticial import libraries for mingw-w64 are missing (libpython26.a
> and msvcr90.a). We cannot build C extensions for Python with mingw-w64. If
> you can build with disutils, your are not using mingw-w64 but another C
> compiler.
Sturla,
Have yo
On Mon, Aug 16, 2010 at 11:36 AM, Ralf Gommers
wrote:
>
>
> On Mon, Aug 16, 2010 at 4:50 PM, Sandro Tosi wrote:
>>
>> Hi all,
>> sorry for the delay
>>
>> On Sun, Aug 1, 2010 at 18:38, Ralf Gommers
>> wrote:
>> > I am pleased to announce the availability of the first beta of NumPy
>> > 1.5.0.
>>
On Mon, Aug 16, 2010 at 4:50 PM, Sandro Tosi wrote:
> Hi all,
> sorry for the delay
>
> On Sun, Aug 1, 2010 at 18:38, Ralf Gommers
> wrote:
> > I am pleased to announce the availability of the first beta of NumPy
> 1.5.0.
> > This will be the first NumPy release to include support for Python 3,
2010/8/16 Guillaume Chérel :
> Hello,
>
> I'd like to know if there is an easy way to save a list of 1D arrays to a
> csv file, with the first line of the file being the column names.
>
> I found the following, but I can't get to save the column names:
>
> data = rec.array([X1,X2,X3,X4], names=[n1,
2010/8/16 Guillaume Chérel :
> Hello,
> I'd like to know if there is an easy way to save a list of 1D arrays to a
> csv file, with the first line of the file being the column names.
>
> I found the following, but I can't get to save the column names:
>
> data = rec.array([X1,X2,X3,X4], names=[n1,n
> It looks like the gain in performance is
> rather low compared to tests i have seen elsewhere.
>
> Am I missing something here..?
>
> Cheers...Vasilis
Turn HTML off please.
Use time.clock(), not time.time().
Try some tasks that actually takes a wh
Hello,
I'd like to know if there is an easy way to save a list of 1D arrays to a
csv file, with the first line of the file being the column names.
I found the following, but I can't get to save the column names:
data = rec.array([X1,X2,X3,X4], names=[n1,n2,n3,n4])
savetxt("filename", data, delim
2010/8/16 Sturla Molden
> Two criticial import libraries for mingw-w64 are missing (libpython26.a
> and msvcr90.a). We cannot build C extensions for Python with mingw-w64. If
> you can build with disutils, your are not using mingw-w64 but another C
> compiler.
>
You are correct. The 32 bit setup
Perhaps related tickets, but no perfect match (as far as I can judge):
- http://projects.scipy.org/numpy/ticket/1399 "distutils fails to build ppc64
support on Mac OS X when requested"
This revision is older than the one I used, ergo should already be applied.
- http://projects.scipy.org
Hello!
At first, I'd like to say thanks to the numpy/scipy team and all contributors.
Great software!
On Snow Leopard, aka Mac OS X 10.6.4 (server) I managed to build numpy
2.0.0.dev8636 (and scipy 0.9.0.dev6646) for arch i386 in combined 32/64bit
against MacPorts python27 (No ppc here!).
All
On Mon, Aug 16, 2010 at 10:12 AM, Vasileios Gkinis wrote:
> Hi all,
>
> This is a question on f2py.
> I am using a Crank Nicholson scheme to model a diffusion process and in the
> quest of some extra speed I started playing with f2py.
> However I do not seem to be able to get any significant boos
Two criticial import libraries for mingw-w64 are missing (libpython26.a
and msvcr90.a). We cannot build C extensions for Python with mingw-w64. If
you can build with disutils, your are not using mingw-w64 but another C
compiler.
There are rumors of incompatibility issues between libgfortran and th
Hi all,
This is a question on f2py.
I am using a Crank Nicholson scheme to model a diffusion process
and in the quest of some extra speed I started playing with
f2py.
However I do not seem to be able to get any significant boost in
Hi all,
sorry for the delay
On Sun, Aug 1, 2010 at 18:38, Ralf Gommers wrote:
> I am pleased to announce the availability of the first beta of NumPy 1.5.0.
> This will be the first NumPy release to include support for Python 3, as
> well as for Python 2.7. Please try this beta and report any prob
Hi all,
Are there any success stories in building f2py extensions on AMD64 with
latest versions? Building the same extension on 32 bit works like a charm.
I am having trouble finding documentation or examples, is it supposed to be
working?
Compiling (with distutils) works like a charm, but that
34 matches
Mail list logo