On Fri, Mar 28, 2008 at 10:52 AM, Harry Mangalam <[EMAIL PROTECTED]> wrote:
> Here's the last few lines of the command that was kicked off by:
>
> f2py --opt="-O3" -c -m fd_rrt1d --fcompiler=g95 --link-lapack_opt *.f
>
> (incidentally, this is the same final error from both the ports
> versio
On Friday 28 March 2008 14:29:29 Charles Doutriaux wrote:
> Hi Pierre,
>
> Hum... something is still broken. But maybe you can help me figuring out
> if something dramtically changed
Something did indeed: numpy.ma.MaskedArray is now a subclass of ndarray, and
inheriting from MaskedArray should fo
Hi Pierre,
Hum... something is still broken. But maybe you can help me figuring out
if something dramtically changed
We're defining a new class object MaskedVariable which inherit from our
other class: AbstractVariable (in which we define a reorder function for
the obects) and from MaskedArray
Charles,
> I just tested it out, I'm still missing
> from numpy.oldnumeric.ma import common_fill_value , set_fill_value
> which breaks the code later
Turns out I had forgotten to put the functions in numpy.ma.core.__all__: they
had been already coded all along... That's fixed in SVN4950
On Friday 28 March 2008 14:04:28 Charles Doutriaux wrote:
> Hi Pierre,
>
> I just tested it out, I'm still missing
> from numpy.oldnumeric.ma import common_fill_value , set_fill_value
> which breaks the code later
OK, thx, I'll take care of that.
___
Num
On Fri, Mar 14, 2008 at 02:53:17PM -0500, Travis E. Oliphant wrote:
> Zbyszek Szmek wrote:
> > On Thu, Mar 13, 2008 at 05:44:54PM -0400, Alan G Isaac wrote:
> >> In principle you should be able to use ``fromiter``,
> >> I believe, but it does not work. BUG? (Crasher.)
> >>
> > import nump
Hi Pierre,
I just tested it out, I'm still missing
from numpy.oldnumeric.ma import common_fill_value , set_fill_value
which breaks the code later
C.
Pierre GM wrote:
> All,
> Would you mind trying the SVN (ver > 4946) and let me know what I'm still
> missing ?
> Thanks a lot in advance
> P.
> _
On Fri, Mar 28, 2008 at 3:20 AM, João Quinta da Fonseca <
[EMAIL PROTECTED]> wrote:
> I have a function that returns the dot product of two unit vectors.
> When I try to use arcos on the values returned I sometimes get the
> warning:
> "Warning: invalid value encountered in arccos", and the angle
Also using g95, which is fairly new I guess, but is a downstream
requirement for the application.
installed python 2.5 from darwin ports, installed most of rest of the
python stuff from ports as well, numpy 1.0.4 failed repeatedly
with 'too many options' error when processing cmdline options so
David Cournapeau wrote:
> João Quinta da Fonseca wrote:
>
>> I have a function that returns the dot product of two unit vectors.
>> When I try to use arcos on the values returned I sometimes get the
>> warning:
>> "Warning: invalid value encountered in arccos", and the angle
>> returned is
João Quinta da Fonseca wrote:
> I have a function that returns the dot product of two unit vectors.
> When I try to use arcos on the values returned I sometimes get the
> warning:
> "Warning: invalid value encountered in arccos", and the angle
> returned is nan. I found out that this happens
I have a function that returns the dot product of two unit vectors.
When I try to use arcos on the values returned I sometimes get the
warning:
"Warning: invalid value encountered in arccos", and the angle
returned is nan. I found out that this happens for essentially co-
linear vectors, for
12 matches
Mail list logo
