Hi,
On Fri, Oct 8, 2010 at 8:20 PM, Joshua Holbrook wrote:
>
> What mechanism are you using for gh-pages, if I may ask? I would be
> interested in this for future projects.
the default github implementation relies on a 'hidden' branch called
gh-pages that lives in the main repo. I think this is
On Fri, Oct 8, 2010 at 6:21 PM, Fernando Perez wrote:
> Hi Rob, Josh and Lluis,
>
> On Thu, Sep 30, 2010 at 9:41 AM, Rob Speer wrote:
>> The fact that I wasn't around for the sprint probably has a lot to do
>> with how much the code had diverged. But it's not too bad -- I merged
>> Fernando's bra
On Wed, Sep 8, 2010 at 5:00 AM, Lluís wrote:
> Well, the pull requests I posted to your repository are for fairly trivial
> fixes
> (but some still need documentation and regression test updates).
>
By the way Lluis, I replied to one of your requests (Keith merged the
other one, thanks!) here:
Hi Rob, Josh and Lluis,
On Thu, Sep 30, 2010 at 9:41 AM, Rob Speer wrote:
> The fact that I wasn't around for the sprint probably has a lot to do
> with how much the code had diverged. But it's not too bad -- I merged
> Fernando's branch into mine and only had to change a couple of things
> to ma
On 10/ 8/10 03:43 PM, Ralf Gommers wrote:
> On Fri, Oct 8, 2010 at 6:38 AM, Dr. David
> Kirkbywrote:
>
>> On 10/ 6/10 12:49 AM, Pauli Virtanen wrote:
>>> Hi,
>>>
>>> Should we set a date for a bugfix 1.5.1 release? There are some bugs that
>>> would be nice to sort out in the 1.5.x series:
>>>
>>>
On Fri, Oct 8, 2010 at 1:09 AM, Jonathan March wrote:
> On Wed, Oct 6, 2010 at 6:17 PM, wrote:
> > On Wed, Oct 6, 2010 at 7:08 PM, Jonathan March
> wrote:
> >> It appears that the numpy testing decorators for skipping and for
> >> known failure should behave similarly to each other, at least f
On Fri, Oct 8, 2010 at 1:55 PM, Pauli Virtanen wrote:
> Fri, 08 Oct 2010 13:28:01 -0400, josef.pktd wrote:
> [clip]
>> I think I clarified the doc string enough that user that read the
>> docstring don't get confused anymore.
>> http://docs.scipy.org/numpy/docs/numpy.random.mtrand.RandomState.pare
My program works with
NrHorPixels=10
NrVerPixels=10
NrCellsPerPixel=16
but not with
NrHorPixels=2048
NrVerPixels=2048
NrCellsPerPixel=100
The problem is in the variable Z definition and in the meshgrid, getting
MemoryError and ValueError: dimensions too large.
Is there any solution to avoid such
Fri, 08 Oct 2010 13:28:01 -0400, josef.pktd wrote:
[clip]
> I think I clarified the doc string enough that user that read the
> docstring don't get confused anymore.
> http://docs.scipy.org/numpy/docs/numpy.random.mtrand.RandomState.pareto/
>
> At least the first part is explicit about it, the not
On Fri, Oct 8, 2010 at 1:10 PM, Pauli Virtanen wrote:
> Fri, 08 Oct 2010 10:48:14 -0600, Charles R Harris wrote:
>> On Fri, Oct 8, 2010 at 10:37 AM, wrote:
> [clip]
>>> Ok I remember, Pareto is actually Lomax or Pareto second kind, and
>>> should be renamed. The proposal was to rename the current
I don't think that the problem is my libraries. I think the problem is that
numpy is not using them. If I build numpy with "BLAS=None LAPACK=None
ATLAS=None sudo python setup.py install" my benchmark program takes 8
seconds, the same as if I build it with atlas supposedly included.
I built lapack
Fri, 08 Oct 2010 10:48:14 -0600, Charles R Harris wrote:
> On Fri, Oct 8, 2010 at 10:37 AM, wrote:
[clip]
>> Ok I remember, Pareto is actually Lomax or Pareto second kind, and
>> should be renamed. The proposal was to rename the current pareto to
>> pareto2 and create a new pareto that corrects lo
On Fri, Oct 8, 2010 at 10:37 AM, wrote:
> On Fri, Oct 8, 2010 at 12:21 PM, Charles R Harris
> wrote:
> >
> >
> > On Fri, Oct 8, 2010 at 10:12 AM, wrote:
> >>
> >> On Fri, Oct 8, 2010 at 11:11 AM, Charles R Harris
> >> wrote:
> >> >
> >> >
> >> > On Thu, Oct 7, 2010 at 8:16 AM, Ralf Gommers
> >
On Fri, Oct 8, 2010 at 12:21 PM, Charles R Harris
wrote:
>
>
> On Fri, Oct 8, 2010 at 10:12 AM, wrote:
>>
>> On Fri, Oct 8, 2010 at 11:11 AM, Charles R Harris
>> wrote:
>> >
>> >
>> > On Thu, Oct 7, 2010 at 8:16 AM, Ralf Gommers
>> >
>> > wrote:
>> >>
>> >>
>> >> On Thu, Oct 7, 2010 at 10:00 PM
On 10/08/2010 10:58 AM, Ian Goodfellow wrote:
Here's the output on my atlas library:
file -L /usr/local/atlas/lib/libatlas.so
/usr/local/atlas/lib/libatlas.so: ELF 64-bit LSB shared object,
x86-64, version 1 (SYSV), dynamically linked, not stripped
It looks mostly the same as yours except it
On Fri, Oct 8, 2010 at 10:12 AM, wrote:
> On Fri, Oct 8, 2010 at 11:11 AM, Charles R Harris
> wrote:
> >
> >
> > On Thu, Oct 7, 2010 at 8:16 AM, Ralf Gommers <
> ralf.gomm...@googlemail.com>
> > wrote:
> >>
> >>
> >> On Thu, Oct 7, 2010 at 10:00 PM, Pierre GM
> wrote:
> >>>
> >>> Just asking,
>
On Fri, Oct 8, 2010 at 11:11 AM, Charles R Harris
wrote:
>
>
> On Thu, Oct 7, 2010 at 8:16 AM, Ralf Gommers
> wrote:
>>
>>
>> On Thu, Oct 7, 2010 at 10:00 PM, Pierre GM wrote:
>>>
>>> Just asking,
>>> Should I backport some bugs that were corrected in 2.0 for numpy.ma ? I
>>> don't have any part
Here's the output on my atlas library:
file -L /usr/local/atlas/lib/libatlas.so
/usr/local/atlas/lib/libatlas.so: ELF 64-bit LSB shared object, x86-64,
version 1 (SYSV), dynamically linked, not stripped
It looks mostly the same as yours except it says "not stripped" while yours
says "stripped." Do
On 10/08/2010 10:01 AM, Ian Goodfellow wrote:
I'm using 64-bit Ubuntu 10.04. I originally tried building without
site.cfg and got the same result. After that I removed the
installation and the numpy/build directory and tried again with site.cfg.
Here's the otuput of my show_config(). Does thi
On Thu, Oct 7, 2010 at 8:10 PM, Peter <
numpy-discuss...@maubp.freeserve.co.uk> wrote:
> Just FYI:
>
> The DEV_README.txt file needs a trivial update to talk about git not SVN
>
> Thanks, fixed in commit a8441313.
Ralf
___
NumPy-Discussion mailing list
On Thu, Oct 7, 2010 at 8:16 AM, Ralf Gommers wrote:
>
>
> On Thu, Oct 7, 2010 at 10:00 PM, Pierre GM wrote:
>
>> Just asking,
>> Should I backport some bugs that were corrected in 2.0 for numpy.ma ? I
>> don't have any particular in mind, but I'm sure there must be some...
>>
>> That would be hel
I'm using 64-bit Ubuntu 10.04. I originally tried building without site.cfg
and got the same result. After that I removed the installation and the
numpy/build directory and tried again with site.cfg.
Here's the otuput of my show_config(). Does this mean it's actually using
atlas? I ran 'make time'
On 10/08/2010 09:06 AM, Benjamin Root wrote:
On Fri, Oct 8, 2010 at 8:47 AM, Ian Goodfellow
mailto:goodfellow@gmail.com>> wrote:
Can anyone explain how to get numpy to recognize atlas? I have
atlas built and installed, and I put what I thought should be
sufficient, based on num
On Fri, Oct 8, 2010 at 6:38 AM, Dr. David Kirkby wrote:
> On 10/ 6/10 12:49 AM, Pauli Virtanen wrote:
> > Hi,
> >
> > Should we set a date for a bugfix 1.5.1 release? There are some bugs that
> > would be nice to sort out in the 1.5.x series:
> >
> > Any Python versions:
> >
> > - #1605 (Cython vs
On Fri, Oct 8, 2010 at 1:42 AM, Nils Becker wrote:
> Hi,
>
> what about the normed=True bug in numpy.histogram? It was discussed here
> a while ago, and fixed (although i did not find it on the tracker), but
> the message
>
>
>
> suggests it just missed 1.5.0? I don't have 1.5 installed, so I ca
Is there a log file I should post or do you just mean to capture everything
that setup.py prints to stdout?
On Fri, Oct 8, 2010 at 10:06 AM, Benjamin Root wrote:
> On Fri, Oct 8, 2010 at 8:47 AM, Ian Goodfellow
> wrote:
>
>> Can anyone explain how to get numpy to recognize atlas? I have atlas b
On Fri, Oct 8, 2010 at 8:47 AM, Ian Goodfellow wrote:
> Can anyone explain how to get numpy to recognize atlas? I have atlas built
> and installed, and I put what I thought should be sufficient, based on
> numpy's INSTALL.TXT, to make numpy use atlas in my site.cfg then ran python
> setup.py insta
Can anyone explain how to get numpy to recognize atlas? I have atlas built
and installed, and I put what I thought should be sufficient, based on
numpy's INSTALL.TXT, to make numpy use atlas in my site.cfg then ran python
setup.py install. The resulting build is incredibly slow. Multiplying a
1,000
Thanks for this, very informative! :-)
Chris
On 06/10/2010 17:35, Friedrich Romstedt wrote:
> 2010/10/5 Chris Withers:
>> Hi All,
>>
>> I can't find any docs on this behavior.
>>
>> So, I have a python function. To keep it simple, lets just do addition:
>>
>> def add(x,y):
>>print x,y
>>r
thanks,
it was actually obvious and I figured it out minutes later I sent the message.
Thanks anyway.
Quoting Robert Kern :
> On Thu, Oct 7, 2010 at 10:09, Ioan Ferencik wrote:
>> Hello Robert,
>>
>> I dare to bother you again with some questions.
>>
>> this time I have a numpy array with fi
Hi,
>> 'Talk is cheap, show me the code' .
>
> Yes, let's.
>
> First we want to initialize memory mapped arrays which will be used for
> the variables. This python script does that:
Ah - no - sorry - I was suggesting you write an implementation of the
object you want, in numpy. I am sure that wa
31 matches
Mail list logo
