Thanks for the input, guys. I'll be looking into the
scikits.timeseries package before submitting an application.
>was it the intent that these new data types should be implemented at the
>C/cython level?
That's fine with me. I've got plenty of experience in C++, and I've
delved into my fair shar
Hi all,
How do I compile any legacy C and Fortran code in 64 bit
using gcc/gfortran ?
Any pointer would be appreciated.
Thanks in advance
Nils
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://mail.
On Wed, Mar 25, 2009 at 10:33 AM, Pierre GM wrote:
> Ciao Marty,
> Great idea indeed ! However, I'd really like to have an easy way to
> plug the suggested dtype w/ the existing Date class from the
> scikits.timeseries package (Date is implemented in C, you can find the
> sources through the lin
On Wed, Mar 25, 2009 at 9:50 PM, F. David del Campo Hill
wrote:
>
> Also (and pardon me if this is a stupid question), wouldn't the
> non-SSE installer work anywhere (albeit more slowly)?
Yes, it would - but then people would complain about numpy being slow,
etc... because average users w
On Wed, Mar 25, 2009 at 07:17, F. David del Campo Hill
wrote:
> Note: I do not work for Microsoft or receive any money from them; I am just
> an IT officer one of whose users needs Numpy for teaching. I do not know what
> Numpy does or doesn't do, I just need it installed fast.
[Disclaimer: I w
Ciao Marty,
Great idea indeed ! However, I'd really like to have an easy way to
plug the suggested dtype w/ the existing Date class from the
scikits.timeseries package (Date is implemented in C, you can find the
sources through the link on http://pytseries.sourceforge.net). I agree
that th
Hello Marty,
A Tuesday 24 March 2009, Marty Fuhry escrigué:
> Hello,
>
> Sorry for any overlap, as I've been referred here from the scipi-dev
> mailing list.
> I was reading through the Summer of Code ideas and I'm terribly
> interested in date/time proposal
> (http://projects.scipy.org/numpy/brow
Dan Yamins wrote:
>
>
> > Then I attempt
> >>>> A = numpy.rec.fromarrays(L,names =
> ['Aggregates','__color__'])
>
> So what happens when you set the dtype here?
>
>
> Since you have variable lengths of strings, numpy probably has guessed
> incorrectly. I would also chec
>
> > Then I attempt
> >>>> A = numpy.rec.fromarrays(L,names = ['Aggregates','__color__'])
>
> So what happens when you set the dtype here?
>
> Since you have variable lengths of strings, numpy probably has guessed
> incorrectly. I would also check that Col1 and Col2 are what you expect,
> esp
Dan Yamins wrote:
> Hi all,
>
> I'm having a seg fault error from numpy.rec.fromarrays.
>
> I have a python list
> L = [Col1, Col2]
> where Col1 and Col2 are python lists of short strings (the max length
> of Col1 strings is 4 chars and max length of Col2 is 7 chars). The
> len of Col1 and
Kevin,
In this instance, the best thing is to write a wrapper function that
calls your matSum() function, and takes a double* rather than a
double**. You can %ignore the original function and %rename the
wrapper so that the python interface gets the name you want.
On Mar 25, 2009, at 7:39
Dear David,
I did not have any problems in extracting the three EXE installers
(numpy-1.3.0b1-nosse.exe, numpy-1.3.0b1-sse2.exe, numpy-1.3.0b1-sse3.exe) from
the superpack (7zip can do that with a right-click), it is when I tried to
extract the files inside the per-arch installers that
Hi Davie,
F. David del Campo Hill wrote:
> Sometimes, EXE setup packages are just MSI packages wrapped in an EXE
> file, that is why I tried to extract the files from your superpack (without
> luck).
>
Currently, with the superpack installer, the individual per arch
installers can be e
Dear David,
Without going into the inherent benefits of the MSI (Microsoft
Installer) architecture over other EXE setup formats, its main advantage is
that MSI packages can be added to Group Policy Objects in Active Directory
(Windows domain controller database); this means that, as lon
2009/3/25 Jesper Larsen :
> import numpy as npy
> a = npy.empty((2), dtype=npy.object_)
>
> # Works fine:
> for i in range(len(a)):
> a[i] = []
> print a
>
> # Does not work:
> a[:] = []
> a[:] = list()
Slightly simpler would be:
In [26]: x = np.empty((2,), dtype=object)
In [27]: x[:] = [[] * le
Thanks Bill, it helps me a lot ! My function works fine now.
But I encounter an other problem. This time with a NumPy array of 2
dimensions.
Here is the function I want to use :
//
double matSum(double** mat, int n, int m){
int i,j;
double sum = 0.0;
for (i=0;i wrote:
Wed, 25 Mar 2009 12:04:43 +0100, Jesper Larsen wrote:
> I have a problem with array broadcasting for object arrays and list. I
> would like to create a numpy array containing empty lists (initially - I
> will append to them later):
[clip]
> Is it possible to broadcast a list to all elements of a nu
Hi numpy people,
I have a problem with array broadcasting for object arrays and list. I
would like to create a numpy array containing empty lists (initially -
I will append to them later):
import numpy as npy
a = npy.empty((2), dtype=npy.object_)
# Works fine:
for i in range(len(a)):
a[i] = []
On Wed, Mar 25, 2009 at 03:00, Brennan Williams
wrote:
> On a more serious note, it is clear that, as expected, operating on
> elements of an array inside a Python for loop is slow for large arrays.
> Soon I will be writing an import interface to read corner point grid
> geometries and I'm curren
Robert Kern wrote:
> On Wed, Mar 25, 2009 at 00:09, Brennan Williams
> wrote:
>
>> Robert Kern wrote:
>>
>>> On Tue, Mar 24, 2009 at 18:29, Brennan Williams
>>> wrote:
>>>
>>>
I have an array (porvatt.yarray) of ni*nj*nk values.
I want to create two further arrays.
>
20 matches
Mail list logo
