The Persistence of Vision Raytracer (POV-Ray).

This is the legacy Bug Tracking System for the POV-Ray project. Bugs listed here are being migrated to our github issue tracker. Please refer to that for new reports or updates to existing ones on this system.


FS#79 - Full-Featured Test-Scene to check the correctness of povray

Attached to Project: POV-Ray
Opened by Michael Lindig (lindig) - Thursday, 04 March 2010, 09:02 GMT
Last edited by William F Pokorny (wfpokorny) - Thursday, 19 January 2017, 14:42 GMT
Task Type Feature Request
Category Source code
Status Tracked on GitHub
Assigned To No-one
Operating System All
Severity Low
Priority Normal
Reported Version 3.70 beta 35a
Due in Version Future release
Due Date Undecided
Percent Complete 0%
Votes 0
Private No



it would be nice if there exists a test scene (not a benchmark) which has a high coverage of povray source and can be used as correctness validation of povray. It schould be produce an image which can be compared to a golden reference image.

It may be also possible to create a regression test suite which does automatic comparision of the render results.

This task depends upon

Comment by Grimbert Jérôme (Le_Forgeron) - Thursday, 11 March 2010, 21:44 GMT

Looks to me the "all image" & "all animation" scripts (as well as the portfolio) might cover the topic.

It's not a single image, and due to png compression (as well as changing features), it's not possible to automat the comparaison. (yet ?)

Using the right combination of imagemagick, it might be possible to check for a global "black" difference.

Moreover, povray never says that anti-aliasing was determinist amongst different computers
(and aliased pictures are just horrible to look, but might be good for non-regression checks)

Comment by Christoph Lipka (clipka) - Monday, 22 March 2010, 22:20 GMT

I'm already doing performance comparisons of the current 3.7 betas or my development versions against earlier betas as well as 3.6 (on a Linux machine), using a suite of ~151 images at present, and also occasionally check the output images; while I initially did that manually using BeyondCompare, I have by now written a small command line program to read in two PNG images, compare them, output two images showing (a) a (contrast-boosted) difference image and (b) a greyscale version with differences highlighted, and ultimately returning an exit code identifying how severe the differences are (according to some rather simple heuristics). If someone is interested, I might publish the code for that tool in one of the newsgroups.

Comment by Simon (infoised) - Sunday, 24 February 2013, 17:37 GMT

imagemagick suite comes with "compare" tool that does exaclty this. It also generates a lot of different measures of difference between images, which gives you numbers to compare.

Comment by William F Pokorny (wfpokorny) - Thursday, 19 January 2017, 14:42 GMT
  • Field changed: Status (New → Tracked on GitHub)

Now tracked on github as issue #192.