 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Tue, 11 Jan 2000 15:56:40 -0500, Jim Kress wrote:
>You could also use Paint Shop Pro to do a difference on the two scenes (the
>master and the test) and inspect the result.
True, but my method can be automated with a Perl script.
--
These are my opinions. I do NOT speak for the POV-Team.
The superpatch: http://www2.fwi.com/~parkerr/superpatch/
My other stuff: http://www2.fwi.com/~parkerr/traces.html
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Ron Parker wrote:
>
> On Mon, 10 Jan 2000 22:25:48 -0600, Mark Gordon wrote:
> >There are two ways I do this: rendering a bunch of stuff with low
> >resolution just to see whether it works (I've known the render to fail,
> >and I've known the render to hang). Running allscene.sh on my machine
> >typically takes around 25 minutes. Other methods involve rendering at
> >larger resolution (over a period of days) and visually eyeballing for
> >unusual artifacts. I've seen all the scenes in the standard
> >distribution enough to have some idea if something goes completely
> >screwy, and I also have "canonical" high-resolution versions saved on my
> >hard drive. The MegaPov example scenes are not so familiar.
>
> The reason I asked is because it's something I've thought about myself.
> I think it should be relatively easy to work out an automated solution
> for the cases where there aren't any failures:
>
> Use pnminvert to invert the canonical copy of the image, then use ppmmix
> to mix 50% of it with 50% of the test image. Finally, run ppmhist on
> the result and examine its output to see how many pixels are significantly
> different from solid 50% gray. If it's over a certain threshold, you can
> guarantee there's been a significant change in how the image was rendered.
>
> Adjusting the threshold and the definition of "significantly different from
> solid 50% gray" allows you to detect smaller and smaller differences in
> rendering, up to and including perfect reproduction of the original image.
> So you can sort the images into categories: "really different - probably a bug",
> "A little different", and "perfect".
I had been picturing something similar (though I was going to use the
GIMP), but I haven't gotten around to it yet.
-Mark Gordon
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I'll see your Perl script and raise you one Fortran program ...
Jim
--
Ron Parker <ron### [at] povray org> wrote in message
news:387b9d45@news.povray.org...
> On Tue, 11 Jan 2000 15:56:40 -0500, Jim Kress wrote:
> >You could also use Paint Shop Pro to do a difference on the two scenes
(the
> >master and the test) and inspect the result.
>
> True, but my method can be automated with a Perl script.
>
> --
> These are my opinions. I do NOT speak for the POV-Team.
> The superpatch: http://www2.fwi.com/~parkerr/superpatch/
> My other stuff: http://www2.fwi.com/~parkerr/traces.html
>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Wed, 12 Jan 2000 00:39:59 -0500, Jim Kress wrote:
>I'll see your Perl script and raise you one Fortran program ...
Guess I'll have to pull out my big guns, then: netpbm is free,
PSP isn't.
--
These are my opinions. I do NOT speak for the POV-Team.
The superpatch: http://www2.fwi.com/~parkerr/superpatch/
My other stuff: http://www2.fwi.com/~parkerr/traces.html
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Hy,
just a note on the measurement, how about md5 checksums?
They can be distributed easily, so that several people can do the check.
At times I looked into configure;make;... I thought about adding an
essential part of allscene.sh to the test target, then make -j could
parallize such tests.
Axel
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Wed, 12 Jan 2000 19:01:50 +0100, Axel Hecht wrote:
>Hy,
>just a note on the measurement, how about md5 checksums?
>They can be distributed easily, so that several people can do the check.
>At times I looked into configure;make;... I thought about adding an
>essential part of allscene.sh to the test target, then make -j could
>parallize such tests.
checksums would be fine if the only intent was to insure that the image
was exactly identical, but I'm not sure that there aren't some changes
that would result in slightly different but acceptable and/or desirable
results.
--
These are my opinions. I do NOT speak for the POV-Team.
The superpatch: http://www2.fwi.com/~parkerr/superpatch/
My other stuff: http://www2.fwi.com/~parkerr/traces.html
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I yield to the superior economic argument ...
:>)
Jim
--
Ron Parker <ron### [at] povrayorg> wrote in message
news:387c7aff@news.povray.org...
> On Wed, 12 Jan 2000 00:39:59 -0500, Jim Kress wrote:
> >I'll see your Perl script and raise you one Fortran program ...
>
> Guess I'll have to pull out my big guns, then: netpbm is free,
> PSP isn't.
>
> --
> These are my opinions. I do NOT speak for the POV-Team.
> The superpatch: http://www2.fwi.com/~parkerr/superpatch/
> My other stuff: http://www2.fwi.com/~parkerr/traces.html
Post a reply to this message
|
|
| |
| |
|
|
From: Mark Wagner
Subject: Re: Regression tests for POV development
Date: 13 Jan 2000 00:31:27
Message: <387d632f@news.povray.org>
|
|
|
| |
| |
|
|
Axel Hecht wrote in message <387CC18E.B65B1D8F@numerik.uni-kiel.de>...
>Hy,
>just a note on the measurement, how about md5 checksums?
>They can be distributed easily, so that several people can do the check.
>At times I looked into configure;make;... I thought about adding an
>essential part of allscene.sh to the test target, then make -j could
>parallize such tests.
This won't work if the image is testing "crand" finishes or jittered
antialiasing. Both these features are random and cannot be exactly
duplicated from one image to the next.
Mark
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
