









 
 




 
 


I'm using POVRay to render cross sections of four and five dimensional uniform
polytopes  especially star polytopes. These renders can be seen on my website
http://www.polyope.htm/hedrondude/polychora.htm I use the polygon keyword quite
a bit, but it only renders with the binary filling (all odd density regions gets
filled in, even density are left as holes) which forces me to manually fill in
all the non0 even density regions. This isn't too bad for simple polytopes,
but with more complex ones, this gets very tedious. Is it possible to render
polygons with density filling (all non0 density regions gets filled in  i.e.
filled in by the 'winding method') or better yet could this be a feature for
POVRay 3.8 where there is a density filling option for the polygon keyword. I
would suggest something like this:
#local obj=polygon {45,v1,v2,v3,......,v44,v1 density}
Post a reply to this message


 
 




 
 


Le 03/06/2018 Ã 05:24, Hedrondude a Ã©critÂ :
> I'm using POVRay to render cross sections of four and five dimensional uniform
> polytopes  especially star polytopes. These renders can be seen on my website
> http://www.polyope.htm/hedrondude/polychora.htm I use the polygon keyword quite
> a bit, but it only renders with the binary filling (all odd density regions gets
> filled in, even density are left as holes) which forces me to manually fill in
> all the non0 even density regions. This isn't too bad for simple polytopes,
> but with more complex ones, this gets very tedious. Is it possible to render
> polygons with density filling (all non0 density regions gets filled in  i.e.
> filled in by the 'winding method') or better yet could this be a feature for
> POVRay 3.8 where there is a density filling option for the polygon keyword. I
> would suggest something like this:
>
> #local obj=polygon {45,v1,v2,v3,......,v44,v1 density}
>
>
Fixing the url: http://www.polytope.net/hedrondude/polychora.htm
You seems to already have some works on filling
(http://www.polytope.net/hedrondude/glossary.htm , Filling method)
Post a reply to this message


 
 




 
 


Am 03.06.2018 um 05:24 schrieb Hedrondude:
> I'm using POVRay to render cross sections of four and five dimensional uniform
> polytopes  especially star polytopes. These renders can be seen on my website
> http://www.polyope.htm/hedrondude/polychora.htm I use the polygon keyword quite
> a bit, but it only renders with the binary filling (all odd density regions gets
> filled in, even density are left as holes) which forces me to manually fill in
> all the non0 even density regions. This isn't too bad for simple polytopes,
> but with more complex ones, this gets very tedious. Is it possible to render
> polygons with density filling (all non0 density regions gets filled in  i.e.
> filled in by the 'winding method') or better yet could this be a feature for
> POVRay 3.8 where there is a density filling option for the polygon keyword. I
> would suggest something like this:
>
> #local obj=polygon {45,v1,v2,v3,......,v44,v1 density}
I'm not sure I understand how Density Filling is defined; I had a look
at http://www.polytope.net/hedrondude/fillings.png, but the technical
terms "density" and "orientable" used in there are greek to me. (Also,
it certainly doesn't help that it is depicted as giving results
indentical to Natural Filling).
At the end of the day, we'll need an algorithm to implement, so ideally,
can you describe how one would test whether a given point (Xp,Yp) is to
be coloured black or white, based on the list of points (X1,Y1),
(X2,Y2), ... (Xn,Yn)?
The closer that algorithm is to our current Binary Filling method, the
easier it would be to implement.
The current algorithm implementing Binary Filling takes each edge
(Xa,Ya)>(Xb,Yb), tests whether it intersects the ray
(Xp,Yp)>(+inf,Yp), and keeps track of whether the number of
intersecting edges is odd or even.
For example, this algorithm would be easy to adapt to Solid Filling, by
just keeping track of whether the number of intersecting edges is nonzero.
I have a hunch that a similar algorithm to implement Density Filling
would take each edge (Xa,Ya)>(Xb,Yb), test whether it intersects the
ray (Xp,Yp)>(+inf,Yp), and if so, test whether Ya>Yb  and then do
/something/ with the result; compute the difference between the Ya>Yb
and Ya<Yb intersections, maybe? Or keep tabs on the distances of the
intersections, and colour the point depending on whether Ya>Yb?
I'd like to point out that such an algorithm may break down "near"
regions where a portion of the polygon is "flipped over" (if you know
what I mean; but I suspect that's what is meant by "nonorientable", so
you probably already know that).
Note that an algorithm along the lines of, "examine all edges
immediately adjacent to the region the point is in", would require
drastic changes to the polygon code, as the current implementation has
no concept of "regions": All it knows about are the coordinates and
ordering of the original defining vertices.
Post a reply to this message


 
 




 
 


Am 03.06.2018 um 11:27 schrieb clipka:
> The current algorithm implementing Binary Filling takes each edge
> (Xa,Ya)>(Xb,Yb), tests whether it intersects the ray
> (Xp,Yp)>(+inf,Yp), and keeps track of whether the number of
> intersecting edges is odd or even.
>
> For example, this algorithm would be easy to adapt to Solid Filling, by
> just keeping track of whether the number of intersecting edges is nonzero.
Ha, that's of course nonsense, as it would leave everything "left" of
the polygon filled. Solid filling is far more difficult to implement
than binary filling, and I guess it can't be done without first
analyzing the topology of the polygon boundary.
Post a reply to this message


 
 




 
 


clipka <ano### [at] anonymousorg> wrote:
> Am 03.06.2018 um 05:24 schrieb Hedrondude:
> > I'm using POVRay to render cross sections of four and five dimensional uniform
> > polytopes  especially star polytopes. These renders can be seen on my website
> > http://www.polyope.htm/hedrondude/polychora.htm I use the polygon keyword quite
> > a bit, but it only renders with the binary filling (all odd density regions gets
> > filled in, even density are left as holes) which forces me to manually fill in
> > all the non0 even density regions. This isn't too bad for simple polytopes,
> > but with more complex ones, this gets very tedious. Is it possible to render
> > polygons with density filling (all non0 density regions gets filled in  i.e.
> > filled in by the 'winding method') or better yet could this be a feature for
> > POVRay 3.8 where there is a density filling option for the polygon keyword. I
> > would suggest something like this:
> >
> > #local obj=polygon {45,v1,v2,v3,......,v44,v1 density}
>
> I'm not sure I understand how Density Filling is defined; I had a look
> at http://www.polytope.net/hedrondude/fillings.png, but the technical
> terms "density" and "orientable" used in there are greek to me. (Also,
> it certainly doesn't help that it is depicted as giving results
> indentical to Natural Filling).
>
> At the end of the day, we'll need an algorithm to implement, so ideally,
> can you describe how one would test whether a given point (Xp,Yp) is to
> be coloured black or white, based on the list of points (X1,Y1),
> (X2,Y2), ... (Xn,Yn)?
>
> The closer that algorithm is to our current Binary Filling method, the
> easier it would be to implement.
>
> The current algorithm implementing Binary Filling takes each edge
> (Xa,Ya)>(Xb,Yb), tests whether it intersects the ray
> (Xp,Yp)>(+inf,Yp), and keeps track of whether the number of
> intersecting edges is odd or even.
>
> For example, this algorithm would be easy to adapt to Solid Filling, by
> just keeping track of whether the number of intersecting edges is nonzero.
>
>
> I have a hunch that a similar algorithm to implement Density Filling
> would take each edge (Xa,Ya)>(Xb,Yb), test whether it intersects the
> ray (Xp,Yp)>(+inf,Yp), and if so, test whether Ya>Yb  and then do
> /something/ with the result; compute the difference between the Ya>Yb
> and Ya<Yb intersections, maybe? Or keep tabs on the distances of the
> intersections, and colour the point depending on whether Ya>Yb?
Thanks for the replies everyone.
For density filling, take each edge (Xa,Ya)>(Xb,Yb) and it's direction (if
heading downwards (clockwise) then direction=+1, if heading upwards (counter
clockwise) then direction=1) and test if it intersects the ray
(Xp,Yp)>(+inf,Yp)  add up all of the direction values to get the density of
the region. That should do it.
Another cool feature would be to color polygons according to density or to leave
some densities unfilled.
Post a reply to this message


 
 




 
 


