POV-Ray : Newsgroups : povray.beta-test : Clock precision wrong? : Re: Clock precision wrong? Server Time
1 Jun 2024 21:51:58 EDT (-0400)
  Re: Clock precision wrong?  
From: ErOssel
Date: 25 Jun 2011 18:10:01
Message: <web.4e065ad595481d03d091e86b0@news.povray.org>
Thorsten Froehlich <tho### [at] trfde> wrote:
> On 25.06.11 22:25, ErOssel wrote:
> > Hi folks,
> >
> > I noticed a not correct value for clock in animation.
> >
> > Test with version 3.7.0.RC3.msvc9.win64 running on Windows 7 (64bit).
> <snip>
> > Result: frame_number:   21 clock:  0.666666687 g_Clock:  0.666666667
> > There is a difference of 0.66666662
>
> I guess you meant that the difference is 0.00000002, which is perfectly
> normal for floating point numbers. The difference will vary depending on how
> well a number can be represented, hence you will see slightly different
> precision errors for different values.
>
> This precision limit is normal and not a problem in POV-Ray.
>
>  Thorsten
Hi Thorsten,

Yes, you're right, it should be with zero's.
I am not afraid that the result of calculation will be wrong, but with 3.6 is
goes as expected.
My animation is printing clock*48 with 2880 frames and on frame 2570 the
difference is already within 6 decimal digits.
frame_number: 2570 clock*48: 42.816668 g_Clock*48: 42.816667
Doing it by storing clock in a variable is okay for me.

I just do not understand the difference using the inbuilt float clock and an
user variable. And confused with the change between 3.6 and 3.7!

Anyway, thanks for your reaction.

Regards, ErO


Post a reply to this message

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.