On Wed, 2008-11-12 at 19:24 -0500, David Warde-Farley wrote:
>
> Indeed, for the size of problem I *thought* I was running, 32 bit
> would be sufficient. In fact I had my data transposed and so was
> working with a much larger matrix which would put me past the 32-bit
> bound.
Still, ideal
On 12-Nov-08, at 6:05 PM, Michael Abshoff wrote:
>> I'm running the python.org 2.5.2 build of Python, and the latest SVN
>> build of numpy (though the same thing happened with 1.1.0).
>
> IIRC that is a universal build for 32 bit PPC and Intel, so
> depending on
> the problem size 32 bits might
My system..
Ubuntu v8.0.4; Gnu gcc v4.0.3;g95 v0.92
Python v2.5.2;Numpy v1.2.1;f2py v2.5972
Hope someone can see what's wrong here?
thanks
Dave Lang
..Here is the F90 code...
! PROGRAM TO DEMONSTRATE PYTHON-->F90 AND F90-->PYTHON INTERFACE
S
Hello,
I'm not sure if this is the right list for this question, but attempts
to subscribe myself to f2py-users fail, as I never get an email back
asking
me to confirm my subscription request. Is that list no longer active?
I'm trying to compile a medium-short Fortran90 code using f2py, and
ge
On Wed, Nov 12, 2008 at 12:58 PM, David Huard <[EMAIL PROTECTED]> wrote:
> Revision 6020 proceeds with the planned changes to histogram semantics for
> the 1.3 release.
Thanks,
--
Jarrod Millman
Computational Infrastructure for Research Labs
10 Giannini Hall, UC Berkeley
phone: 510.643.4014
http
David Warde-Farley wrote:
> Hello folks,
Hi David,
> I'm doing some rather big matrix products on a G5, and ran into this.
> Strangely on the same OS version on my Intel laptop, this isn't an
> issue. Available memory isn't the problem either, I don't think, this
> machine is pretty beefy.
On Wed, Nov 12, 2008 at 2:09 PM, David Huard <[EMAIL PROTECTED]> wrote:
>
> Mike, before patching, please take a look at the tickets related to
> histogram on the numpy trac. Previously, histogram returned only used the
> left bin edges and it caused a lot of problems with outliers and
> normalizat
On Wed, Nov 12, 2008 at 1:27 PM, Mike Ressler <[EMAIL PROTECTED]>wrote:
> On Wed, Nov 12, 2008 at 4:30 AM, Scott Sinclair <[EMAIL PROTECTED]>
> wrote:
> >> "Mike Ressler" <[EMAIL PROTECTED]> 11/12/08 1:19 AM
> >> I did an update to a Fedora 9 workstation yesterday that included
> >> updating numpy
Hello folks,
I'm doing some rather big matrix products on a G5, and ran into this.
Strangely on the same OS version on my Intel laptop, this isn't an
issue. Available memory isn't the problem either, I don't think, this
machine is pretty beefy.
I'm running the python.org 2.5.2 build of Pyth
NumPy users,
Revision 6020 proceeds with the planned changes to histogram semantics for
the 1.3 release.
This modification brings no change in functionality, only changes in the
warnings being raised:
No warning is printed for the default behaviour (new=None).
new=False now raises a Depreca
Nope this one wouldn't have worked for me, it's basically axis=-1
but there might be additional dimensions after index
C.
On Nov 12, 2008, at 10:43 AM, Roberto De Almeida wrote:
On Wed, Nov 12, 2008 at 4:36 PM, Gabriel Gellner
<[EMAIL PROTECTED]> wrote:
On Wed, Nov 12, 2008 at 12:34:51PM -060
Charles سمير Doutriaux wrote:
> Hello,
>
> I'm wondering if there's aquick way to do the following:
>
> s[:,5]=value
>
> in a "general" function
> def setval(array,index,value,axis=0):
> ## code here
Assuming that axis specifies where the index goes, that would be:
def setval(array, inde
On Wed, Nov 12, 2008 at 4:36 PM, Gabriel Gellner <[EMAIL PROTECTED]>wrote:
> On Wed, Nov 12, 2008 at 12:34:51PM -0600, Ryan May wrote:
> > Charles سمير Doutriaux wrote:
> > > Hello,
> > >
> > > I'm wondering if there's aquick way to do the following:
> > >
> > > s[:,5]=value
> > >
> > > in a "gene
Thx!
On Nov 12, 2008, at 10:36 AM, Gabriel Gellner wrote:
> On Wed, Nov 12, 2008 at 12:34:51PM -0600, Ryan May wrote:
>> Charles سمير Doutriaux wrote:
>>> Hello,
>>>
>>> I'm wondering if there's aquick way to do the following:
>>>
>>> s[:,5]=value
>>>
>>> in a "general" function
>>> def setval(arr
Something I use a lot is a little generator that iterates over a ndarray by a
given axis. I was wondering if this is already built-in to numpy (and not
using the apply_along_axis which I find ugly) and if not would there be
interest in adding it?
the function is just:
def by_axis(nobj, axis=0):
On Wed, Nov 12, 2008 at 12:34:51PM -0600, Ryan May wrote:
> Charles سمير Doutriaux wrote:
> > Hello,
> >
> > I'm wondering if there's aquick way to do the following:
> >
> > s[:,5]=value
> >
> > in a "general" function
> > def setval(array,index,value,axis=0):
> > ## code here
>
> Assuming
On Wed, Nov 12, 2008 at 09:43:34AM -0800, Charles سمير Doutriaux wrote:
> Hello,
>
> I'm wondering if there's aquick way to do the following:
>
> s[:,5]=value
>
> in a "general" function
> def setval(array,index,value,axis=0):
> ## code here
>
> The issue is to put enough ":" before the i
On Wed, Nov 12, 2008 at 4:30 AM, Scott Sinclair <[EMAIL PROTECTED]> wrote:
>> "Mike Ressler" <[EMAIL PROTECTED]> 11/12/08 1:19 AM
>> I did an update to a Fedora 9 workstation yesterday that included
>> updating numpy to 1.2.0 and matplotlib 0.98.3 (python version is
>
> They reported that the Fedor
On Tuesday 11 November 2008 04:19:26 am Rolf Wester wrote:
> I'm not sure whether TNT is still actively maintained, the TNT home page
> was last modified in 2004, so you are probably right. But the TNT Arrays
> are just what I need and I know of no alternative.
Use boost.python + boost.ublas + num
Hello,
I'm wondering if there's aquick way to do the following:
s[:,5]=value
in a "general" function
def setval(array,index,value,axis=0):
## code here
The issue is to put enough ":" before the index value inside the
square bracket of the assignement.
Thanks,
C.
___
Wed, 12 Nov 2008 10:57:59 -0600, Ryan May wrote:
[clip: numpy doc editor]
> Great, can someone get me edit access?
Done.
--
Pauli Virtanen
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-di
Pauli Virtanen wrote:
> Hi,
>
> Wed, 12 Nov 2008 10:16:35 -0600, Ryan May wrote:
>> Here's a quick diff to fix some typos in the docstrings for matlib.zeros
>> and matlib.ones. They're causing 2 (of many) failures in the doctests
>> for me on SVN HEAD.
>
> There are probably bound to be more of
Hi,
Wed, 12 Nov 2008 10:16:35 -0600, Ryan May wrote:
> Here's a quick diff to fix some typos in the docstrings for matlib.zeros
> and matlib.ones. They're causing 2 (of many) failures in the doctests
> for me on SVN HEAD.
There are probably bound to be more of these. It's possible to fix them
u
Hi,
Here's a quick diff to fix some typos in the docstrings for matlib.zeros
and matlib.ones. They're causing 2 (of many) failures in the doctests
for me on SVN HEAD.
Filed in trac as #953
(http://www.scipy.org/scipy/numpy/ticket/953)
(Unless someone wants to give me SVN rights for fixing/addin
> "Mike Ressler" <[EMAIL PROTECTED]> 11/12/08 1:19 AM
> I did an update to a Fedora 9 workstation yesterday that included
> updating numpy to 1.2.0 and matplotlib 0.98.3 (python version is
> 2.5.1). This seems to have played havoc with some of the histogram
> plotting we do. I was aware of the hist
Hello,
Here is a exemple of call-back use from Fortran to Python using f2py :
http://cens.ioc.ee/projects/f2py2e/usersguide/f2py_usersguide.pdf
But maybe you have already read it?
http://cens.ioc.ee/projects/f2py2e/usersguide/f2py_usersguide.pdf
2008/11/12 Dave Lang <[EMAIL PROTECTED]>
> He
26 matches
Mail list logo
