Could someone explain to me, briefly, the meaning of the following
isosurfaces functions : 

r, s, %, min(), max().

Thank you very much.
Fabien.

Post a reply to this message

Fabien Mosen wrote:

> Could someone explain to me, briefly, the meaning of the following
> isosurfaces functions :
>
> r, s, %, min(), max().

min and max : see the file texture1.pov in the megapov demos, for
instance :
#declare GRID1=    function  {min(min(abs(cos(z)),
abs(cos(y))),abs(cos(x)))}

r,s : something from the isoblob ?

G.


>
>
> Thank you very much.
> Fabien.

Post a reply to this message

On Thu, 27 Jul 2000 14:11:33 +0200, Gilles Tran wrote:
>Fabien Mosen wrote:
>
>> Could someone explain to me, briefly, the meaning of the following
>> isosurfaces functions :
>>
>> r, s, %, min(), max().
>
>min and max : see the file texture1.pov in the megapov demos, for
>instance :
>#declare GRID1=    function  {min(min(abs(cos(z)),
>abs(cos(y))),abs(cos(x)))}
>
>r,s : something from the isoblob ?

% is the modulo operator, I'd guess.  (a%b) is the remainder when you divide
a by b.

I think r and s are reserved words but they don't actually do anything.  It
was a feature that was never completely implemented or something.

-- 
Ron Parker   http://www2.fwi.com/~parkerr/traces.html
My opinions.  Mine.  Not anyone else's.

Post a reply to this message

In article <397FF3F8.1CD236F3@skynet.be>, Fabien Mosen 
<fab### [at] skynetbe> wrote:

> Could someone explain to me, briefly, the meaning of the following
> isosurfaces functions : 
> 
> r, s, %, min(), max().

min() and max() take two parameters, and return the lesser and greater 
of the two respectively. min(A, B) will return A if it is lower than B, 
and B if it is lower than A, max() does the opposite, returning the 
greater value.

% is modulus
! is factorial
^ is exponentiation

t is the clock value, according to the function pattern documentation, 
however, the isoblob functions also use r, s, and t. In isoblobs, they 
are the coordinates of something...I'm not sure what, though. Looking at 
the code, it seems to be coordinates in "component space", after the 
transformations are done, while x, y, and z would be absolute, 
non-transformed coordinates.
Take this with a grain of salt though...I find this portion of the code 
difficult to read(argh, more global variables!).

-- 
Christopher James Huff - Personal e-mail: chr### [at] maccom
TAG(Technical Assistance Group) e-mail: chr### [at] tagpovrayorg
Personal Web page: http://homepage.mac.com/chrishuff/
TAG Web page: http://tag.povray.org/

Post a reply to this message