Re: [Numpy-discussion] Compiling numpy using icc gets missing library error

2011-03-25 Thread Hoyt Koepke
Okay, even better news. After a little bit of probing around, it turns out that some of the errors, namely the one in the interpolator, were due to intel's handling of floating point values at higher optimization levels. Thus the two rather important flags, if you wish to avoid difficult-to-expla

Re: [Numpy-discussion] Compiling numpy using icc gets missing library error

2011-03-25 Thread Pauli Virtanen
On Fri, 25 Mar 2011 13:46:41 -0700, Hoyt Koepke wrote: [clip] > Also, I could still not get the CloughTocher2DInterpolator to not > segfault. Backtrace would be useful here. It's probably best to recompile with "-O0" and some debug flags enabled in the compiler to get something reasonable out.

Re: [Numpy-discussion] Compiling numpy using icc gets missing library error

2011-03-25 Thread Hoyt Koepke
Okay, last update. I finally have got everything to work. It turns out the problems that I had earlier with f2py were due to intel's -ipo flag. So the only place this flag works is with the C++ code, not fortran or c. Also, I forgot to mention -- the qhull_a.h method has a workaround for some a

[Numpy-discussion] ANN: TreeDict 0.12, a lightweight library for hierarchical parameter/data management

2011-03-25 Thread Hoyt Koepke
Hello, I thought the numpy/scipy community might be particularly interested in this library, so here goes: I'm pleased to announce a release of the next version of TreeDict, a dictionary-like, hierarcical python container to simplify the bookkeeping surrounding parameters, variables and data. It

Re: [Numpy-discussion] 1.6.0b1 half float buffer bug?

2011-03-25 Thread Mark Wiebe
On Fri, Mar 25, 2011 at 11:28 AM, Mark Wiebe wrote: > On Fri, Mar 25, 2011 at 11:14 AM, Eli Stevens (Gmail) < > wickedg...@gmail.com> wrote: > >> On Fri, Mar 25, 2011 at 10:35 AM, Mark Wiebe wrote: >> > That said, I think starting a discussion with the Python core developers >> > about the float

Re: [Numpy-discussion] 1.6.0b1 half float buffer bug?

2011-03-25 Thread Charles R Harris
On Fri, Mar 25, 2011 at 12:28 PM, Mark Wiebe wrote: > On Fri, Mar 25, 2011 at 11:14 AM, Eli Stevens (Gmail) < > wickedg...@gmail.com> wrote: > >> On Fri, Mar 25, 2011 at 10:35 AM, Mark Wiebe wrote: >> > That said, I think starting a discussion with the Python core developers >> > about the float

Re: [Numpy-discussion] 1.6.0b1 half float buffer bug?

2011-03-25 Thread Mark Wiebe
On Fri, Mar 25, 2011 at 11:14 AM, Eli Stevens (Gmail) wrote: > On Fri, Mar 25, 2011 at 10:35 AM, Mark Wiebe wrote: > > That said, I think starting a discussion with the Python core developers > > about the float16 type is worthwhile. There might be interest in > supporting > > the float16 type in

Re: [Numpy-discussion] 1.6.0b1 half float buffer bug?

2011-03-25 Thread Eli Stevens (Gmail)
On Fri, Mar 25, 2011 at 10:35 AM, Mark Wiebe wrote: > That said, I think starting a discussion with the Python core developers > about the float16 type is worthwhile. There might be interest in supporting > the float16 type in the struct interface, something that would be required > as part of ame

Re: [Numpy-discussion] 1.6.0b1 half float buffer bug?

2011-03-25 Thread Eli Stevens (Gmail)
On Fri, Mar 25, 2011 at 10:21 AM, Pauli Virtanen wrote: > The buffer interface cannot be used to export the half-float types, since > the type is not specified in PEP 3118. Numpy cannot unilaterally add > nonstandard format codes to the spec. > > What can be done instead is exporting the half-floa

Re: [Numpy-discussion] 1.6.0b1 half float buffer bug?

2011-03-25 Thread Mark Wiebe
On Fri, Mar 25, 2011 at 10:21 AM, Pauli Virtanen wrote: > Fri, 25 Mar 2011 10:00:24 -0700, Eli Stevens (Gmail) wrote: > > I'm working on getting support for 16-bit floats into cython and have > > run into what seems like a numpy bug (I'm a new contributor to both > > projects, so bear with me ;).

Re: [Numpy-discussion] Ticket closing policy

2011-03-25 Thread Mark Wiebe
On Thu, Mar 24, 2011 at 8:22 PM, David wrote: > Hi Mark, hi all, > > I noticed you did a lot of cleaning in the bug trackers, thank you for > helping there, this is sorely needed. > > However, I noticed quite a few tickets were closed as wontfix even > though they are valid. I understand the conc

Re: [Numpy-discussion] 1.6.0b1 half float buffer bug?

2011-03-25 Thread Pauli Virtanen
Fri, 25 Mar 2011 10:00:24 -0700, Eli Stevens (Gmail) wrote: > I'm working on getting support for 16-bit floats into cython and have > run into what seems like a numpy bug (I'm a new contributor to both > projects, so bear with me ;). > > https://github.com/wickedgrey/numpy/ commit/29f9f1b709cc2c34

