

"B. Gimeno" <nomail@nomail> wrote:
According to the documentation, the
> polynomial version of the syntax lacks the "command" parameter at first so that
> the program starts processing.
I checked out the results using the data for the torus in the docs, and I think
I see what you mean. polynomial {} requires the order of the equation followed
by the rest of the data. I made the edit, and it should work fine now. [version
1.0a]
> From the "function" version I lack experience to
> know why it also gets stuck in the calculation. Greetings, and thank you for
> sharing.
>
> B. Gimeno
I'm not sure what you mean by "stuck"  does POVRay give you an error?
I had no problems when I copied and pasted the function into a scene:
#declare Polynomial = function {(pow(x,4)) + (2 * pow(x,2) * pow(y,2)) + (2 *
pow(x,2) * pow(z,2)) + (104 * pow(x,2)) + (pow(y,4)) + (2 * pow(y,2) *
pow(z,2)) + (56 * pow(y,2)) + (pow(z,4)) + (104 * pow(z,2)) + 784}
and then used that function in an isosurface:
isosurface {
function {Polynomial (x, y, z)}
accuracy 0.001
max_gradient 4510
contained_by {box {<10, 4, 10>, <10, 4, 10>} }
texture {pigment {DocPigment} finish {specular 0.2}}
} // end isosurface
I may see if I can work out some more refinements to make it a little easier to
use. I could highlight the terms that need values (if they are nonzero) so
that it's easier to find the terms to edit. There might also be a way for me to
consolidate the list of terms depending on the order  but that might take quite
a bit of tinkering.
Post a reply to this message
Attachments:
Download 'polynomial 1.0a.ods.dat' (47 KB)

