Re: [Numpy-discussion] GSOC 2013

2013-03-06 Thread Eric Firing
On 2013/03/05 8:14 AM, Kurt Smith wrote: > On Tue, Mar 5, 2013 at 1:45 AM, Eric Firing wrote: >> On 2013/03/04 9:01 PM, Nicolas Rougier wrote: > This made me think of a serious performance limitation of structured > dtypes: a > structured dtype is always "packed", which may lead to te

Re: [Numpy-discussion] GSOC 2013

2013-03-06 Thread Kurt Smith
On Wed, Mar 6, 2013 at 4:29 AM, Francesc Alted wrote: > On 3/5/13 7:14 PM, Kurt Smith wrote: >> On Tue, Mar 5, 2013 at 1:45 AM, Eric Firing wrote: >>> On 2013/03/04 9:01 PM, Nicolas Rougier wrote: >> This made me think of a serious performance limitation of structured >> dtypes: a >>

Re: [Numpy-discussion] GSOC 2013

2013-03-06 Thread Francesc Alted
On 3/5/13 7:14 PM, Kurt Smith wrote: > On Tue, Mar 5, 2013 at 1:45 AM, Eric Firing wrote: >> On 2013/03/04 9:01 PM, Nicolas Rougier wrote: > This made me think of a serious performance limitation of structured > dtypes: a > structured dtype is always "packed", which may lead to terrib

Re: [Numpy-discussion] GSOC 2013

2013-03-06 Thread Todd
On Mar 5, 2013 7:53 PM, "Nathaniel Smith" wrote: > > On 4 Mar 2013 23:21, "Jaime Fernández del Río" wrote: > > > > On Mon, Mar 4, 2013 at 2:29 PM, Todd wrote: > >> > >> > >> 5. Currently dtypes are limited to a set of fixed types, or combinations of these types. You can't have, say, a 48 bit fl

Re: [Numpy-discussion] GSOC 2013

2013-03-05 Thread Nathaniel Smith
On 4 Mar 2013 23:21, "Jaime Fernández del Río" wrote: > > On Mon, Mar 4, 2013 at 2:29 PM, Todd wrote: >> >> >> 5. Currently dtypes are limited to a set of fixed types, or combinations of these types. You can't have, say, a 48 bit float or a 1-bit bool. This project would be to allow users to cr

Re: [Numpy-discussion] GSOC 2013

2013-03-05 Thread Kurt Smith
On Tue, Mar 5, 2013 at 1:45 AM, Eric Firing wrote: > On 2013/03/04 9:01 PM, Nicolas Rougier wrote: >>> >This made me think of a serious performance limitation of structured >>> >dtypes: a >>> >structured dtype is always "packed", which may lead to terrible byte >>> >alignment >>> >for common typ

Re: [Numpy-discussion] GSOC 2013

2013-03-05 Thread Andrew Collette
>> 5. Currently dtypes are limited to a set of fixed types, or combinations >> of these types. You can't have, say, a 48 bit float or a 1-bit bool. This >> project would be to allow users to create entirely new, non-standard dtypes >> based on simple rules, such as specifying the length of the si

Re: [Numpy-discussion] GSOC 2013

2013-03-04 Thread Eric Firing
On 2013/03/04 9:01 PM, Nicolas Rougier wrote: >> >This made me think of a serious performance limitation of structured >> >dtypes: a >> >structured dtype is always "packed", which may lead to terrible byte >> >alignment >> >for common types. For instance, `dtype([('a', 'u1'), ('b', >> >'u8')]).i

Re: [Numpy-discussion] GSOC 2013

2013-03-04 Thread Nicolas Rougier
> This made me think of a serious performance limitation of structured dtypes: a > structured dtype is always "packed", which may lead to terrible byte alignment > for common types. For instance, `dtype([('a', 'u1'), ('b', > 'u8')]).itemsize == 9`, > meaning that the 8-byte integer is not aligned

Re: [Numpy-discussion] GSOC 2013

2013-03-04 Thread Kurt Smith
On Mon, Mar 4, 2013 at 4:29 PM, Todd wrote: > > 3. Structured arrays are accessed in a manner similar to python dictionaries, > using a key. However, they don't support the normal python dictionary > methods like keys, values, items, iterkeys, itervalues, iteritems, etc. This > project would be

Re: [Numpy-discussion] GSOC 2013

2013-03-04 Thread Till Stensitzki
Todd gmail.com> writes: > > I have some ideas, but they may not be suitable for GSOC or may just be terrible ideas, so feel free to reject them: > I have also a possible (terrible?) idea in my mind: Including (maybe optional as blas) faster transcendental functions into numpy. Something like ht

Re: [Numpy-discussion] GSOC 2013

2013-03-04 Thread Jaime Fernández del Río
On Mon, Mar 4, 2013 at 2:29 PM, Todd wrote: > > 5. Currently dtypes are limited to a set of fixed types, or combinations > of these types. You can't have, say, a 48 bit float or a 1-bit bool. This > project would be to allow users to create entirely new, non-standard dtypes > based on simple ru

Re: [Numpy-discussion] GSOC 2013

2013-03-04 Thread Todd
On Mon, Mar 4, 2013 at 9:41 PM, Ralf Gommers wrote: > > > > On Tue, Feb 26, 2013 at 11:17 AM, Todd wrote: > >> Is numpy planning to participate in GSOC this year, either on their own >> or as a part of another group? >> > > If we participate, it should be under the PSF organization. I suspect >

Re: [Numpy-discussion] GSOC 2013

2013-03-04 Thread Ralf Gommers
On Tue, Feb 26, 2013 at 11:17 AM, Todd wrote: > Is numpy planning to participate in GSOC this year, either on their own or > as a part of another group? > If we participate, it should be under the PSF organization. I suspect participation for NumPy (and SciPy) largely depends on mentors being av

[Numpy-discussion] GSOC 2013

2013-02-26 Thread Todd
Is numpy planning to participate in GSOC this year, either on their own or as a part of another group? If so, should we start trying to get some project suggestions together? ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.