On Thu, Apr 22, 2010 at 12:04 PM, Adrien Guillon wrote:
>
> The idea here, is that if I can ensure there is never extended
> precision in the Python code...
This is totally out of reach with numpy is you use the float32 dtype,
for the reasons I have given before. The only solutions I could see
a
Adrien Guillon wrote:
> Thank you for your questions... I'll answer them now.
>
> The motivation behind using Python and NumPy is to be able to "double
> check" that the numerical algorithms work okay in an
> engineer/scientist friendly language. We're basically prototyping a
> bunch of algorithms
On 04/21/2010 09:47 AM, Adrien Guillon wrote:
> Hello all,
>
> I've recently started to use NumPy to prototype some numerical
> algorithms, which will eventually find their way to a GPU (where I
> want to limit myself to single-precision operations for performance
> reasons). I have recently switc
On 21 April 2010 23:04, Adrien Guillon wrote:
> Thank you for your questions... I'll answer them now.
>
> The motivation behind using Python and NumPy is to be able to "double
> check" that the numerical algorithms work okay in an
> engineer/scientist friendly language. We're basically prototypin
On Wed, Apr 21, 2010 at 9:04 PM, Adrien Guillon wrote:
> Thank you for your questions... I'll answer them now.
>
> The motivation behind using Python and NumPy is to be able to "double
> check" that the numerical algorithms work okay in an
> engineer/scientist friendly language. We're basically p
Thank you for your questions... I'll answer them now.
The motivation behind using Python and NumPy is to be able to "double
check" that the numerical algorithms work okay in an
engineer/scientist friendly language. We're basically prototyping a
bunch of algorithms in Python, validating that they
On 04/21/2010 11:47 PM, Adrien Guillon wrote:
> Hello all,
>
> I've recently started to use NumPy to prototype some numerical
> algorithms, which will eventually find their way to a GPU (where I
> want to limit myself to single-precision operations for performance
> reasons). I have recently switc
Adrien Guillon wrote:
> I use single-precision floating point operations.
>
> My understanding, however, is that Intel processors may use extended
> precision for some operations anyways unless this is explicitly
> disabled, which is done with gcc via the -ffloat-store operation.
IIUC, that forc
On 21 April 2010 11:03, Pauli Virtanen wrote:
> ke, 2010-04-21 kello 10:47 -0400, Adrien Guillon kirjoitti:
> [clip]
>> My understanding, however, is that Intel processors may use extended
>> precision for some operations anyways unless this is explicitly
>> disabled, which is done with gcc via th
On Wed, Apr 21, 2010 at 8:47 AM, Adrien Guillon wrote:
> Hello all,
>
> I've recently started to use NumPy to prototype some numerical
> algorithms, which will eventually find their way to a GPU (where I
> want to limit myself to single-precision operations for performance
> reasons). I have rece
ke, 2010-04-21 kello 10:47 -0400, Adrien Guillon kirjoitti:
[clip]
> My understanding, however, is that Intel processors may use extended
> precision for some operations anyways unless this is explicitly
> disabled, which is done with gcc via the -ffloat-store operation.
> Since I am prototyping al
Hello all,
I've recently started to use NumPy to prototype some numerical
algorithms, which will eventually find their way to a GPU (where I
want to limit myself to single-precision operations for performance
reasons). I have recently switched to the use of the "single" type in
NumPy to ensure I
12 matches
Mail list logo
