accuracy problem in calculation
invalid at invalid.invalid
Thu Nov 8 19:17:48 CET 2012
On 2012-11-08, Chris Angelico <rosuav at gmail.com> wrote:
> On Fri, Nov 9, 2012 at 4:05 AM, Debashish Saha <silideba at gmail.com> wrote:
>> Out: 2.384185791015625e-07
>> Out: 7.000000001866624e-08
>> above i am showing the two different results,though the two outputs
>> should be same if we do it in copy (the lass one is acceptable value).
Then do it the way you did the last one.
Seriously, that's the answer they teach you in numerical analysis
>> so my question is how to increase the accuracy(windows7(32bit)
> Welcome to floating point. You're working with very large and very
> small numbers, and you _will_ lose accuracy.
> There are a few options. It's possible that a 64-bit build of Python
> will give you more accuracy,
Pretty doubtful. 64-bit and 32-bit builds on all common OSes and
hardware are both going to use 64-bit IEEE floating point.
> but better would be to separate your huge numbers from your tiny ones
> and work with them separately.
> Alternatively, switch to the Decimal or Fraction types, but be aware
> that your script will probably run a lot slower.
Or admit to yourself that the measurements that produce your input
data just aren't that accurate anyway and forget about it. :)
Grant Edwards grant.b.edwards Yow! Bo Derek ruined
at my life!
More information about the Python-list