On 2/10/25 10:12, kurtz le pirate wrote:
> With ./configure, the compilation goes well but I get this message at 
> the end:
> --------------------
> configure: WARNING: All program feature using the OpenEXR library are 
> disabled
> 
> 
> However, the OpenEXR package is (seems) installed. I don't know if I can 
> continue if I can continue with the rest of the installation.
> 

The missing support only matters if you need to read or write .exr 
images with your scenes.

In a terminal window what do you see with the commands:

   pkg-config --print-errors OpenEXR
     ()

   pkg-config --modversion OpenEXR
     (3.1.5)

   pkg-config --cflags OpenEXR
     (-I/usr/include/OpenEXR -pthread -I/usr/include/Imath)

   pkg-config --libs OpenEXR
     (-lOpenEXR-3_1 -lOpenEXRUtil-3_1 -lOpenEXRCore-3_1
       -lIex-3_1 -lIlmThread-3_1 -lImath-3_1)

What is within the ()s is what I see on my Ubuntu 24.04 machine.

Bill P.

Post a reply to this message

On 10/02/2025 16:45, William F Pokorny wrote:
> On 2/10/25 10:12, kurtz le pirate wrote:
>> With ./configure, the compilation goes well but I get this message at 
>> the end:
>> --------------------
>> configure: WARNING: All program feature using the OpenEXR library are 
>> disabled
>>
>>
>> However, the OpenEXR package is (seems) installed. I don't know if I 
>> can continue if I can continue with the rest of the installation.
>>
> 
> The missing support only matters if you need to read or write .exr 
> images with your scenes.

OK, it's not mandatory for the time being.
So I will continue.


> In a terminal window what do you see with the commands:
> 
>    pkg-config --print-errors OpenEXR
>      ()
> 
>    pkg-config --modversion OpenEXR
>      (3.1.5)
> 
>    pkg-config --cflags OpenEXR
>      (-I/usr/include/OpenEXR -pthread -I/usr/include/Imath)
> 
>    pkg-config --libs OpenEXR
>      (-lOpenEXR-3_1 -lOpenEXRUtil-3_1 -lOpenEXRCore-3_1
>        -lIex-3_1 -lIlmThread-3_1 -lImath-3_1)

Same answer for the four orders:

