True
> False
>
> so that in the first case, SimpleArray.__eq__ is not called. Is this a
> bug, and if so, can anyone think of a workaround? If this is expected
> behavior, how do I ensure SimpleArray.__eq__ gets called in both
> cases?
>
This should be working in all
some smaller differences. Given a good idea for the api, I think a new
function maybe better. Since I am not on a computer at the moment I did
not check the old discussions though.
- Sebastian
___
> NumPy-D
both operators are
probably used out there. So if you have any serious doubt about starting
this deprecation please note it here.
The Pull request to implement such a deprecation is:
https://github.com/numpy/numpy/pull/4105
Regards,
Sebastian
___
NumPy
ith similar functionality in Numpy. It's
already hard to overlook the existing functions and all their possible
applications and variants. The axis=None proposal for shuffling all
items is very intuitive.
I think we don't want to take the path of matlab: a huge amount of
powerful functions, but few people know of their powerful possibilities.
regards,
Sebastian
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
On 2014-11-04 15:06, Todd wrote:
> On Tue, Nov 4, 2014 at 2:50 PM, Sebastian Wagner <mailto:se...@sebix.at>> wrote:
>
> Hello,
>
> I want to bring up Issue #2522 'numpy.diff fails on unsigned integers
> (Trac #1929)' [1], as it was resonsible for
On 2014-11-04 19:44, Charles R Harris wrote:
> On Tue, Nov 4, 2014 at 11:19 AM, Sebastian wrote:
>
>> On 2014-11-04 15:06, Todd wrote:
>>> On Tue, Nov 4, 2014 at 2:50 PM, Sebastian Wagner >
>>> <mailto:se...@sebix.at>> wrote:
>>>
>>> Hel
Hi,
I'll just comment on the creation of your dtype:
> dt = [(">> dt = [(">> dty = np.dtype(dt)
>>> dty.names
('>> dt = [(">> dty = np.dtype(('>> dty.names
('f0', 'f1')
>>> dty.descr
[('f0', 'http://mail.scipy.org/mailman/listinfo/numpy-discussion
forward
to Py3 and Numpy is not considered to be compatible to Python 3.
just my 5 cents,
Sebastian
On 03/06/2015 04:37 PM, Ryan Nelson wrote:
> Arnd,
>
> I can see where this is an issue. If you are trying to update your
code for Py3, I still think that it would really help to add a versio
it yourself with various
dependencies. That's easy to accomplish. Have a look at
https://winpython.github.io/
https://code.google.com/p/pythonxy/
http://docs.continuum.io/anaconda/
regards,
Sebastian
On 03/20/2015 09:45 AM, Per Tunedal wrote:
> Hi,
> how do I install Numpy on Windows?
dtxt that allows skipping a header
or other data at the beginning, which do not start with #. This is often
the case with data from measurement device and software. Sometimes these
lines are also used to give informations about the circumstances or the
probe in a non-CSV and non-tab-separated s
here makes any good.
Python is also strong-typed which means that types are never converted
silently. I think a library should follow the behavior of the language.
https://wiki.python.org/moin/Why%20is%20Python%20a%20dynamic%20language%20and%20also%20a%20strongly%20typed%20language
Sebastian
-
> +1. Not a high priority, but it would be nice.
Opened an issue for this: https://github.com/numpy/numpy/issues/6790
> Warren
Sebastian
signature.asc
Description: OpenPGP digital signature
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
lready, last release with 2.7 was in October.
More details on download rates (but unfortunately without absolute
numbers) here:
http://sourceforge.net/projects/winpython/files/
Sebastian
--
python programming - mail server - photo - video - https://sebix.at
To verify my cryptographic signature or s
On 2016-01-27 21:01, Ralf Gommers wrote:
On Wed, Jan 27, 2016 at 7:26 PM, Sebastian Berg
wrote:
Hi all,
in my PR about warnings suppression, I currently also have a commit
which bumps the warning stacklevel to two (or three), i.e. use:
warnings.warn(..., stacklevel=2)
(almost) everywhere
t what is going wrong here. I don't think I'm missing some
dependency nor mixing compilers, but maybe I'm wrong, any hints?
best regards,
- Sebastian Gurovich
[r...@siate soft]# ipython
Python 2.5.1 (r251:54863, Jun 15 2008, 18:24:56)
Type "copyright", "credits"
Thanks for the help.
I think that deleting the old build directory before rebuilding may have
been the trick.
The output below shows i'm no longer reproducing the error.
best wishes,
- Sebastian Gurovich
In [3]: numpy.__version__
Out[3]: '1.3.0'
In [4]: a=numpy.zeros(0x8000,dt
Did you try using the parameter range?
I do something like this.
regards
ax = fig.add_subplot(1,1,1)
> pylab.title(r'\Large BCG NO radio distribution $ \rm{TITLE}$')
> n, bins, patches = pylab.hist(values, bins=math.sqrt(len(values)),
> range=(numpy.mean(values)-3*scientificstat.standardDeviation
ean(Value)-3*scientificstat.standardDeviation(Value),numpy.mean(Value)+3*scientificstat.standardDeviation(bpty_plt),0.1)
>
> gaus=normpdf(gausx,numpy.mean(Value),scientificstat.standardDeviation(Value))
> pylab.plot(gausx,gaus, color='red', lw=2)
> ax.set_xlim(-1.5, 1.5)
>
(almost) produces what I
> want.
> For example look at histogram examples in
>
> http://matplotlib.sourceforge.net/examples/index.html
>
> Josef
>
>
> > josef.p...@gmail.com wrote:
> >> On Fri, Nov 27, 2009 at 9:05 PM, Sebastian wrote:
> >>
> >> ...
&g
Don't know the complete answer - but try cobyla in scipy (scipy.optimize).
-Sebastian
On Tuesday 21 November 2006 15:44, amit soni wrote:
> Hi,
>
> I need to do a quadratic optimization problem in python
> where the constraints are quadratic and objective function is linea
Hi,
Just out of curiosity: Can I ask what is special about a
Geometry.Vector ? What is the difference to a normal numpy array ?
I hope this is a good place to as this ?
Thanks, -Sebastian Haase
On 11/24/06, Gary Ruben <[EMAIL PROTECTED]> wrote:
Hi Konrad,
I can report that 2.7.1 insta
ed into a function, so that
that function could modify it, as in:
const int maxNDim = 20;
int dim[maxNDim];
PyArray_DIMS(imgi, dim);
What am I missing ... ?
-Sebastian
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-discussion
s be passed into a function, so that that function could modify it,
as in:
const int maxNDim = 20;
int dim[maxNDim];
PyArray_DIMS(imgi, dim);
--- What am I missing ... ?
-Sebastian
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://
Hi!
Simple question:
How do I test if an array contains NaN ?
Or others like inf ...?
Thanks,
Sebastian Haase
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-discussion
On 1/4/07, Keith Goodman <[EMAIL PROTECTED]> wrote:
> On 1/4/07, Sebastian Haase <[EMAIL PROTECTED]> wrote:
> > How do I test if an array contains NaN ?
> > Or others like inf ...?
>
> isnan()
> ~isfinite()
> any()
Aah ! thanks,
you mean I have to create
y Wiki numarray page about this ?
( http://www.scipy.org/Converting_from_numarray )
Thanks,
Sebastian Haase
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-discussion
On 1/4/07, Sebastian Haase <[EMAIL PROTECTED]> wrote:
> >>> N.__version__
> '1.0.2.dev3487'
>
> in any case: inside the script it somehow generated a nan --- is
> there a bug in numpy !?
No bug here ! see below !
> I remember that there was some disc
Hi!
when calling compress
I get this error message after moving to numpy:
ValueError: 'condition must be 1-d array'
Is the reason for this the change of the default axis from
axis=0
to
axis=None
What does axis=None mean in this case !?
Thanks,
On 1/4/07, Sebastian Haase <[EMAIL PROTECTED]> wrote:
> Hi!
> when calling compress
> I get this error message after moving to numpy:
>
> ValueError: 'condition must be 1-d array'
>
> Is the reason for this the change of the default axis from
> axis=0
>
$PY $*
I thought that within numpy 1.0 there was no recompile
for external C-modules needed !?
Please explain.
Thanks,
Sebastian Haase
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy
On 1/5/07, Russell E Owen <[EMAIL PROTECTED]> wrote:
> In article
> <[EMAIL PROTECTED]>,
> "Sebastian Haase" <[EMAIL PROTECTED]> wrote:
>
> > On 1/4/07, Sebastian Haase <[EMAIL PROTECTED]> wrote:
> >
> > > >>> N.__ve
You are right again, of course !
Sorry for the noise - I should have just checked the date of my so
file (which is August 15)
At least I understood the "official numpy intention of version 1.0"
right then - just checking ...
Thanks,
Sebastian.
On 1/5/07, Robert Kern <[EMAIL PROT
Hi,
All I did is recompiling my (on source code file) C extension. I made
sure that it was including the current numpy header files.
I did not use anything related to distutils ( no "python setup.py ..." ).
Does that answer your question ?
-Sebastian
On 1/5/07, belinda thom <[EM
'-I ' to your compiler
command line -- this is what setup.py would do for you.
( maybe you need to look in /usr/local/lib/... )
-Sebastian
On 1/5/07, belinda thom <[EMAIL PROTECTED]> wrote:
>
> On Jan 5, 2007, at 5:32 PM, Sebastian Haase wrote:
>
> > Hi,
> > A
efers to the difference between
>
> N.resize(x,6)
>
> and
>
> x.resize(6)
>
Hi Stéfan,
Why is there a needed for this very confusing dualty !?
I would almost like to file a bug report on this !
(It definitily broke "backwards compatibility" for my code coming from
numarra
On 1/8/07, Travis Oliphant <[EMAIL PROTECTED]> wrote:
> Sebastian Haase wrote:
>
> >On 1/8/07, Stefan van der Walt <[EMAIL PROTECTED]> wrote:
> >
> >
> >Hi Stéfan,
> >
> >Why is there a needed for this very confusing dualty !?
> >I
On 1/8/07, Robert Kern <[EMAIL PROTECTED]> wrote:
> Sebastian Haase wrote:
>
> > I would suggest treating this as a real bug!
> > Then it could be fixed immediately.
>
> Deliberate design decisions don't turn into bugs just because you disagree
> with
>
On 1/8/07, Travis Oliphant <[EMAIL PROTECTED]> wrote:
> Alan G Isaac wrote:
>
> >On Mon, 8 Jan 2007, Sebastian Haase apparently wrote:
> >
> >
> >>Please explain again what the original decision was based
> >>on.
> >>
> >>
> >
-number between different platforms ?
I thought this might only be guaranteed for "any given computer" to
reproduce the same numbers.
-Sebastian Haase
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-discussion
On 1/13/07, Keith Goodman <[EMAIL PROTECTED]> wrote:
> On 1/13/07, Sebastian Haase <[EMAIL PROTECTED]> wrote:
> > On 1/13/07, Keith Goodman <[EMAIL PROTECTED]> wrote:
> > > On 1/11/07, Robert Kern <[EMAIL PROTECTED]> wrote:
> > > > Keith Go
On 1/13/07, Keith Goodman <[EMAIL PROTECTED]> wrote:
> On 1/13/07, Sebastian Haase <[EMAIL PROTECTED]> wrote:
> > On 1/13/07, Keith Goodman <[EMAIL PROTECTED]> wrote:
> > > On 1/13/07, Sebastian Haase <[EMAIL PROTECTED]> wrote:
> > > &g
ypes (addressing the shortcoming of the (few) scalar type
provided by standard python).
What would be an easy way to "recognize" such a scalar type in C-API
numpy code and can I extract the C-scalar value from it ?
Thanks for any hints,
Sebastian Haase
__
aligned=True, shape=1)
ProStr[0] ['nAnalog'] = 1
I get this error message:
ValueError: shape-mismatch on array construction
ProStr ['nAnalog'] = 1
works fine.
Surprisingly
ProStr['nAnalog'] = [1,2,3,4]
works.
Could someone explain ?
Thanks,
Seb
.
Thanks,
Sebastian Haase
On 1/16/07, Sebastian Haase <[EMAIL PROTECTED]> wrote:
> Hi!
> After converting to numpy my SWIG-wrapped code runs a bunch of error
> of this type:
>
> TypeError: argument number 9: a 'float' is expected,
> 'numpy.float32(-2.1078
e.org/gmane.comp.python.numeric.general/8521 )
I traced the problem to the libmx system library.
Since I really don't need "long double" (128 bit) operations - I was
wondering if there is a flag to just turn them of?
Will SciPy built with this ? (Is there an equivalent flag maybe ?)
Tha
On 1/25/07, Robert Kern <[EMAIL PROTECTED]> wrote:
> Sebastian Haase wrote:
> > Hi!
> > When I try running my code on
> > panther (10.3) with a numpy that was built on tiger (10.4)
> > it can't load numpy because of missing symbols
> > in numpy/core/umat
On 1/25/07, Steve Lianoglou <[EMAIL PROTECTED]> wrote:
> >> Generally speaking, you need to build binaries on the lowest-
> >> versioned OS X that
> >> you intend to run on.
> >>
> > The problem with building on 10.3 is that it generally comes only with
> > gcc 3.3. I remember that some things re
On 1/26/07, Robert Kern <[EMAIL PROTECTED]> wrote:
> Sebastian Haase wrote:
>
> > The easiest would be to be able to disable the long double functions.
>
> Actually, there are a number of other configuration items that are discovered
> by
> compiling small C programs
How about
mat[0:3, 4:7] += 1
-Sebastian
On 1/29/07, Steve Lianoglou <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I was just curious what the "correct" (fast) way to select and alter
> a submatrix.
>
> For example, say I have a 10x10 array and only want to add so
How about
mat[0:3, 4:7] += 1
-Sebastian
On 1/29/07, Steve Lianoglou <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > I was just curious what the "correct" (fast) way to select and alter
> > a submatrix.
> >
> > For example, say I have a 10x10 array
Hi!
Do numpy memmap have a way of explicitly
flushing data to disk
and/or
closing the memmap.
In numarray these were methods called
memmappedArr.flush()
and
memmappedArr.close()
Thanks,
Sebastian
___
Numpy-discussion mailing list
Numpy-discussion
w__
mm = mmap.mmap(fid.fileno(), bytes, access=acc)
EnvironmentError: [Errno 12] Cannot allocate memory
Calling gc.collect() seams to clean things up and I can create 4-5
times afterwards, before running out of memory space again.
Note: My code is based on code that was tested and worked using numarray.
Thanks,
Sebastian
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-discussion
(), bytes, access=acc)
EnvironmentError: [Errno 12] Cannot allocate memory
Calling gc.collect() seams to clean things up and I can create 4-5
times afterwards, before running out of memory space again.
Note: My code is based on code that was tested and worked using numarray.
Thanks,
Sebastian
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-discussion
rs are allowed to posts to the list - is this correct ?
- Sebastian.
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-discussion
e been deleted. For this reason, __del__() methods
should do the absolute minimum needed to maintain external invariants.
Cheers,
Sebastian Haase
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-discussion
ntf("%12lu %4.1lfGb %p\n",n,n/1024./1024./1024.,p);
free(p); } return 0; }
Hope this helps anyone.
Sebastian
On 2/1/07, Travis Oliphant <[EMAIL PROTECTED]> wrote:
> Louis Wicker wrote:
>
> > Travis:
> >
> > yes it does. Its the Woodcrest ser
ntf("%12lu %4.1lfGb %p\n",n,n/1024./1024./1024.,p);
free(p); } return 0; }
Hope this helps anyone.
Sebastian
On 2/1/07, Travis Oliphant <[EMAIL PROTECTED]> wrote:
> Louis Wicker wrote:
>
> > Travis:
> >
> > yes it does. Its the Woodcrest server c
Travis,
Could you explain what a possible downside of this would be !?
It seems that if you don't need to refer to a specific "self" object
that a class-method is what it should - is this not always right !?
-Sebastian
On 2/1/07, Robert Kern <[EMAIL PROTECTED]> wrote:
&g
hen suggested.
Of course -- as I see it -- the numpy.ones(...) part requires lots of
extra memory. Maybe there are other downsides ... !?
-Sebastian
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-discussion
the problem
> > go away. Why?
>
> Possibly a bug in Numeric.
>
> --
> Robert Kern
Is there *any* support for old Numeric on this list !?
Maybe it should be officially stated that the one way to go is
numpy
and that problems with Numeric ( or numarray )
ap.py", line 67, in __new__
mm = mmap.mmap(fid.fileno(), bytes, access=acc)
OverflowError: memory mapped size is too large (limited by C int)
}}}
I'm using a recent numpy on a 64bit Linux (debian etch, kernel:
2.6.16-2-em64t-p4-smp)
{{{
>>> N.__version__
'1.0.2.dev3509'
Of course !
Now I remember why I didn't test it yet...
Thanks,
-Sebastian
On 2/6/07, Robert Kern <[EMAIL PROTECTED]> wrote:
> Sebastian Haase wrote:
> > Hi,
> > I finally tried to do the test, to memmap a large file
> > filesize: 2.8G
> &
?
How does the speed compare atlas-sse2 vs. atlas-see (ignoring the
repeatablity problem)?
-Sebastian Haase
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-discussion
On 2/16/07, Keith Goodman <[EMAIL PROTECTED]> wrote:
> On 2/15/07, Sebastian Haase <[EMAIL PROTECTED]> wrote:
> > On 2/15/07, Keith Goodman <[EMAIL PROTECTED]> wrote:
> > > On 2/15/07, Keith Goodman <[EMAIL PROTECTED]> wrote:
> > > > I built a
have liked to stay
> > longer. If you want to see the slides for my talk
> > they are here:
> >
> >
> http://us.pycon.org/common/talkdata/PyCon2007/045/PythonTalk.pdf
>
Travis,
very nice overview !
Could the file be renamed to
NumpyTalk.pdf
?
Just a thought...
Hi,
why does
numpy.round(a)
return a float ?
I need something that I can use as indices for another array. Do I
have to (implicitly) create a temporary array and use:
N.round(a).astype(N.int) ?
Or is there a simple, clean and easy way to just round
[1.1 4.8]
into
[1 5]
Thanks,
Sebastian
On 3/6/07, Alan G Isaac <[EMAIL PROTECTED]> wrote:
> On Tue, 6 Mar 2007, Sebastian Haase apparently wrote:
> > why does
> > numpy.round(a)
> > return a float ?
>
> Because it works with a copy of a.
>
> >>> help(N.round)
> Help on function
rays in a for loop using
numpy.ndarray(buffer=largeArray[offset], shape=..., dtype=...) ---
you increment offset appropriately during the loop
3) then you can reset all small arrays to new random numbers with one
call to resetting the large array ((they all have the same statistics
Hi !
This is really only one question:
Which dtypes are supported by numexpr ?
We are very interested in numexpr !
Where is the latest / most-up-to-date documentation ?
Thanks,
Sebastian Haase
___
Numpy-discussion mailing list
Numpy-discussion
file there should be this option:
[notification]
always_notify_owner = true
Why is this (or is it !?) not used in numpy/scipy TRAC system ?
I think - since one has to sign up using an email address - that it's
naturally to expect that one would get comments copied by email.
-Sebastian
Sorry for being so dense - what do the numbers mean ?
S.H.
On 3/10/07, Steven H. Rogers <[EMAIL PROTECTED]> wrote:
> Thanks to all who responded to my question about teaching array
> programming. I've compiled a brief summary of the responses.
>
> NumPy
> =
> * Subject
> - Physics/Astronom
file type for dynamic loading
>
> How can I fix this problem? My system is Mac OSX Tiger- Pentium.
> Thanks.
Hi Nevin,
I got the same error message -- your scipy package is for non-Intel (PPC) !
You either have to recompile scipy yourself -- which requires a
working fortran compiler -- or
wever, people here are very helpful - once you go with the new
numpy - to help converting any old code you might have. Essentially
numarray and numpy (mostly, 98% ?) Python-code compatible anyway !!!
Do the the switch and you will get help.
Regards,
Sebastian
On 3/6/07, Duhaime Johanne &l
Hi,
Please remind me what's wrong with pylab's
rand and randn !
I just learned about their existence recently and thought
they seem quite handy and should go directly into (the top-level of) numpy.
Functions that have the same name and do the same thing don't conflict
either ;-)
-
take a look at the "one-way" calls to
ensure that functions, that would block, won't wait for the function
to return)
Just a thought --
-Sebastian Haase
On 3/13/07, Bill Baxter <[EMAIL PROTECTED]> wrote:
> Howdy Folks,
>
> I was missing the good ole days of
On 3/14/07, Timothy Hochberg <[EMAIL PROTECTED]> wrote:
>
>
> On 3/14/07, Sebastian Haase <[EMAIL PROTECTED]> wrote:
> > Hi,
> > Please remind me what's wrong with pylab's
> > rand and randn !
> > I just learned about their existence recent
eally hard to
*find* (as in *see* n the popup-list) the pylab-only functions. --
what can I do about this ?
Thanks,
Sebastian
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-discussion
[ 8, -2],
> > [ 9, -1]])
> >
> >
> > ?
> >
> > I thought there would be an easier way. Did I overlook something?
>
> How about
>
> N.vstack((a,b)).T
>
Also mentioned here should be the use of
newaxis.
As in
a[:,newaxis]
However I never got a "good feel" for how to use it, so I can't
complete the code you would need.
-Sebastian Haase
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-discussion
On 3/22/07, Bill Baxter <[EMAIL PROTECTED]> wrote:
> On 3/23/07, Eric Firing <[EMAIL PROTECTED]> wrote:
> > Sebastian Haase wrote:
> > > On 3/22/07, Stefan van der Walt <[EMAIL PROTECTED]> wrote:
> > >> On Thu, Mar 22, 2007 at 08:13:22PM -0400, Brian
consider checking for "native byte order"
as part of your inplace-typemap.
I found that to be a problem in my SWIG type maps
that I hi-jacked / boiled down from the older numpy swig files.
(They are mostly for 3D image data, only for a small number of types)
a[mask,-1] with a[mask,-1,...] and such. Hmm. Not bad reminder,
> thanks.
Hold on -- aren't the "..." at the *end* always implicit:
I you have
a.shape = (6,5,4,3)
a[3,2] is the same as a[3,2,:,:] is the same as a[3,2,...]
only if you wanted a[...,3,2] you would have to chang
ms, the
typecheck returns False (if I remember right).
For me this is just a "last-line of defence" - meaning that I have
most of my functions wrapped by another level of python "convenience"
functions, and those take care of type and byte-order issues
beforehand as needed.
-Seba
broadly used as -- Python might be just better off having a
simple, concise and limited set of infix operators. I assume that
this is the official argument.
I got especially "worried" when being remember of the "\"
right-to-left division operator. (As I said, it very useful to h
hat is it ?
b) I don't think that if m[1] would return a (rank 2) matrix, that
m[1].A could return a (rank 1) array ...
c) I'm curious if there is a unique way to extend the matrix class
into 3D or ND.
-Sebastian
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-discussion
( != SciPy )
Some links are here:
http://www.bsp-worldwide.org/
http://en.wikipedia.org/wiki/Bulk_Synchronous_Parallel
Evaluating Scientific Python/BSP on selected parallel computers
http://ove.nipen.no/diplom/
http://dirac.cnrs-orleans.fr/plone/software/scientificpython/
- Sebastian Haase
the 1st dimension,
would only need about 1MB -- that can not really explain the memory
error.
Thanks,
Sebastian
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-discussion
Another rather old ticket is this one:
http://projects.scipy.org/scipy/numpy/ticket/454>
Any comments on this !?
Thanks,
-Sebastian
On 2/16/07, NumPy <[EMAIL PROTECTED]> wrote:
> #454: Importing numpy prevents decrementing references for loc
Is enthought now defaulting to numpy ?
-Sebastian
On 4/4/07, Robert Kern <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] wrote:
> > --- Discussion of Numerical Python > [EMAIL PROTECTED]
> > wrote:
>
> >>> If I get the latest
> > SVN of the
ot; ) would be created with b.x
being 6 -- because 'x' is a class attribute and nor a instance
attribute !?
This is obviously a beginners question - and I'm hopefully missing something.
Thanks,
Sebastian Haase
On 4/3/07, Gael Varoquaux <[EMAIL PROTECTED]> wrote:
&g
On 4/4/07, Robert Kern <[EMAIL PROTECTED]> wrote:
> Sebastian Haase wrote:
> > Hello Gael,
> >
> > Short question regarding your tutorial -- I'm very intrigued by traits
> > and would like to use them too
> > Why do you define e.g. the P
st leaving out the "Scipy_" part.
BTW, do peer review papers count !? I have two of them, using numpy
(originally numarray, but now it's numpy)
Maybe the projects should be in categories:
- open source
- commercial (?)
- papers
- ??
-Sebastian
On 4/4/07, Bill Baxter <[E
ently the
tutorial is supposed to "look nice" [[ don't get me wrong, I
really recommend the tutorial, I like it, I think it's good ]]
But some (even if) ugly things should be said up front, if they clear
up the way.
Python 3000 will also default to new-style classes -- so
Hi Anne,
I'm just starting to look into your code (sound very interesting -
should probably be put onto the wiki)
-- quick note:
you are mixing tabs and spaces :-(
what editor are you using !?
-Sebastian
On 4/17/07, Anne Archibald <[EMAIL PROTECTED]> wrote:
> On 17/04/07, Lou
functions in
> linalg, nothing else.
>
Hi,
I don't know much about ATLAS -- would there be other numpy functions
that *could* or *should* be implemented using ATLAS !?
Any ?
-Sebastian
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-discussion
On 4/17/07, Anne Archibald <[EMAIL PROTECTED]> wrote:
> On 18/04/07, Robert Kern <[EMAIL PROTECTED]> wrote:
> > Sebastian Haase wrote:
> >
> > > Hi,
> > > I don't know much about ATLAS -- would there be other numpy functions
> > > that *c
On 4/18/07, Robert Kern <[EMAIL PROTECTED]> wrote:
> Sebastian Haase wrote:
> > On 4/17/07, Anne Archibald <[EMAIL PROTECTED]> wrote:
> >> On 18/04/07, Robert Kern <[EMAIL PROTECTED]> wrote:
> >>> Sebastian Haase wrote:
> >>>
> >&g
data that was allocated via new[] -- so two different deallocation
functions (free() and delete[], respectively) would be required for
this to be trigged, once the reference counter goes back to zero.
Thanks,
Sebastian Haase
___
Numpy-discussion maili
ine /any/ function to be
called once the ref.count goes to zero - right?
Could someone with C-API knowledge put a sample together !? This
would also be quite useful to be used with a SWIG output typemap.
-Sebastian
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-discussion
<", ">" and "="
I assume that if arr.dtype.byteorder is "="
then, even on a little endian system
the comparison arr.dtype.byteorder == "<" still fails !?
Or are the == and != operators overloaded !?
Thanks,
Sebastian Haase
_
any comments !?
On 6/25/07, Sebastian Haase <[EMAIL PROTECTED]> wrote:
> Hi,
> Suppose I'm on a little-edian system.
> Could I have a little-endian numpy array arr, where
> arr.dtype.byteorder
> would actually be "<"
> instead of "=" !?
>
1 - 100 of 892 matches
Mail list logo
