Robert is right, you can always implement your own function.
What version of numpy and Python are you using ?
There may be something you can add to your numpy installation related to
the old Numeric support which I believe is now deprecated.
Raul
On 25/02/2014 4:28 AM, Robert Kern wrote:
>
John,
Just noticed this message,
We are already cleaning up all of our code to not be numpy based but for
porting from Numeric to numpy:
In our C code we settled for the following,
#define NUMPY
#if !defined(NUMPY)
#include "arrayobject.h"
#else
#include "numpy/oldnumeric.h"
#endi
On 05/08/2013 2:17 PM, Charles R Harris
wrote:
On Mon, Aug 5, 2013 at 2:00 PM, Raul Cota
<r...@virtualmaterials.com>
wrote:
Hello,
I had not updated my code for a few months. I updated to
Hello,
I had not updated my code for a few months. I updated today to the
latest source and I cannot build anymore,
(Windows, Python 2.6)
When I do,
python setup.py build
I get,
"""
Running from numpy source directory.
Traceback (most recent call last):
File "setup.py", line 192, in
For the sake of completeness, I don't think I ever mentioned what I used
to profile when I was working on speeding up the scalars. I used AQTime
7. It is commercial and only for Windows (as far as I know). It works
great and it gave me fairly accurate timings and all sorts of visual
navigation
It is great that you are looking into this !! We are currently
running on a fork of numpy because we really need these
performance improvements .
I noticed that, as suggested, you took from the pull request I
posted a while ago for the
Few comments on the topic,
The postings I did to the list were in numpy 1.6 but the pull
requests were done on the latest code at that time I believe 1.7 .
There are still a few comments pending that I have not had a
chance to look into, but that is a separ
Josef's suggestion is the first thing I'd try.
Are you doing any of this in C ? It is easy to end up duplicating memory
that you need to Py_DECREF .
In the C debugger you should be able to monitor the ref count of your
python objects.
btw, for manual tracking of reference counts you can do,
sy
inreg.OpenKey(_winreg.HKEY_LOCAL_MACHINE,
'SOFTWARE')
vmg_key = _winreg.CreateKey(software_key, 'VMG')
_winreg.SetValue(vmg_key, dllkey, _winreg.REG_SZ,
os.path.abspath(os.curdir))
_winreg.CloseKey(vmg_key)
_winreg.CloseKey(software_key)
based on our situation
On 10/01/2013 9:02 AM, Christopher Hanley wrote:
I'm all for a big scary warning on import. Fair
warning is good for everyone, not just our developers.
agree
As
We can keep testing it in coming
versions while we catch up.
Raul Cota (P.Eng., Ph.D. Chemical Engineering)
Research & Development Manager
Virtual Materials Group - Canada
www.virtualmaterials
ing Msg: Using deprecated NumPy API, disable
it by #defining NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION
c:\python27\lib\site-packages\numpy\core\include\numpy\npy_deprecated_api.h
8
"""
Raul Cota
On 07
On 07/01/2013 9:22 AM, Charles R Harris
wrote:
On Sun, Jan 6, 2013 at 9:15 PM, Raul Cota
<r...@virtualmaterials.com>
wrote:
I realize we may be a minority but it would be very
nice if suppo
I realize we may be a minority but it
would be very nice if support for numeric could be kept for a few
more versions. We don't have any particular needs for numarray.
We just under went through an extremely long and painful process
to upgrade our software
On 04/01/2013 5:44 PM, Nathaniel Smith wrote:
> On Fri, Jan 4, 2013 at 11:36 PM, Raul Cota wrote:
>> On 04/01/2013 2:33 PM, Nathaniel Smith wrote:
>>> On Fri, Jan 4, 2013 at 6:50 AM, Raul Cota wrote:
>>>> On 02/01/2013 7:56 AM, Nathaniel Smith wrote:
>>>&g
On 04/01/2013 2:33 PM, Nathaniel Smith wrote:
> On Fri, Jan 4, 2013 at 6:50 AM, Raul Cota wrote:
>> On 02/01/2013 7:56 AM, Nathaniel Smith wrote:
>>> But, it's almost certainly possible to optimize numpy's float64 (and
>>> friends), so that they are them
wrote:
> On Fri, Dec 21, 2012 at 7:20 PM, Raul Cota wrote:
>> Hello,
>>
>>
>> On Dec/2/2012 I sent an email about some meaningful speed problems I was
>> facing when porting our core program from Numeric (Python 2.2) to Numpy
>> (Python 2.6). Some of our t
On 02/01/2013 7:58 AM, Nathaniel Smith wrote:
> On Wed, Jan 2, 2013 at 2:56 PM, Nathaniel Smith wrote:
>> On Fri, Dec 21, 2012 at 7:20 PM, Raul Cota wrote:
>>> b.1)
>>> I noticed that PyFloat * Float64 resulted in an unnecessary "on the fly"
>>&g
On 02/01/2013 7:56 AM, Nathaniel Smith wrote:
On Fri, Dec 21, 2012 at 7:20 PM, Raul Cota wrote:
Hello,
On Dec/2/2012 I sent an email about some meaningful speed problems I was
facing when porting our core program from Numeric (Python 2.2) to Numpy
(Python 2.6). Some of our tests went from
week ago, using the float() function is not
needed to get it to run in 1 second.
Raul Cota
On 30/12/2012 5:35 PM, Chris Barker - NOAA Federal wrote:
> On Sun, Dec 30, 2012 at 3:41 AM, Happyman wrote:
>> nums=32
>> rows=120
>> cols=150
>>
>> f
the power function. I am not sure what else could be there.
=====
That's about it. Sorry for the long email. I tried to summarize as much
as possible.
Let me know if you have any questions or if you want the actual files I
modified.
Cheers,
Raul Cota
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
e
> environments?
>
> Sturla
>
>
> Den 14. des. 2012 kl. 05:14 skrev Raul Cota :
>
>>
>> +1 from me
>>
>> For what is worth, we are just moving forward from Python 2.2 / Numeric
>> and are going to 2.6 and it has been rather painful because of the
+1 from me
For what is worth, we are just moving forward from Python 2.2 / Numeric
and are going to 2.6 and it has been rather painful because of the
several little details of extensions and other subtleties. I believe we
will settle there for a while. For companies like ours, it is a big
pro
assuming savetxt does not support it,
I modified a bit of code I had to do what I think you need ONLY works
for a 1D array and wrapped it into a function that writes in properly
formatted columns. I didn't really test it other than what is there. I
"dressed" it like savetxt but the glaring diff
Chris,
thanks for the feedback,
fyi,
the minor changes I talked about have different performance enhancements
depending on scenario,
e.g,
1) Array * Array
point = array( [2.0, 3.0])
scale = array( [2.4, 0.9] )
retVal = point * scale
#The line above runs 1.1 times faster with my new code (but
On 03/12/2012 4:14 AM, Nathaniel Smith wrote:
> On Mon, Dec 3, 2012 at 1:28 AM, Raul Cota wrote:
>> I finally decided to track down the problem and I started by getting
>> Python 2.6 from source and profiling it in one of my cases. By far the
>> biggest bott
ke this work:
>
> python -m numba filename.py
>
> To get an effective autojit on all the filename.py functions (and optionally
> on all python modules it imports).The autojit works out of the box today
> --- you can get Numba from PyPI (or inside of the completely free Anaconda
Thanks Christoph.
It seemed to work. Will do profile runs today/tomorrow and see what come
out.
Raul
On 02/12/2012 7:33 PM, Christoph Gohlke wrote:
> On 12/2/2012 5:28 PM, Raul Cota wrote:
>> Hello,
>>
>> First a quick summary of my problem and at the end I include the
Hello,
First a quick summary of my problem and at the end I include the basic
changes I am suggesting to the source (they may benefit others)
I am ages behind in times and I am still using Numeric in Python 2.2.3.
The main reason why it has taken so long to upgrade is because NumPy
kills perfo
29 matches
Mail list logo
