Hi again, I apologize, the mistake was entirely my own. Sqrt's do the
right thing
Adam
On Sat, Oct 17, 2009 at 12:17 PM, Adam Ginsburg
wrote:
> My code is actually wrong but I still have the problem I've
> identified that sqrt is leading to precision errors. Sorry abo
My code is actually wrong but I still have the problem I've
identified that sqrt is leading to precision errors. Sorry about the
earlier mistake.
Adam
On Sat, Oct 17, 2009 at 12:08 PM, Adam Ginsburg
wrote:
>
> sqrt(float64(1.034324523462345))
> # 1.0170174646791199
>
Hi folks,
I'm trying to write a ray-tracing code for which high precision is
required. I also "need" to use square roots. However, math.sqrt and
numpy.sqrt seem to only use single-precision floats. Is there a
simple way to make sqrt use higher precision? Alternately, am I
simply being obtuse
> In [85]: bi = (f.bolo_indices[np.newaxis,:]+
>
> ones([7751,1])).astype('int')
>
> In [86]: whc = (whscan[:,np.newaxis] + ones([1,107])).astype('int')
>
> In [87]: array2d[whc,bi] = temp2d
>
> I thought this had worked, but the values didn't seem to be going to the
> right places when I re-exami
