Compiled on linux (revision #5066),
./configure COMPILED_BY="###" --disable-io-restrictions

the command: povray --benchmark

is failing:
Failed to parse INI file


povray --version
================
povray: this pre-release version of POV-Ray for Unix expires in 27 
day(s) and 5 hour(s)
POV-Ray 3.7.0.beta.38

This is a time-limited beta test version which expires 31 Dec 2010.
General distribution is strongly discouraged.

Copyright 1991-2003 Persistence of Vision Team
Copyright 2003-2010 Persistence of Vision Raytracer Pty. Ltd.

Built-in features:
   I/O restrictions:          disabled
   X Window display:          enabled (using SDL)
   Supported image formats:   gif tga iff ppm pgm hdr png jpeg tiff openexr
   Unsupported image formats: -

Compilation settings:
   Build architecture:  x86_64-unknown-linux-gnu
   Built/Optimized for: x86_64-unknown-linux-gnu (using -march=native)
   Compiler vendor:     gnu
   Compiler version:    g++ 4.4.3
   Compiler flags:      -pipe -Wno-multichar -Wno-write-strings 
-fno-enforce-eh-specs -s -O3 -ffast-math -march=native -pthread

Post a reply to this message

Le_Forgeron <jgr### [at] freefr> wrote:
> Compiled on linux (revision #5066),

> povray --version
> ================
> povray: this pre-release version of POV-Ray for Unix expires in 27
> day(s) and 5 hour(s)
> POV-Ray 3.7.0.beta.38

Hi,
Can you share the secret as to the location of the Linux Beta 38 source?
http://www.povray.org/beta/source/ still only lists beta.35a.
Cheers,
Peter

Post a reply to this message

Am 05.07.2010 23:41, schrieb geep999:

> Can you share the secret as to the location of the Linux Beta 38 source?
> http://www.povray.org/beta/source/ still only lists beta.35a.

His secret is that he has access to the POV-Ray code repository.

Post a reply to this message

Le 04/07/2010 18:31, Le_Forgeron nous fit lire :
> Compiled on linux (revision #5066),
> ./configure COMPILED_BY="###" --disable-io-restrictions
>
> the command: povray --benchmark
>
> is failing:
> Failed to parse INI file
>

Issue seems to be related to
Output_File_Type=s

Removing the line from the generated pov*.ini allows to manually run it.

A shame the error message does not display the offending line. (I had to 
make a printf in source/base/processoptions.cpp / 
ProcessOptions::Parse_INI_Option to get at least the last parsed key )

After further code analysis, it looks like only windows get a 
SYS_TO_STANDARD defined to BMP (in vfe/win/syspovconfig.h) .
(ok, no mac code, only win or unix)
Traditional Unix got png as "s", has it been changed ?

Post a reply to this message

On 07/05/2010 08:33 PM, Le_Forgeron wrote:
> Le 04/07/2010 18:31, Le_Forgeron nous fit lire :
>> Compiled on linux (revision #5066),
>> ./configure COMPILED_BY="###" --disable-io-restrictions
>>
>> the command: povray --benchmark
>>
>> is failing:
>> Failed to parse INI file

yep ... i get the error as well

>>
> 
> Issue seems to be related to
> Output_File_Type=s
> 
> Removing the line from the generated pov*.ini allows to manually run it.
> 
> A shame the error message does not display the offending line. (I had to
> make a printf in source/base/processoptions.cpp /
> ProcessOptions::Parse_INI_Option to get at least the last parsed key )
> 
> After further code analysis, it looks like only windows get a
> SYS_TO_STANDARD defined to BMP (in vfe/win/syspovconfig.h) .
> (ok, no mac code, only win or unix)
> Traditional Unix got png as "s", has it been changed ?

I had +fn in my ini file (left over from when i was on windows) ...
removing it I get png file so I'd say ... no hasn't changed.

Jim

Post a reply to this message

Am 06.07.2010 01:56, schrieb Jim Holsenback:

>> After further code analysis, it looks like only windows get a
>> SYS_TO_STANDARD defined to BMP (in vfe/win/syspovconfig.h) .
>> (ok, no mac code, only win or unix)

Thanks guys for the analysis so far.

>> Traditional Unix got png as "s", has it been changed ?
>
> I had +fn in my ini file (left over from when i was on windows) ...
> removing it I get png file so I'd say ... no hasn't changed.

These are two different things: Removing the "+fn" option gives you the 
/default/, which happens to have been changed to PNG for all versions 
recently. The "s" file type, on the other hand, is a /system specific/ 
type. (I guess its importance has diminished a lot though, so if it 
wasn't for backward compatibility I'd say let's throw it out altogether.)

It's strange that the benchmark .ini file specifies an output file type 
at all, given that it should disable file output anyway.

Post a reply to this message

On 07/07/2010 05:01 AM, clipka wrote:
> 
> These are two different things: Removing the "+fn" option gives you the
> /default/, which happens to have been changed to PNG for all versions
> recently. The "s" file type, on the other hand, is a /system specific/
> type. (I guess its importance has diminished a lot though, so if it
> wasn't for backward compatibility I'd say let's throw it out altogether.)

Oh-key-doe-key ... then riddle me this batman ;-)

I have this is unix specific documentation (3.5):

1.3.3.3 Output file formats
The default output file format of POV-Ray for Unix is PNG (+fn). This
can be changed at runtime by setting the Output_File_Type or +fx option.
Eventually, the default format can be changed at compile time by setting
DEFAULT_FILE_FORMAT in the config.h file located in the unix/ directory.

This seems to be saying that png was already default for unix!

The closest I can find in the source is:
~smp/vfe/unix/syspovconfig.h:#define DEFAULT_OUTPUT_FORMAT
kPOVList_FileType_PNG

Is that what the above (1.3.3.3) passage is eluding to?

Lastly ... what is the sys specific format (or type "s") for unix? I
can't find SYS_TO_STANDARD anywhere but what was mentioned in previous
thread in this post. Reference section on Output File Type hints at type
"s" on win/mac (bmp/pict) ... but not for unix. Perhaps I'm chasing
something that simply needs to be downplayed as "legacy" and retained
for backward compatibility reasons, since the default output file type
across all platforms is now png.

Jim

Post a reply to this message

It looks like "Output_File_Type=s" is hardcoded in unix's benchmark.cpp, ie:

# diff -u source/backend/control/benchmark.cpp{.orig,}
--- source/backend/control/benchmark.cpp.orig   2010-08-30 16:20:20.000000000
-0700
+++ source/backend/control/benchmark.cpp        2010-08-30 18:02:55.000000000
-0700
@@ -1305,7 +1305,7 @@
   "Odd_Field=Off\n"
   "Output_Alpha=Off\n"
   "Output_File_Name=\n"
-  "Output_File_Type=s\n"
+  "Output_File_Type=n\n"
   "Output_To_File=Off\n"
   "Palette=3\n"
   "Pause_When_Done=Off\n"


This allows to run the benchmark, although I'm not sure how relevant are the
results. The benchmarking code is different in 3.7.0.beta.38 between windows and
linux, windows producing more statistics including PPS (ie PrintRenderTimes in
windows/pvengine.cpp).

Are there any plans to match the benchmarking code between windows and linux ?

Post a reply to this message

On 08/30/2010 10:32 PM, Alec Istomin wrote:
> Are there any plans to match the benchmarking code between windows and linux ?
>

I've already changed the output file type to "n" with the built-in
version (cross platform) and it's on my to do list to synchronize the
scene file and the built-in versions ... oh yeah for consistency I also
changed the output file type in benchmark.ini (scene file version) as
well ... those changes should flow with the next beta release.

Post a reply to this message

Jim Holsenback <jho### [at] povrayorg> wrote:
> On 08/30/2010 10:32 PM, Alec Istomin wrote:
> > Are there any plans to match the benchmarking code between windows and linux ?
> >
>
> I've already changed the output file type to "n" with the built-in
> version (cross platform) and it's on my to do list to synchronize the
> scene file and the built-in versions ... oh yeah for consistency I also
> changed the output file type in benchmark.ini (scene file version) as
> well ... those changes should flow with the next beta release.

Thank you Jim, will be looking forward for a new beta!

Post a reply to this message