Chambers <ben### [at] pacificwebguycom> wrote:
> Warp wrote:
> > Chambers <ben### [at] pacificwebguycom> wrote:
> >> Warp wrote:
> >>> Chambers <ben### [at] pacificwebguycom> wrote:
> >>>> You're dealing with two numbers, one of them being approximately 20 
> >>>> million times the other.  It's a known aspect of the hardware we use 
> >>>> that you should keep your ratios smaller than this to avoid precision 
> >>>> errors.
> >>>   Where exactly are you getting that number?
> > 
> >> Location of 1M, radius of 0.05.
> > 
> >   You didn't really answer my question.
> > 

> OK Warp, then 1M / 0.05 = 20M.  So the one number is 20M times the other.

  You are not understanding.

  You said, and I quote: "It's a known aspect of the hardware we use
that you should keep your ratios smaller than this to avoid precision
errors."
  I didn't know that the ratio between double precision floating point
numbers must be smaller than 20 millions in order to preserve accuracy.
I asked where did you get that number.

  The limit hit by the original poster has nothing to do with double
precision floating point number accuracy.

-- 
                                                          - Warp

Post a reply to this message