Hi,
since there was so much discussion whether bzr or hg, Mercurial has
now free hosting too:
http://freehg.org/
also Mercurial 1.0 was finally released yesterday.
Bzr has Launchpad, that's one of the (main) reasons ipython is
investigating it, so I am still learning how to use bzr, but it's no
I am going to apply for a Google Summer of Code project about "Developing
Cython towards better NumPy integration" (Cython: http://cython.org).
Anyone interested in how this is done can have a look at the links below,
any feedback is welcome.
Unfortunately I don't have much time to spare before th
Andreas Klöckner wrote:
>> [snip]
>> a += 3 is really equivalent to a = a+3.
>
> Except when it isn't.
right -- it isn't the same. In fact, if I were king (or BDFL), you
wouldn't be able to use += with immutable types, but I'm not ;-)
One of the reasons the augmented assignment operators where
Hi as a follwup the latest error seems to be caused by:
>>> a=numpy.array(1.)
>>> a.shape
()
>>> numpy.asfortranarray(a).shape
(1,)
So in cases where my input is basically a float (but sometimes it has 3
or more dims) to gets confused
C.
Charles Doutriaux wrote:
> Hello,
>
> I have an f2py m
Hello,
I have an f2py module that used to work great, now it breaks,
first of all the setup.py extension used to have:
# f2py_options = ["--fcompiler=gfortran",],
I now need to comment this out, and hope it picks up the right compiler...
at the beg of the script I
Lou Pecora wrote:
> Travis, Does that mean it's not worth starting a
> ticket? Sounds like nothing can be done, *except* to
> put this in the documentation and the FAQ. It has
> bitten several people.
>
You can start a ticket with a milestone of 1.1, but I don't think it is
worth it, given
Travis, Does that mean it's not worth starting a
ticket? Sounds like nothing can be done, *except* to
put this in the documentation and the FAQ. It has
bitten several people.
--- "Travis E. Oliphant" <[EMAIL PROTECTED]>
wrote:
> Stéfan van der Walt wrote:
>> Lou Pecora wrote:
> >> Thanks, Mat
least significant eigenimage
> is "deteriorated" is logical. Eigenimages are trying to represent in a
> linear way something that is not. The smallest variations are then
> represented by an artifact, and this is what you get.
>
>
thanks Matthieu ..if that is the logical behaviour then i believe my
On Tuesday 25 March 2008 10:33:58 Chris Withers wrote:
> Pierre GM wrote:
> > Well, yeah, my bad, that depends on whether you use masked_invalid or
> > fix_invalid or just build a basic masked array.
>
> Yeah, well, if there were any docs I'd have a *clue* what you were
> talking about ;-)
My bad,
>
> #now this creates 2 images.they are given in this page(http://
> roytechdumps.blogspot.com/).The leasteigenface ie 'eigenface16.jpg'
> is quite 'deteriorated' in appearance compared to the other.Is this
> because of the
>
> corresponding eigenvector containing least variations? can someone
> e
hi
As discussed in the thread
http://groups.google.com/group/Numpy-discussion/browse_thread/thread/b9774ac757c3c
98e/a66aa2565d4e6a24
i tried to create an application to create eigenfaces from a set of
jpeg images.I followed these steps after obtaining an ndarray of 17
images (ie 17 rows where ea
Pierre GM wrote:
>
> Well, yeah, my bad, that depends on whether you use masked_invalid or
> fix_invalid or just build a basic masked array.
Yeah, well, if there were any docs I'd have a *clue* what you were
talking about ;-)
y=ma.fix_invalid(x)
I've never done this ;-)
> Having
On Dienstag 25 März 2008, Nadav Horesh wrote:
> scalars are immutable objects in python. Thus the += (and alike) are "fake":
Again, thanks for the explanation. IMHO, whether or not they are fake is an
implementation detail. You shouldn't have to know Python's guts to be able to
use Numpy success
On Tue, 2008-03-25 at 10:47 +0100, Sebastian Haase wrote:
> Hi Connelly !
>
Hi Sebastian,
>
> If someone wants to not "rely" on scipy , then the precentile would
> still be missing .
The problem is that you can apply this reasoning to any function. So
there should be a limit.
> (And I a
Hi Connelly !
I saw your bug-report (#626) was closed (as invalid).
[[ I think "invalid" is wrong, since numpy != scipy ]]
(http://scipy.org/scipy/numpy/ticket/626)
Two functions I am continually re-implementing in my own number-crunching
projects are percentile() and clamp(). Here percentil
Hi all,
Is this a known issue with latest svn
numpy.test(verbosity=2) segfaults with
check_float_repr
(numpy.core.tests.test_scalarmath.TestRepr)
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 182894186368 (LWP 6930)]
0x003390e3d5e5 in __mpn_mul_1 () from
/lib64/
16 matches
Mail list logo