[Numpy-discussion] 1.6.0b1 half float buffer bug?

2011-03-25 Thread Eli Stevens (Gmail)
I'm working on getting support for 16-bit floats into cython and have run into what seems like a numpy bug (I'm a new contributor to both projects, so bear with me ;). https://github.com/wickedgrey/numpy/commit/29f9f1b709cc2c346b8514859c58a761df80f031 Adding NPY_HALF to the switch statement on li

[Numpy-discussion] HP-UX users, please test distutils changes

2011-03-25 Thread Ralf Gommers
Hi, Here are some updated compile flags for HP-UX that were submitted on the bug tracker. It would be nice to have someone confirm this works: https://github.com/rgommers/numpy/tree/hp Thanks, Ralf ___ NumPy-Discussion mailing list NumPy-Discussion@scip

[Numpy-discussion] loadtxt/savetxt tickets

2011-03-25 Thread Charles R Harris
Hi All, Could someone with an interest in loadtxt/savetxt look through the associated tickets? A search on the tickets using either of those keys will return fairly lengthy lists. Chuck ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http:/

Re: [Numpy-discussion] So...

2011-03-25 Thread Pauli Virtanen
Fri, 25 Mar 2011 13:40:54 +0100, Sturla Molden wrote: > Den 25.03.2011 13:33, skrev Pauli Virtanen: >> That npy_intp will not be redefined as ssize_t does not mean that the >> type of array indices could not be changed. > > By the way, what is the resonable array index for AMD64, where 32-bit is >

Re: [Numpy-discussion] So...

2011-03-25 Thread Sturla Molden
Den 25.03.2011 13:33, skrev Pauli Virtanen: > That npy_intp will not be redefined as ssize_t does not mean that the > type of array indices could not be changed. By the way, what is the resonable array index for AMD64, where 32-bit is the native offset size but size_t is 64 bit? Sturla _

Re: [Numpy-discussion] So...

2011-03-25 Thread Pauli Virtanen
Fri, 25 Mar 2011 13:23:11 +0100, Sturla Molden wrote: > FFTs should keep the GIL locked, because sharing the interpreter is not > funny. > Array indices should be sizeof(void*), because following C standard and > Python C API is lame. > Median should be calculated in O(n log n) instead of O(n) time

[Numpy-discussion] So...

2011-03-25 Thread Sturla Molden
FFTs should keep the GIL locked, because sharing the interpreter is not funny. Array indices should be sizeof(void*), because following C standard and Python C API is lame. Median should be calculated in O(n log n) instead of O(n) time, because redundant sorting is gymnatics for the CPU. But at

Re: [Numpy-discussion] help me

2011-03-25 Thread dileep kunjaai
Thank you sir,,, Thank you very much. On Fri, Mar 25, 2011 at 5:32 PM, Miguel de Val-Borro wrote: > On Fri, Mar 25, 2011 at 05:28:50PM +0530, dileep kunjaai wrote: > > Dear sir, > > I have a numpy array,,. in which i have to choose only different values > > only, > > For example > > >

Re: [Numpy-discussion] help me

2011-03-25 Thread Miguel de Val-Borro
On Fri, Mar 25, 2011 at 05:28:50PM +0530, dileep kunjaai wrote: > Dear sir, > I have a numpy array,,. in which i have to choose only different values > only, > For example > > Let A= [ 20. 21. 22. 23. 24. 25. 20. 21. 22. 23. 24. 25. > 20. 21. 22. 23. 24. 25. 20. 21. 22. 23.

[Numpy-discussion] help me

2011-03-25 Thread dileep kunjaai
Dear sir, I have a numpy array,,. in which i have to choose only different values only, For example Let A= [ 20. 21. 22. 23. 24. 25. 20. 21. 22. 23. 24. 25. 20. 21. 22. 23. 24. 25. 20. 21. 22. 23. 24. 25. 20. 21. 22. 23. 24. 25.] then the answer is [20, 21. 22. 2

Re: [Numpy-discussion] when numpy in Linux apt will be updated? It's still 1.3.0 with many bugs

2011-03-25 Thread David Cournapeau
2011/3/24 Dmitrey : > hi, > when numpy in Linux apt will be updated? It's still 1.3.0 with many bugs We do not decide what Ubuntu and/or debian are putting into their release. You should send bug report to those distributions bug trackers if you want to see things improve for those distributions.

Re: [Numpy-discussion] Ticket closing policy

2011-03-25 Thread Ralf Gommers
On Fri, Mar 25, 2011 at 4:22 AM, David wrote: > Hi Mark, hi all, > > I noticed you did a lot of cleaning in the bug trackers, thank you for > helping there, this is sorely needed. > > However, I noticed quite a few tickets were closed as wontfix even > though they are valid. I checked all the won

Re: [Numpy-discussion] Compiling numpy using icc gets missing library error

2011-03-25 Thread Hoyt Koepke
Okay, so here's a follow up on my progress. Apologies in advance for the long email here, but I'd like to be thorough about this before I forget. For the sake of completeness, here's my setup. I'm running python 2.7.1 compiled from source with icc. I'm running ubuntu 10.10 on one of intel's new