Am 04.06.2018 um 04:29 schrieb Hedrondude:
> Another cool feature would be to color polygons according to density or to leave
> some densities unfilled.
I don't think the former would be possible /per se/ with reasonable
effort. The latter would probably be quite easy to implement (and could
then be used to emulate the former, by using copies of the polygon with
different colours and different density ranges), but we'd need to find a
neat syntax for such a feature.
Post a reply to this message


 
 




 
 


Le 04/06/2018 Ã 04:29, Hedrondude a Ã©critÂ :
> Thanks for the replies everyone.
>
> For density filling, take each edge (Xa,Ya)>(Xb,Yb) and it's direction (if
> heading downwards (clockwise) then direction=+1, if heading upwards (counter
> clockwise) then direction=1) and test if it intersects the ray
> (Xp,Yp)>(+inf,Yp)  add up all of the direction values to get the density of
> the region. That should do it.
>
> Another cool feature would be to color polygons according to density or to leave
> some densities unfilled.
>
After thought, I'm afraid there is a big problem: in Povray, polygon
(and actually triangle too) are not oriented. This is basically the root
of the nonhandness commitment.
As long as "density" would need an orientation to work correctly, it
would be notcompatible with the parsing of polygon using 3D vectors.
On the other hand, the polygon of Povray allows the removal of inner
parts, something usual polygons do not allow without tricking (such as
zerowidth links between outside perimeter and inner holes).
polygon { Number, V1, V2, ... Vk, V1,
H1, H2, ... Hm, H1 }
Vx being outside perimeter
Hx being inside hole perimeter (and holes can be repeated)
Post a reply to this message


 
 




 
 


