In article <3c576c79@news.povray.org> , "Mike Hough" <Ama### [at] aolcom> 
wrote:

> "As said, it is a precision issue.  It is irrelevant what 3.1 would output
> because it is a precision issue and thus it really doesn't matter if
> something changed or not.  Just get used to it."
>
> I don't know if it was an actual bug or not but it seemed to be written off
> without investigation.

Oh, come on.  First of all you are quoting from the second thread about this,
in the original thread several people had explained the problem in more detail
and the nature of floating-point precision and how to properly deal with it.
As I have no way in proving that there is no problem until the source code is
released, you either take my word for it or you don't.  If you really want to
use this fact to claim there is a problem and nobody cares, I find it rather
unreasonable :-(

Do you really think there is some code in there that says:
"add 0.00000000298023224 to clock to annoy users"?  ;-)

    Thorsten

____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde

Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message

Warp wrote:
<snip lots of stuff>

Great!  Now I'm drooling on my keyboard for 3.5

From reading the messages, I have decided to wait for 3.5.  If, after a
while, I learn and exploit everything in it, I'll check into the then
3.5 based Mega-Pov.  

But since there's still lot's of 3.1 aspects that I haven't figured out
how to use, it may take a while.

-- 
Tom A.
"No doubt many that post deserve to be flamed.  And many that are flamed
didn't deserve it.  Can you give them the latter?  Then don't be so
quick to deal out the former!" - not Gandalf.
Deja mail is gone.  Look for me at raugost at yahoo . com

Post a reply to this message

I always meant to ask; I keep hearing that in POV3.5 iso's, "&" means OR
and "|" means AND. How come?

-- 
signature{
  "Grey Knight" contact{ email "gre### [at] yahoocom" }
  site_of_week{ url "http://digilander.iol.it/jrgpov" }
}

Post a reply to this message

Thorsten Froehlich <tho### [at] trfde> wrote:
: Do you really think there is some code in there that says:
: "add 0.00000000298023224 to clock to annoy users"?  ;-)

  I was wondering if floats could *really* be that inaccurate. When I make
this with povray:

#debug concat(str(99/100,0,25), "\n")

what I get is:

0.9899999999999999911182158

(instead of 0.99). I though, "is this really possible?".
  Then I wanted to be sure and I made a small C program which does basically
the same thing:

#include "stdio.h"
int main()
{
    printf("%.25f\n", 99.0/100.0);
    return 0;
}

  This program prints, surprise surprise:

0.9899999999999999911182158

  So now I am convinced that there's no bug in povray.

  Of course, when making a scene file, one has to minimize the effects of
floating point inaccuracy.
  For example, don't do it this way:

#declare Ind = 0;
#declare Clock = 0;
#while(Ind <= 100)
  #debug concat("Clock: ", str(Clock,0,25), "\n")
  #declare Clock = Clock+1/100;
  #declare Ind = Ind+1;
#end

(The last number printed is 1.0000000000000006661338148.)
  Instead, do it this way:

#declare Ind = 0;
#while(Ind <= 100)
  #declare Clock = Ind/100;
  #debug concat("Clock: ", str(Clock,0,25), "\n")
  #declare Ind = Ind+1;
#end

(The last number printed is 1.0000000000000000000000000.)

  The reason for the second code being better than the first is left as
an exercise to the reader.

-- 
#macro M(A,N,D,L)plane{-z,-9pigment{mandel L*9translate N color_map{[0rgb x]
[1rgb 9]}scale<D,D*3D>*1e3}rotate y*A*8}#end M(-3<1.206434.28623>70,7)M(
-1<.7438.1795>1,20)M(1<.77595.13699>30,20)M(3<.75923.07145>80,99)// - Warp -

Post a reply to this message

Grey Knight <s16### [at] namtarqubacuk> wrote:
: I always meant to ask; I keep hearing that in POV3.5 iso's, "&" means OR
: and "|" means AND. How come?

  I haven't followed this thing quite closely, but AFAIK the meaning of '&'
and '|' was changed to logical operators "logical and" and "logical or"
(instead of being set theory operators "intersection" and "union", as they
are in megapov, I think).

-- 
#macro N(D)#if(D>99)cylinder{M()#local D=div(D,104);M().5,2pigment{rgb M()}}
N(D)#end#end#macro M()<mod(D,13)-6mod(div(D,13)8)-3,10>#end blob{
N(11117333955)N(4254934330)N(3900569407)N(7382340)N(3358)N(970)}//  - Warp -

Post a reply to this message

"Warp" <war### [at] tagpovrayorg> wrote in message news:3c580c79@news.povray.org...

<snip>

Just out of curiousity, why does this surprise you?

Also just out of curiosity, if you ask a robot do they say "but it does say
0.99"? Hmm...

Post a reply to this message

Tom Melly <tom### [at] tomandlucouk> wrote:
: Just out of curiousity, why does this surprise you?

  I knew that doubles are inaccurate, but it surprised me that they are *that*
inaccurate. The inaccuracy is "only" in the 18th decimal.

  On the other hand, 18 decimals starts to sound like the maximum number of
digits (when converted to decimal) that the base of a double can hold...

-- 
#macro M(A,N,D,L)plane{-z,-9pigment{mandel L*9translate N color_map{[0rgb x]
[1rgb 9]}scale<D,D*3D>*1e3}rotate y*A*8}#end M(-3<1.206434.28623>70,7)M(
-1<.7438.1795>1,20)M(1<.77595.13699>30,20)M(3<.75923.07145>80,99)// - Warp -

Post a reply to this message

"Ken" <tyl### [at] pacbellnet> wrote in message
news:3C576D9E.D6CEA9B8@pacbell.net...
>
>
> 25ct wrote:
>
> > In actual fact, It was a very confusing time for me as Megapov and
3.1 were
> > being talked about quite a lot in the forums, and as a result, I
now have
> > 3.1g, Megapov 0.7 and 3.5 beta10 installed.
>
> Is that all? I've got 1.0, 2.2, 3.01, 3.1, 3.5 and a half dozen or
more
> patched versions installed. :)
>

Why do I never see anyone mention 2.1? That's what I've still got
loaded, not 2.2 but all after and megapov 0.7, all DOS. Now I'm in
serious trouble <grin> coz I needed to get Winpov 3.1 for 1st time to
try Schmitt's recompile (Hey! I can use my box while Pov is working.
Thats a novelty!). So thought might as well get WinMega while I'm at
it. If I'm not careful, 3.5b will worm its way in soon.

Alf

Post a reply to this message

Wasn't it Zeger Knaepen who wrote:
>>   On the other hand there are things that can be done with 3.5 that can't
>> be done with megapov.
>like?

One neat little feature is spline functions. It's now possible to use a
spline to define a function, and then use that function, say, to specify
an isosurface without any of the mathematics that would otherwise be
involved.

-- 
Mike Williams
Gentleman of Leisure

Post a reply to this message

Wasn't it Zeger Knaepen who wrote:
>> : And again: I never used the include files bundled with POV-Ray.
>>   Because there wasn't anything interesting in them, until now.
>no, because I like to make everything myself.  Even when I add a lensflare, it's 
>with a
>customized version of Colefax' include file and using a custom lens effect.

Note, however, that there's been a slight tendency to move some of the
stuff out of the core code and into standard include files. A few things
that are features of the MegaPOV language are implemented in the 3.5
include files.

-- 
Mike Williams
Gentleman of Leisure

Post a reply to this message