On Thu, Mar 27, 2008 at 1:57 PM, Travis E. Oliphant
<[EMAIL PROTECTED]> wrote:
> If this works then it should be fine. If it doesn't, however, then it
> would not be too big a deal to just move the old implementation over.
> In fact, I rather think it ought to be done anyway.
My main concern i
All,
Would you mind trying the SVN (ver > 4946) and let me know what I'm still
missing ?
Thanks a lot in advance
P.
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-discussion
On Thu, March 27, 2008 7:20 pm, Tom Loredo wrote:
>
> Pearu-
>
>> smll_offset = smll_offset
>> exec `smll_offset.__doc__`
>
> Thanks for the quick and helpful response! I'll give it
> a try. I don't grasp why it works, though. I suppose I don't
> need to, but... I'm guessing the exec adds stuff
Hello,
Ok, I'll wait for Pierre's changes and see what it does for us. If it
still breaks here or there then i'll do as Travis suggested (while still
reporting to Pierre what went wrong).
Thank you all,
C.
Travis E. Oliphant wrote:
> Jarrod Millman wrote:
>
>> On Thu, Mar 27, 2008 at 1:31
Jarrod Millman wrote:
> On Thu, Mar 27, 2008 at 1:31 PM, Pierre GM <[EMAIL PROTECTED]> wrote:
>
>> On Thursday 27 March 2008 16:11:22 Travis E. Oliphant wrote:
>> > I guess what could be done is to take the old numpy.core.ma file and
>> > move it into oldnumeric.ma (along with the few re-namin
On Thu, Mar 27, 2008 at 1:31 PM, Pierre GM <[EMAIL PROTECTED]> wrote:
> On Thursday 27 March 2008 16:11:22 Travis E. Oliphant wrote:
> > I guess what could be done is to take the old numpy.core.ma file and
> > move it into oldnumeric.ma (along with the few re-namings that are there
> > now)? Co
On Thursday 27 March 2008 16:11:22 Travis E. Oliphant wrote:
> I guess what could be done is to take the old numpy.core.ma file and
> move it into oldnumeric.ma (along with the few re-namings that are there
> now)? Could you test that option out and see if it works for you?
I'm currently re-intr
Charles Doutriaux wrote:
> Eric, Pierre,
>
> I agree the new ma is probably much better and we should use it.
>
> all i was saying is that 1.0.4 was working great with the small
> compatibility layer.
> I even have a frozen version of 1.0.5 devel that works great. Then
> suddenly everything broke
lorenzo bolla wrote:
> The problem with fromfile() is that it doesn't know anything about ndarrays.
> If my file is a table of ncols and nrows, fromfile() will give me a
> 1darray with nrows*ncols elements, while loadtxt() will give me a
> 2dmatrix nrows x ncols. In other words, I loose the "shap
Thank you all.
The problem with fromfile() is that it doesn't know anything about ndarrays.
If my file is a table of ncols and nrows, fromfile() will give me a 1darray
with nrows*ncols elements, while loadtxt() will give me a 2dmatrix nrows x
ncols. In other words, I loose the "shape" of the table.
Alan G Isaac wrote:
> I believe Robert fixed this;
> update from the SVN repository.
lorenzo bolla wrote:
> Should I use numpy.fromfile, instead?
You can also do that. If fromfile() supports your data format, it will
be much faster.
-Chris
--
Christopher Barker, Ph.D.
Oceanographer
Emergen
Pearu-
> smll_offset = smll_offset
> exec `smll_offset.__doc__`
Thanks for the quick and helpful response! I'll give it
a try. I don't grasp why it works, though. I suppose I don't
need to, but... I'm guessing the exec adds stuff to the current
namespace that isn't there until a fortran objec
Hi Pierre,
No problem, let me know when you have something in. I can't be sure all
I mentioned is all that's missing. It's all I got so far.
But since I can't get our end going. I can't really give you a
comprehensive list of what's exactly missing. Hopefully this is all and
it will work fine a
Charles,
> all i was saying is that 1.0.4 was working great with the small
> compatibility layer.
> I even have a frozen version of 1.0.5 devel that works great. Then
> suddenly everything broke.
Could you be more specific ? Would you mind sending me bug reports so that I
can check what's going
Hi,
Tom Loredo wrote:
> Hi folks-
>
> Can anyone offer any tips on how I can get epydoc to produce
> API documentation for functions in an f2py-produced module?
> Currently they get listed in the generated docs as "Variables":
>
> Variables
> psigc =
> sigctp =
> smll_offset
On Thu, 27 Mar 2008, lorenzo bolla apparently wrote:
> I realized that numpy.loadtxt do not read the last
> character of an input file. This is annoying if the input
> file do not end with a newline.
I believe Robert fixed this;
update from the SVN repository.
hth,
Alan Isaac
__
Eric, Pierre,
I agree the new ma is probably much better and we should use it.
all i was saying is that 1.0.4 was working great with the small
compatibility layer.
I even have a frozen version of 1.0.5 devel that works great. Then
suddenly everything broke.
I was really happy was the layer of
Hi all!
I realized that numpy.loadtxt do not read the last character of an input
file. This is annoying if the input file do not end with a newline.
For example:
data.txt
---
1 2 3
In [33]: numpy.loadtxt('data.txt')
Out[33]: array([ 1., 2.])
While:
data.txt
---
1 2 3
In [33]: numpy
hi
i am trying to reconstruct face images from eigenfaces derrived from
original set of face images.
i represented orig images by an ndarray with each row for each image
and each column for pixel intensity.I sorted the eigenvectors such
that each row of sortedeigenvectors is an eigenvector(first ro
19 matches
Mail list logo
