I switched to numpy-1.8.2. . Now getting following error. I am using
LAPACK that comes with atlast installation. Can this be a problem?
Traceback (most recent call last):
File "", line 1, in
File
"/home/svu/a0095654/.local/lib/python2.7/site-packages/numpy/__init__.py",
line 170, in
from
Julian Taylor wrote:
> thanks for the explanation.
> Modules are only available with f90 right? f77 files do not have these
> generated interdependencies?
> being able to handle f77 would already be quite good, as it should at
> least cover current scipy.
> One can look at a smarter scheme for f9
this applies to the mingw-w64 builds as well
see also:
https://gcc.gnu.org/ml/fortran/2014-10/msg00038.html
From: "Joseph S. Myers"
To: FX
Cc: GCC Patches ,
fortran List
Date: Mon, 6 Oct 2014 20:38:14
Subject: Re: [patch] Add -static-libquadmath option
Since -static-libquad
On 10.10.2014 23:07, Matthew Brett wrote:
> Hi,
>
> On Tue, Oct 7, 2014 at 5:13 PM, Julian Taylor
> wrote:
>> On 06.10.2014 18:54, Andrew Collette wrote:
>>> Hi all,
>>>
>>> I am working with the HDF Group on a new open-source viewer program
>>> for HDF5 files, powered by NumPy, h5py, and wxPytho
Hi,
On Tue, Oct 7, 2014 at 5:13 PM, Julian Taylor
wrote:
> On 06.10.2014 18:54, Andrew Collette wrote:
>> Hi all,
>>
>> I am working with the HDF Group on a new open-source viewer program
>> for HDF5 files, powered by NumPy, h5py, and wxPython. On Windows,
>> since people don't typically have Py
On 10.10.2014 11:34, per.brodtk...@ffi.no wrote:
> I have worked on a generalized piecewise function (genpiecewise) that
> are simpler and more general than the current numpy.piecewise
> implementation. The new generalized piecewise function allows functions
> of the type f(x0, x1,.. , xn) i.e. to
This is not NumPy specific but may still interest list members:
http://randomascii.wordpress.com/2014/10/09/intel-underestimates-error-bounds-by-1-3-quintillion/
Alan Isaac
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.or
On 10.10.2014 21:09, Sturla Molden wrote:
> Julian Taylor wrote:
>
>> There is still one problem in regards to parallelizing fortran 90. The
>> ccompiler.py contains following comment:
>> # build any sources in same order as they were originally specified
>> # especially important for f
On Fr, 2014-10-10 at 14:30 -0400, Benjamin Root wrote:
> Oy! I got to be having a brain fart today. np.all on the list of
> boolean arrays applied on the first(?) axis is much clearer than any
> ufunc or reduce call. And to answer the next question... use np.any
> for logical_or()...
>
Of course
Sturla Molden wrote:
> So the Fortran 90 files creates a directed asyclic graph. To compute in
> parallel
Eh, *compile* in parallel.
> Sturla
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-d
Sturla Molden wrote:
> When a Fortran module is compiled, the compiler emits an object file (.o)
> and a module file (.mod). The module file plays the role of a header file
> in C. So when another Fortran file imports the module with a use statement,
> the compiler looks for the module file. Beca
Julian Taylor wrote:
> There is still one problem in regards to parallelizing fortran 90. The
> ccompiler.py contains following comment:
> # build any sources in same order as they were originally specified
> # especially important for fortran .f90 files using modules
>
> This indicate
Oy! I got to be having a brain fart today. np.all on the list of boolean
arrays applied on the first(?) axis is much clearer than any ufunc or
reduce call. And to answer the next question... use np.any for
logical_or()...
Thanks!
Ben Root
On Fri, Oct 10, 2014 at 2:27 PM, Stephan Hoyer wrote:
>
On Fri, Oct 10, 2014 at 11:23 AM, Benjamin Root wrote:
> I have a need to "and" together an arbitrary number of boolean arrays.
> np.logical_and() expects only two positional arguments. There has got to be
> some sort of easy way to just and these together using the ufunc mechanism,
> right?
>
D
I have a need to "and" together an arbitrary number of boolean arrays.
np.logical_and() expects only two positional arguments. There has got to be
some sort of easy way to just and these together using the ufunc mechanism,
right?
Cheers!
Ben Root
___
Num
hi,
To speed up compilation of extensions I have made a PR to compile
extension files in parallel:
https://github.com/numpy/numpy/pull/5161
It adds the --jobs/-j flags to the build command of setup.py which
defines the number of parallel compile processes.
E.g.
python setup.py build --jobs 4 insta
On 10.10.2014 19:26, Lahiru Samarakoon wrote:
> Red Hat Enterprise Linux release 5.8
> gcc (GCC) 4.1.2
>
> I am also trying to install numpy 1.9.
that is the broken platform, please try the master branch or the
maintenance/1.9.x branch, those should work now.
Are there volunteers to report this
Red Hat Enterprise Linux release 5.8
gcc (GCC) 4.1.2
I am also trying to install numpy 1.9.
On Sat, Oct 11, 2014 at 12:59 AM, Julian Taylor <
jtaylor.deb...@googlemail.com> wrote:
> On 10.10.2014 18:51, Lahiru Samarakoon wrote:
> > Dear all,
> >
> > I am trying to install numpy without root acce
On 10.10.2014 18:51, Lahiru Samarakoon wrote:
> Dear all,
>
> I am trying to install numpy without root access. So I am building from
> the source. I have installed atlas which also has lapack with it. I
> changed the site.cfg file as given below
>
> [DEFAULT]
> library_dirs = /home/svu/a009565
Dear all,
I am trying to install numpy without root access. So I am building from the
source. I have installed atlas which also has lapack with it. I changed
the site.cfg file as given below
[DEFAULT]
library_dirs = /home/svu/a0095654/ATLAS/build/lib
include_dirs = /home/svu/a0095654/ATLAS/buil
I have worked on a generalized piecewise function (genpiecewise) that are
simpler and more general than the current numpy.piecewise implementation. The
new generalized piecewise function allows functions of the type f(x0, x1,.. ,
xn) i.e. to have arbitrary number of input arguments that are eval
21 matches
Mail list logo
