Using the command line setting -gw which should turn off all warnings don't
affect the warnings about isosurface max_gradient settings.

Beta 12, Win 98.

// command line settings:
// -gw

// warning about max gradient can't be turned off!
light_source {<0,1,-1>*100,rgb 1}
isosurface {
   function {sqrt(x*x+y*y+z*z)-1}
   accuracy 0.02
   max_gradient 6
   contained_by {box {-1,1}}
   translate 3*z
   pigment {rgb 1}
}

// warning about no pigment.
// warning about camera being inside non-hollow object.
// these can be turned off fine.
sphere {0, 10}

Rune
--
3D images and anims, include files, tutorials and more:
Rune's World:    http://rsj.mobilixnet.dk (updated Feb 16)
POV-Ray Users:   http://rsj.mobilixnet.dk/povrayusers/
POV-Ray Webring: http://webring.povray.co.uk

Post a reply to this message

In article <3c8a1241@news.povray.org> , "Rune" <run### [at] mobilixnetdk>
wrote:

> Using the command line setting -gw which should turn off all warnings don't
> affect the warnings about isosurface max_gradient settings.

A) -gw is the incorrect switch to "turn off all warnings".  it turns off the
warning stream, which is no the same.  The correct switch to turn off all
warnings -wl0 .

B) Does the described problem when using -gw occur with a regular end of
rendering, a stpped rendering and/or a rendering terminated by some error?

C) Do these warnings get redirected to a file correctly when only redirecting
the warning stream?

    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

"Thorsten Froehlich" skrev:
> -gw is the incorrect switch to "turn off all warnings".
> it turns off the warning stream, which is no the same.

Very confusing and not at all clear from the documentation. Which warnings
are not part of the warning stream, and which streams do they belong to
then?

> Does the described problem when using -gw occur with
> a regular end of rendering

yes.

> a stopped rendering

no.

> a rendering terminated by some error?

no.

> Do these warnings get redirected to a file correctly
> when only redirecting the warning stream?

I can't say, as I don't know what the desired behavior is or how it's
supposed to be used. I may understand it if you answer the questions at the
top of this message.

Rune
--
3D images and anims, include files, tutorials and more:
Rune's World:    http://rsj.mobilixnet.dk (updated Feb 16)
POV-Ray Users:   http://rsj.mobilixnet.dk/povrayusers/
POV-Ray Webring: http://webring.povray.co.uk

Post a reply to this message

In article <3c8a2c48$1@news.povray.org> , "Rune" <run### [at] mobilixnetdk>
wrote:

> Very confusing and not at all clear from the documentation. Which warnings
> are not part of the warning stream, and which streams do they belong to
> then?

Warnings are warnings.  There is not some "magic" that decides something that
looks like a warning is a warning and another thing that looks like one is
not.  All warnings are created equal! :-)

However, turning off the warning stream still generates those warnings, they
are just not displayed because you turn the stream display off.  That is the
very nature of stream output on screen if it is off.  Setting the warning
level turns of generating of those warnings and consequently they are not in
the stream.

This works similar to the verbose display.  If you turn the verbose option on,
you get more messages in the streams.  Of course, if you direct those streams
to nowhere you won't see the messages anymore, but verbose is still turned on.
Thus you would turn the verbose option off to get rid of the messages and not
redirect it to nowhere.

Got it?

>> Do these warnings get redirected to a file correctly
>> when only redirecting the warning stream?
>
> I can't say,

All I asked is if you direct to a warning stream, if those warnings are in
there or not.  Just redirecting the stream to a file, then opening the file
and searching for them is sufficient to tell if they are in the file or not.

> as I don't know what the desired behavior is or how it's
> supposed to be used. I may understand it if you answer the questions at the
> top of this message.

I did not ask what you think the desired behavior would/should be - I think
you completely misunderstood this question :-(

    Thorsten

____________________________________________________
Thorsten Froehlich
e-mail: mac### [at] povrayorg

I am a member of the POV-Ray Team.
Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message

"Thorsten Froehlich" wrote:
> Warnings are warnings.

> However, turning off the warning stream still
> generates those warnings, they are just not
> displayed because you turn the stream display off.

> Got it?

I think so.

So it's indeed a bug that the max_gradient warning is displayed even
though -gw is used, if I understand correctly.

Anyway, a little testing shows that the max_gradient warning currently is
not part of the warning stream, but rather part of the fatal stream. +gf
and -gf can be used to turn the display of it on and off respectively. It's
the same when outputting to a file. +gwstream.txt doesn't write the
max_gradient to the file but +gfstream.txt does.

Hope that's what you needed to know.

Rune
--
3D images and anims, include files, tutorials and more:
Rune's World:    http://rsj.mobilixnet.dk (updated Feb 16)
POV-Ray Users:   http://rsj.mobilixnet.dk/povrayusers/
POV-Ray Webring: http://webring.povray.co.uk

Post a reply to this message

In article <3c8a6699@news.povray.org> , "Rune" <run### [at] mobilixnetdk>
wrote:

> So it's indeed a bug that the max_gradient warning is displayed even
> though -gw is used, if I understand correctly.

Exactly!

> Anyway, a little testing shows that the max_gradient warning currently is
> not part of the warning stream, but rather part of the fatal stream. +gf
> and -gf can be used to turn the display of it on and off respectively. It's
> the same when outputting to a file. +gwstream.txt doesn't write the
> max_gradient to the file but +gfstream.txt does.
>
> Hope that's what you needed to know.

Yes, and with the info about the fatal stream it was easy for me to locate and
fix this bug!  Thanks!

    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