POV-Ray : Newsgroups : povray.general : Ovus : Re: Ovus Server Time
28 Apr 2024 20:37:02 EDT (-0400)
  Re: Ovus  
From: clipka
Date: 4 May 2016 11:42:09
Message: <572a1851$1@news.povray.org>
Am 04.05.2016 um 16:43 schrieb Le_Forgeron:

>> I have a few requests:
>>
>> (1) Can you update the documentation to include...
>> (1.a) how the radius of the spindle is computed;
>> (1.b) the fact(?) that the bottom sphere is always placed at <0,0,0>
> 
> the documentation is in the wiki, right ? So anyone could update it to
> add these element. I thought 1.b was already in the documentation.

Guess what -- I'm a bit busy documenting all the stuff I've added since
3.7.0 ;)
Also, I thought you might have produced the original 2D sketch, and
might be the person most fit to add the minor spindle radius to it.

You're right about 1.b though.


>> (2) Do you think you can extend the code to allow for more flexibility
>> in the shape, by letting us specify the distance between the two spheres
>> as well as the minor radius of the spindle?
> 
> I would not clobber the actual object with such extension, but I might
> consider a new object (along the line of sor & lathe). The main "beauty"
> of ovus is being similar to torus, and simple.
> Can you provide a new name for such new beast ?

I think the ovus primitive is the perfect place to put these extensions;
after all, I'm sure the ability to tweak these parameters will give us
better results when trying to approximate true egg shapes.

Also, my guess would be that such an extended shape would share a lot of
code with the existing one. The only major things that would need to be
changed are the parameters to compute the radii relevant for the
spindle, and the "altitudes" at which the spindle and spheres meet.
(Though I might of course be wrong, as I haven't looked at the actual
implementation yet.)

Not to mention that finding a really good alternative name for the new
beast is non-trivial, while "ovus" would fit perfectly.

> About being doable, yes, I can (but there will be additional constraints
> on the values, such a minimal minor radius function of the three other
> distances under which you would get an error)

Of course such constraint checks would be part of the deal.

> And do you expect default values for some parameters too ? (yet more
> syntax sugar... )

Since I'd advocate to put it into the ovus primitive, of course the
default values would be Bottom_radius for the Y coordinate of the top
sphere, and 2*max(Bottom_radius,Top_radius).


Post a reply to this message

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.