On Thu, May 20, 2010 at 10:17 AM, David Goldsmith
wrote:
> On Wed, May 19, 2010 at 3:50 PM, William Carithers wrote:
>
>> Hi David and Josef,
>>
>> OK, I updated to numpy-1.4.1 and scipy-0.7.2 and this problem went away.
>> Thanks for your help.
>>
>> BTW, trying to upgrade using the .dmg files fr
On Wed, May 19, 2010 at 3:50 PM, William Carithers wrote:
> Hi David and Josef,
>
> OK, I updated to numpy-1.4.1 and scipy-0.7.2 and this problem went away.
> Thanks for your help.
>
> BTW, trying to upgrade using the .dmg files from Sourceforge didn't work.
> It
> kept saying that it needed Syste
Hi David and Josef,
OK, I updated to numpy-1.4.1 and scipy-0.7.2 and this problem went away.
Thanks for your help.
BTW, trying to upgrade using the .dmg files from Sourceforge didn't work. It
kept saying that it needed System Python 2.6 even though Python 2.6 is
already installed. In fact, it was
On Wed, May 19, 2010 at 4:24 PM, William Carithers wrote:
> Hi Josef,
>
> I did the same test, namely opening a new window and plugging in the
> printout values by hand and polyfit worked just fine. Here's the terminal
> output:
>
import numpy as n
y = n.array([ 864., 865., 866., 867.
The polynomial module definitely postdates 1.2.1; I echo Josef's rec. that
you update if possible.
On Wed, May 19, 2010 at 1:24 PM, William Carithers wrote:
> Hi Josef,
> > I didn't know numpy will use the scipy version of linalg for this.
>
Right, that's what told me he must be using an old (an
Hi Josef,
I did the same test, namely opening a new window and plugging in the
printout values by hand and polyfit worked just fine. Here's the terminal
output:
>>> import numpy as n
>>> y = n.array([ 864., 865., 866., 867., 868.])
>>> a = n.array([ 5.24860191, 6.0217514 , 6.11434555, 6.09
On Wed, May 19, 2010 at 3:51 PM, William Carithers wrote:
> Thanks David and Josef. Replies interspersed below.
>
>
> On 5/19/10 12:24 PM, "josef.p...@gmail.com" wrote:
>
>> On Wed, May 19, 2010 at 3:18 PM, David Goldsmith
>> wrote:
>>> Charles H.: is this happening because he's calling the old
Thanks David and Josef. Replies interspersed below.
On 5/19/10 12:24 PM, "josef.p...@gmail.com" wrote:
> On Wed, May 19, 2010 at 3:18 PM, David Goldsmith
> wrote:
>> Charles H.: is this happening because he's calling the old version of
>> polyfit?
>>
>> William: try using numpy.polynomial.pol
On Wed, May 19, 2010 at 3:18 PM, David Goldsmith
wrote:
> Charles H.: is this happening because he's calling the old version of
> polyfit?
>
> William: try using numpy.polynomial.polyfit instead, see if that works.
>
> DG
>
> On Wed, May 19, 2010 at 11:03 AM, William Carithers
> wrote:
>>
>> I'm
Charles H.: is this happening because he's calling the old version of
polyfit?
William: try using numpy.polynomial.polyfit instead, see if that works.
DG
On Wed, May 19, 2010 at 11:03 AM, William Carithers wrote:
> I'm trying to do a simple 2nd degree polynomial fit to two arrays of 5
> entries
I'm trying to do a simple 2nd degree polynomial fit to two arrays of 5
entries. I get a runtime error:
RuntimeError: more argument specifiers than keyword list entries (remaining
format:'|:calc_lwork.gelss') in the lstsq module inside numpy.polyfit.
Here's the code snippet:
def findPeak(self, yde
11 matches
Mail list logo
