POV-Ray : Newsgroups : povray.unofficial.patches : megapov 0.7: all determinants too small Server Time
5 Jul 2024 13:11:29 EDT (-0400)
  megapov 0.7: all determinants too small (Message 1 to 3 of 3)  
From: Lothar Esser
Subject: megapov 0.7: all determinants too small
Date: 9 Oct 2001 23:03:23
Message: <3BC3BA6B.868E44DA@helix.nih.gov>
Hi,
   I have a question about an error message I get from megapov 0.7.
Rendering a very large mesh2 megapov apparently runs fine but once in a
while gives an error message:

all determinants too small

What does it mean and do I need to worry ?

I recently compiled megapov on Irix 6.5  and am running it on an Octane.

In addition to that it seems very slow. I don't know whether this is a
related error or whether mesh2 can get slow.
I have about 40000 triangles and for each vertex I define a texture (
but there not 120000 textures - just about 5 )

Thanks for any hints.

   Lothar

--
Dr. Lothar Esser
NIH / NCI
Tel. 301-435-6163
email les### [at] helixnihgov


Post a reply to this message

From: Nicolas Calimet
Subject: Re: megapov 0.7: all determinants too small
Date: 10 Oct 2001 13:42:58
Message: <3BC488A1.86F78915@free.fr>
Hi Lothar  ;o)

> all determinants too small

	As you mention later in your message, this is a problem related
to mesh2 and triangles that carry a texture at each vertex. This question
has been asked by Warp in this group [message of 2001-06-28] and I posted
an answer - a bit late actually.
	The code was designed for interpolating 3 colors between the corners
of a triangle, as written by A. Philippsen (you might know him: author of
the DINO software). Later, Nathan Kopp improved the code to get full texture
interpolation instead of colors only. But the code is rather not optimized,
and some times you have a small problems that give this message. This most
probably happen with "degenerate" triangles (part of them include triangles
that have 2 or 3 identical vertices). IMHO this message can thus be simply
ignored, it won't affect rendering.

> In addition to that it seems very slow. I don't know whether this is a
> related error or whether mesh2 can get slow.

	On my pov4grasp page I did extensive benchmarks using mesh2 and
interpolated-color-textures in mesh2 objects and did not notice particular
difference in speed (as compared to original mesh object + Chris Colefax's
macros, or my custom mesh object). I'm talking about rendering speed of
course, not parsing. See http://pov4grasp.free.fr/features/grasp_surface.php3

	For more discussions, don't hesitate to contact me by normal mail
(my adress at work is prefered).


*** Nicolas Calimet
*** http://pov4grasp.free.fr


Post a reply to this message

From: Lothar Esser
Subject: Re: megapov 0.7: all determinants too small
Date: 10 Oct 2001 14:38:06
Message: <3BC4957E.36DB9054@helix.nih.gov>
Hi,

   within the next five minutes I sent this mail off I checked the code and
found
the message in triangle.c. My guess was as you now confirmed that this is due to

an error in the triangle texture interpolation. However I could not create
manually
a situation that created this error. I have run an example with a triangle, that
worked
fine, then I made two vertices the same, still every thing okay ( no error
message ) but
of course no object was drawn, not even a line and finally I made all points the
same
:again no complaints. So I don't know what the problem actually is. But it seems
it
is save to ignore for the moment.

About my second question I found out that I suffered a tremendous performance
hit
when I use +MV3.0 switch ! Megapov is just 5-10 times slower ( rendering ). Does
any
one know why ? BTW povray 3.1 does not get slower at all - so it would seem.
( Not that is really important but puzzling if you are trying to use older style
code )
Thanks,
   Lothar


Nicolas Calimet wrote:

>         Hi Lothar  ;o)
>
> > all determinants too small
>
>         As you mention later in your message, this is a problem related
> to mesh2 and triangles that carry a texture at each vertex. This question
> has been asked by Warp in this group [message of 2001-06-28] and I posted
> an answer - a bit late actually.
>         The code was designed for interpolating 3 colors between the corners
> of a triangle, as written by A. Philippsen (you might know him: author of
> the DINO software). Later, Nathan Kopp improved the code to get full texture
> interpolation instead of colors only. But the code is rather not optimized,
> and some times you have a small problems that give this message. This most
> probably happen with "degenerate" triangles (part of them include triangles
> that have 2 or 3 identical vertices). IMHO this message can thus be simply
> ignored, it won't affect rendering.
>
> > In addition to that it seems very slow. I don't know whether this is a
> > related error or whether mesh2 can get slow.
>
>         On my pov4grasp page I did extensive benchmarks using mesh2 and
> interpolated-color-textures in mesh2 objects and did not notice particular
> difference in speed (as compared to original mesh object + Chris Colefax's
> macros, or my custom mesh object). I'm talking about rendering speed of
> course, not parsing. See http://pov4grasp.free.fr/features/grasp_surface.php3
>
>         For more discussions, don't hesitate to contact me by normal mail
> (my adress at work is prefered).
>
> *** Nicolas Calimet
> *** http://pov4grasp.free.fr

--
Dr. Lothar Esser
NIH / NCI
Tel. 301-435-6163
email les### [at] helixnihgov


Post a reply to this message

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