Package OpenEXR was not found in the pkg-config search path.
Perhaps you should add the directory containing `OpenEXR.pc'
to the PKG_CONFIG_PATH environment variable
Package 'OpenEXR', required by 'virtual:world', not found


> What is within the ()s is what I see on my Ubuntu 24.04 machine.

But, on my 22.04 the command : 'sudo apt-get install openexr' say :

Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
openexr is already the newest version (2.5.7-1). <<<<<<<<<<<<<<<
The following packages were automatically installed and are no longer 
required:
   libwpe-1.0-1 libwpebackend-fdo-1.0-1
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.



;)



-- 
kurtz le pirate
compagnie de la banquise

Post a reply to this message

On 2/10/25 10:31, Bald Eagle wrote:
> Maybe some text could be sent to standard output stating that before your make
> script exits?
> 

Maybe. Let me review the INSTALL.txt file and think about it.

FWIW. On your question, I added a file called yuqk_wrapper_script to the 
shipped documentation for the next release.

...

> While working on the glory feature that CR posted, it (re)occurred to me that
> having some sort of "flag" to jimmy function / color map behaviour would be a
> useful thing.
> 
> I need to absolutely exclude certain inputs to my texture / color_map, and with
> pov-ray's value-wrapping, and real-valued function results, I find myself
> spending a lot of time trying to do clever things to use values to signify that
> I want to do things "off to the side" of what the main function is doing.
> Because I'm stuck using a mathematical function, not a macro or algorithm -
> which some languages refer to as "functions".
> 
> What I'm wondering is if there's a (future) way to set the result of a function
> like select () to NAN, i, or some other "orthogonal placeholder" that a
> color_map would just "ignore" and maybe set to something like rgbft1.

Interesting ideas as far as I understand what you want to do.

The yuqk fork's pattern value wrapping is somewhat different / extended 
compared to POV-Ray - including some internal changes on the internal 
function / pattern map interface.

We have some ability to 'jimmy map behavior' today in v3.8, but I think 
not quite what you are after.

I'll mention with function{}s you can hard code certain values. It's a 
feature I use to test maps. Rather than:

   function { Fn(...) }

code:

   function { 1/3 }

to see how a map behaves at that value. You can also use select to shift 
certain values which would normally fall within the defined map range, 
but I don't think you're asking for that.

There is too the ability to define the map indexes with functions. I 
suppose you could switch between maps that way. It would be a variation 
on code like:

#include "cfunctions.inc"
#declare Fn01 = function { pigment {
     image_map { "average_00_.jpg" ii_interpolate 2 }
     warp { repeat x flip x }
     warp { repeat y flip y }
     }
}
#declare R = 2;
#declare I = -2/4;
#declare EXP = cf_cmplx(R,I);
#declare PigMap = pigment_map {
     average // This necessary and enabled in yuqk fork
     [function { Fn01(cf_real(cf_pow(cf_cmplx(x,y),EXP)),
                      cf_imag(cf_pow(cf_cmplx(x,y),EXP)),0).red }
      color_map { [0 red 0] [1 red 3] }
     ]
     [function { Fn01(cf_real(cf_pow(cf_cmplx(x,y),EXP)),
                      cf_imag(cf_pow(cf_cmplx(x,y),EXP)),0).green }
      color_map { [0 green 0] [1 green 3] }
     ]
     [function { Fn01(cf_real(cf_pow(cf_cmplx(x,y),EXP)),
                      cf_imag(cf_pow(cf_cmplx(x,y),EXP)),0).blue }
      color_map { [0 blue 0] [1 blue 3] }
     ]
}
#declare Pig00 = pigment {
     average
     pigment_map { PigMap}
}

Bill P.

Aside : An idea / question I've had sitting in my head for some years is 
related to spectral rendering. One of the things spectral rendering 
works around is the color calculation biases within POV-Ray. In other 
words, I believe part of the better looking 'spectral result' comes from 
countering / balancing these calculation biases. I just don't know how 
big that 'due-calculation' portion of the result is.

What I'd like to try are ini / flag options which let the user 'rotate' 
a scene's color space. The resulting images would be normalized and 
combined for the final result a little like the current spectral rig. 
Someday, maybe... :-)

Post a reply to this message

On 2/10/25 11:35, kurtz le pirate wrote:
> But, on my 22.04 the command : 'sudo apt-get install openexr' say :

I believe the package you need is: libopenexr-dev

Bill P.

Post a reply to this message

On 10/02/2025 17:44, William F Pokorny wrote:
> On 2/10/25 11:35, kurtz le pirate wrote:
>> But, on my 22.04 the command : 'sudo apt-get install openexr' say :
> 
> I believe the package you need is: libopenexr-dev
> 
> Bill P.

Finally, it's getting better. I had to make mistakes as always.

I redid these steps;
- ldconfig
- reboot
- ./configure
- make
- make check
- make install


I did see the little window with the "cookies".





For the moment, the executable is still in
"/tmp/yuqk_a5c25dda/bin"



------------------------
./povray --version say :

povray: cannot open the user configuration file:
/home/louis/.povray/3.8/povray.conf: No such file or directory
Persistence of Vision(tm) Ray Tracer    (see --license)
Copyright 1991-2025 Persistence of Vision Raytracer Pty. Ltd.
POV-Ray (yuqk) 3.8.0-x.yuqk_a5c25dda.unofficial
This is an unofficial version compiled by: louis

Built-in features:
   Supported image formats:   gif tga iff ppm pgm hdr png jpeg tiff openexr
   Unsupported image formats: -

Compilation settings:
   Build architecture:  x86_64-pc-linux-gnu
   Built/Optimized for: x86_64-pc-linux-gnu
   Compiler vendor:     gnu
   Compiler version:    g++ 11.4.0
   Compiler flags:
     -pipe -w -fno-enforce-eh-specs -O2 -pthread


--------------------------
./povray --libraries say :

povray: cannot open the user configuration file:
/home/louis/.povray/3.8/povray.conf: No such file or directory

Boost 1.74, http://www.boost.org/

libjpeg 8.0, Copyright (C) 1991-1998, Thomas G. Lane.
Modified 2002-2009 by Guido Vollbeding.

OpenEXR 2.5.7 and IlmBase 2.5.7,
Copyright (c) 2002-2011 Industrial Light & Magic.

libpng version 1.6.37
Copyright (c) 2018-2019 Cosmin Truta
Copyright (c) 1998-2002,2004,2006-2018 Glenn Randers-Pehrson
Copyright (c) 1996-1997 Andreas Dilger
Copyright (c) 1995-1996 Guy Eric Schalnat, Group 42, Inc.

LIBTIFF, Version 4.3.0
Copyright (c) 1988-1996 Sam Leffler
Copyright (c) 1991-1996 Silicon Graphics, Inc.

zlib 1.2.11, Copyright (C) 1995-2017 Jean-loup Gailly and Mark Adler




The hard part is over. I don't have time now. I'll continue later :) :)

ps : I took notes and orders throughout the installation. I'll format 
them and give them away if they help other mad people. LOL !!




-- 
kurtz le pirate
compagnie de la banquise

Post a reply to this message

William F Pokorny <ano### [at] anonymousorg> wrote:

> > What I'm wondering is if there's a (future) way to set the result of a function
> > like select () to NAN, i, or some other "orthogonal placeholder" that a
> > color_map would just "ignore" and maybe set to something like rgbft1.
>
> Interesting ideas as far as I understand what you want to do.
>
> The yuqk fork's pattern value wrapping is somewhat different / extended
> compared to POV-Ray - including some internal changes on the internal
> function / pattern map interface.
>
> We have some ability to 'jimmy map behavior' today in v3.8, but I think
> not quite what you are after.

So, I just tested NAN and inf out of curiosity, and it seems they both default
to zero in the color_map.

Bummer.  I suppose that's better than the render failing.

Post a reply to this message

Attachments:
Download 'color_map experiments.png' (24 KB)

Preview of image 'color_map experiments.png'

On 2/10/25 18:59, Bald Eagle wrote:
> So, I just tested NAN and inf out of curiosity, and it seems they both default
> to zero in the color_map.

It should be the +-inf values work - so long as you use yuqk's raw_wave 
value pattern modifier (it's actually a pattern-value modifier bypass).

See attached scene file.

Bill P.

Post a reply to this message

Attachments:
Download 'bw_nan_inf.pov.txt' (2 KB)

On 10/02/2025 19:25, kurtz le pirate wrote:
> 
> The hard part is over. I don't have time now. I'll continue later :) :)
> 


A little bit hs, sorry.

The program works. I have created a folder "yuqk_a5c25dda" in my $HOME 
folder. Files ares :


louis@Jammy:~/yuqk_a5c25dda$ tree
.
├── bin
│   └── povray
├── etc
│   └── povray
│       └── 3.8
│           ├── povray.conf
│           └── povray.ini
└── share
     ├── doc
     │   └── povray-3.8
     │       ├── html
     │       └── NowShippedAsSeparate_DocAndAid_tarball
     ├── man
     │   └── man1
     │       └── povray_yuqk.1
     └── povray-3.8
         ├── icons
         ├── include
         │   ├── arraycoupleddf3s.inc
         │   ├── arrays.inc
         │   ├── arraystatistics.inc
         │   ├── cfunctions.inc
         │   ├── crystal.ttf
         │   ├── cyrvetic.ttf
         │   ├── forkversion.inc
         │   ├── functions.inc
         │   ├── math.inc
         │   ├── munctions.inc
         │   ├── povlogo.ttf
         │   ├── rand.inc
         │   ├── setidtypes.inc
         │   ├── shapes.inc
         │   ├── strings.inc
         │   ├── timrom.ttf
         │   ├── transforms.inc
         │   ├── ttffonts.cat
         │   ├── vectoranalysis.inc
         │   ├── vectors.inc
         │   └── version.inc
         ├── ini
         │   └── povray.ini
         ├── scenes
         │   ├── biscuit.pov
         │   ├── fog
         │   │   ├── Bridge.inc
         │   │   └── fog.pov
         │   └── rtr_kla.pov
         └── scripts
             ├── render_anim.sh
             ├── render_scene.sh
             ├── rerunpov.sh
             └── runpov.sh


I add "~/yuqk_a5c25dda/bin:" in the PATH variable.



Asking the version for povray, i get :

povray: cannot open the system configuration file:
/tmp/yuqk_a5c25dda/etc/povray/3.8/povray.conf: No such file or directory
Persistence of Vision(tm) Ray Tracer    (see --license)
Copyright 1991-2025 Persistence of Vision Raytracer Pty. Ltd.
POV-Ray (yuqk) 3.8.0-x.yuqk_a5c25dda.unofficial
This is an unofficial version compiled by: louis
...
...

povray is still looking for the configuration file in the construction 
folder /tmp/yuqk_a5c25dda/...


I think I'd have to re-run "make install" with my folder as the target, 
but I can't see (or I didn't understand) how to do that.



Any help ?




-- 
kurtz le pirate
compagnie de la banquise

Post a reply to this message

hi,

kurtz le pirate <kur### [at] freefr> wrote:
>
> I think I'd have to re-run "make install" with my folder as the target,
> but I can't see (or I didn't understand) how to do that.

I too installed yuqk in a convenient place.  write an email, I'd be happy to
send you a build script and stuff.


regards, jr.

Post a reply to this message

Damn.
I like that tree command!   :)

Post a reply to this message