Am 04.06.2018 um 17:30 schrieb Le_Forgeron:
> Le 04/06/2018 Ã 04:29, Hedrondude a Ã©critÂ :
>
>> Thanks for the replies everyone.
>>
>> For density filling, take each edge (Xa,Ya)>(Xb,Yb) and it's direction (if
>> heading downwards (clockwise) then direction=+1, if heading upwards (counter
>> clockwise) then direction=1) and test if it intersects the ray
>> (Xp,Yp)>(+inf,Yp)  add up all of the direction values to get the density of
>> the region. That should do it.
>>
>> Another cool feature would be to color polygons according to density or to leave
>> some densities unfilled.
>
> After thought, I'm afraid there is a big problem: in Povray, polygon
> (and actually triangle too) are not oriented. This is basically the root
> of the nonhandness commitment.
>
> As long as "density" would need an orientation to work correctly, it
> would be notcompatible with the parsing of polygon using 3D vectors.
That would only be true if the algorithm would be asymmetric with
respect to winding order.
Note that, in the above algorithm, reversing the definition of "positive
direction" will only affect the /sign/ of the computed "direction sum",
while the magnitude will remain unaffected; and it's only the magnitude
that matters in the "in" vs. "out" test (specifically whether that
magnitude is nonzero).
So no, there's nothing "notcompatible" about density filling; it only
adds one requirement that the user must pay attention to: They must use
a /consistent/ winding order for all "subpolygons" of any /one/ polygon
primitive (with "holes" using the "reverse" of that winding order).
Whether that winding order is left or righthanded from any given
perspective is entirely irrelevant. It may even differ between polygons
on the very same plane, provided they reside in separate primitives.
Post a reply to this message


 
 




 
 


clipka <ano### [at] anonymousorg> wrote:
> Am 04.06.2018 um 04:29 schrieb Hedrondude:
>
> > Another cool feature would be to color polygons according to density or to leave
> > some densities unfilled.
>
> I don't think the former would be possible /per se/ with reasonable
> effort. The latter would probably be quite easy to implement (and could
> then be used to emulate the former, by using copies of the polygon with
> different colours and different density ranges), but we'd need to find a
> neat syntax for such a feature.
ideas for syntax:
binary filling, leave as is:
polygon {n, v1,v2,v3,...v1}
density filling:
polygon {n, v1,v2,v3,...v1 density}
fill in one particular density
polygon {m,v1,v2,v3,...v1 density d}
fill in m particular densities:
polygon {n, v1,v2,v3,...v1 density {m,d1,d2,d3,..,dn}}
Post a reply to this message


 
 




 
 


On 06/04/2018 12:27 PM, clipka wrote:
> Am 04.06.2018 um 17:30 schrieb Le_Forgeron:
>> Le 04/06/2018 Ã 04:29, Hedrondude a Ã©critÂ :
>>
...
>
I'd like to suggest, if we are looking at polygon enhancements 
canonical point ordering for fill options etc, we consider staying
compatible with packages like:
https://sourceforge.net/projects/polyclipping/
even if not looking to support that package specifically  though it
would be my choice at present.
Integrating 'polyclipping' in some fashion with POVRay via new SDL
options would open up new capabilities related to linear splines,
polygons, prisms for sure(1). Perhaps also additional bounding options,
fonts and such too.
Bill P.
(1)  SDL having a general 'list' (C++ std::vector like) features
alongside too for point lists would be very handy too.
Post a reply to this message


 
 




 

