Next Article in Journal
Immersive Molecular Dynamics in Virtual Reality: Increasing Efficiency of Educational Process with Companion Converter for NarupaXR
Previous Article in Journal
Postprocessing for Skin Detection
 
 
Font Type:
Arial Georgia Verdana
Font Size:
Aa Aa Aa
Line Spacing:
Column Width:
Background:
Article

Robust Visibility Surface Determination in Object Space via Plücker Coordinates

Department of Information Engineering, University of Padova, 35131 Padova, Italy
*
Author to whom correspondence should be addressed.
J. Imaging 2021, 7(6), 96; https://doi.org/10.3390/jimaging7060096
Submission received: 7 May 2021 / Revised: 30 May 2021 / Accepted: 31 May 2021 / Published: 3 June 2021
(This article belongs to the Section Visualization and Computer Graphics)

Abstract

:
Industrial 3D models are usually characterized by a large number of hidden faces and it is very important to simplify them. Visible-surface determination methods provide one of the most common solutions to the visibility problem. This study presents a robust technique to address the global visibility problem in object space that guarantees theoretical convergence to the optimal result. More specifically, we propose a strategy that, in a finite number of steps, determines if each face of the mesh is globally visible or not. The proposed method is based on the use of Plücker coordinates that allows it to provide an efficient way to determine the intersection between a ray and a triangle. This algorithm does not require pre-calculations such as estimating the normal at each face: this implies the resilience to normals orientation. We compared the performance of the proposed algorithm against a state-of-the-art technique. Results showed that our approach is more robust in terms of convergence to the maximum lossless compression.

1. Introduction

Nowadays, computer vision plays an increasing role in the industrial robotics area [1]. With the transition to Industry 4.0, robotic systems must be able to work even more independently, without the constant supervision of a human operator. Those systems must be able to see and perform decisions based on what they perceive [2]. For example, consider to grab an object, randomly placed within a box, with a robotic manipulator. Typically, a scanner captures a three-dimensional image of the box and then a matching algorithm compares it with the 3D model of the object to find correspondences. By means of complex algorithms, a compatible robot path is then planned. The problem of those algorithms comes with their complexity which is proportional to mesh dimension, i.e., the number of its triangles. At once, they must be efficient in order to satisfy the imposed cycle time and the best practice to reduce it is by removing unnecessary triangles. Especially in the industrial field, many models are characterised by detailed interiors which are invisible. Most of the faces are hidden inside the model and, therefore, this information is redundant for recognition purposes. In some cases, it can be a considerable part of the total mesh, leading to a waste of system memory and a significant decrease in performance. Actually, this problem arises in heavily based ray tracing applications, such as 3D scanner simulators [3]. In this scenario, an algorithm is essential for reducing the number of triangles without losing useful information. In literature, there exist several different techniques to remove hidden surfaces. They are commonly known as visible-surface determination (VSD) algorithms. There exist two main approaches: image space and object space. The former exploits rasterization rendering techniques to convert objects to pixels. Visibility is decided at each pixel position on the projection plane and, therefore, the complexity and the accuracy depend on the resolution of the view image. Image space techniques quickly provide a result, even if it is bounded to a particular view. In other words, surfaces removed for a viewpoint may be visible from another one. This implies the need to run the algorithm every time the object pose or view changes. These features make those methods suitable for rendering optimizations, e.g., to limit the number of primitives to draw achieving better frame rates. This procedure is handled differently by several algorithms: z-buffering [4], binary space partitioning [5], ray tracing, Warnock [6] and Painter algorithms [7] are the most popular ones. In some scenarios, it is preferable to have a global result, which is view independent, even if at a higher computational cost. Actually, object space methods compare each mesh face with all the others to determine which surfaces, as a whole, are visible. Given the dependence on the number of faces those methods are slower but more precise. Some examples have been proposed in [8,9]. There also exists an hybrid approach that exploits an image space technique with different views to merge the results obtaining an approximated global result [10].
This study presents a robust technique to address the global visibility problem in object space. The aim of this work is to develop an algorithm that guarantees theoretical convergence to the optimal result. In particular, we prove that, with a proper sampling technique, it is possible to correctly classify all the visible faces of a mesh using a finite number of computations. In addition, the proposed method does not require pre-calculations such as estimating the normal at each face, which is necessary information for algorithms relying on image space. These properties make this algorithm suitable for offline evaluation to optimize a 3D model by reducing its size. A typical background of interest of this application is the industrial one where the user needs to recognize an object to plan its manufacturing. Usually, such object does not deform but continuously changes its pose. In this case, it would be enough to pre-process the 3D model once using our method before running recognition algorithms.
Actually, we propose an algorithm based on the definition of ambient occlusion to determine the visibility of 3D model triangles. We exploit the ray tracing technique and, consequently, ray-triangle intersection algorithm. This process is further improved by using a test based on Plücker coordinates instead of the widely known Möller-Trumbore algorithm [11]. Plücker coordinates have already been adopted in exact visibility culling methods [12]: despite this, it is difficult to find a comprehensive mathematical treatment and an algorithm that achieves the optimum in solving the visibility problem. Finally, this approach is numerically tested to validate both the choice of such intersection test and the performance with respect to a state-of-the-art VSD method.
The paper is organized as follows. Section 2 summarizes the most recent works regarding VSD methods and the use of Plücker coordinates to speed up ray-triangle intersection tests. Section 3 shows the problem formulation in detail, focusing on the description of ambient occlusion and Plücker coordinates. Section 5 presents design and software implementation of the algorithm: special emphasis is placed on its limits, highlighting possible future improvements. In Section 6, the proposed solution is tested to analyse compression, quality and performance. The results are also compared to the ones obtained from one of the most widely used VSD methods. Finally, concluding remarks and possible extensions are presented in Section 7.

2. Related Works

Visibility computation is crucial in a wide variety of fields like computer graphics, computer vision, robotics, architecture and telecommunication. First visibility estimation algorithms aimed to determine visible lines or surfaces in a synthesized image of a three-dimensional scene. These problems are known as visible line or visible surface determination. There exist many different techniques to address the visibility problems, but we can identify two widespread algorithms: z-buffering for local visible surface determination and ray tracing for computing global visibility. The z-buffering and its modifications dominate the area of real-time rendering, whereas ray tracing is commonly used in the scope of global illumination simulations. Besides these, there is a plethora of algorithms to solve specific visibility problems. Sutherland [7] provides a survey on ten traditional visible surface algorithms. Durand [13] gives a comprehensive multidisciplinary overview of visibility techniques in various research areas. Bittner [14] provides a taxonomy of visibility problems based on the problem domain and provides a broad overview of visibility problems and algorithms in computer graphics grouped by the proposed taxonomy.
The visibility problem that this work aims to solve can be classified as global visibility, i.e., to identify which surfaces are invisible independently from the viewpoint of an observer placed outside the 3D model. The algorithms that address such problem aims to determine a data structure able to yield the information about which parts of the geometry are invisible to an external observer. Developing efficient global visibility algorithms is still an open problem. A notable work in this field is presented by Durand et al. [9], where the authors propose a structure called visibility complex encoding all visibility relations in 3D space. Unfortunately, creating such structure is O ( n 4 log n ) , where n is the number of polygonal faces in the scene. Therefore, those methods are unfeasible for industrial applications and provide more information of what is really needed for the preprocessing purposes of this work. As explained in Section 3, the approach presented in this paper is based on ambient occlusion computation through ray tracing, to estimate the visibility degree of the various faces to an external observer. Concerning ray tracing computations, several intersection algorithms have been developed over the years. According to Jiménez et al. [15], the most used algorithm to test ray-triangle intersection is the one introduced by Möller and Trumbore [11]. Then, slightly different versions have been proposed mainly aimed at taking advantage of specific hardware accelerations as done by Havel [16]. However, if the intersection point is not required, algorithms based on Plücker coordinates could be faster [17].

3. Problem Formulation

In this section we describe the problem we aim to solve. We want to identify the visible faces of a 3D mesh by exploiting the concept of ambient occlusion in object space. As we will explain extensively in Section 4.1, we evaluate the visibility of a certain point on a face in relation to the amount of ambient light hitting that point. Our goal is to ensure theoretical convergence to the optimal result, i.e., all faces identified correctly. Moreover, we do not take any restrictive assumptions. Before going into theoretical and implementation details, it is useful to first introduce the core elements composing a 3D model and to provide a brief overview about the visibility problem.

3.1. Representation of 3D Objects

There are several ways to represent 3D objects in computer graphics. The most common one consists in considering an object as a collection of surfaces. Given the massive amount of different object types, several surface models have been developed over the years, with an increasing level of complexity according to the level of detail required. Figure 1 shows how a complex surface can be arbitrarily approximated using simple triangles.
The resulting collection of surfaces is called polygonal mesh or simply mesh. Object rendering can be simplified and sped up using polygonal meshes since all surfaces can be described with linear equations. In particular, triangular meshes are preferred for their simplicity, numerical robustness and efficient visualization [18]. Polygonal meshes can be represented in a variety of ways by using the following core elements:
  • vertex: a vector representing the position in 3D space along with further information such as colour, normal vector and texture coordinates;
  • edge: the segment between two vertices;
  • face: a closed set of edges, i.e., a triangle.
These elements are represented in Figure 2.
This work aims to identify which faces of the 3D model are visible or not. By visible we mean there is at least one point outside the model for which there exists a segment, from that point to another on the triangle, that does not intersect any other.

3.2. Visibility Problem

The visibility problem has been one of the first major research topics in computer graphics and is the core of many state-of-the-art algorithms. This concept can be intuitively defined in terms of lines: two points A and B are mutually visible if no object intersects the line A B between them. From this simple notion, it is possible to address the visibility problem in different spaces regarding where points A and B lie [13].
  • Image space: a 2D space for the visual representation of a scene. The rasterization process of converting a 3D scene into a 2D image works in this space. For this reason, the most common methods to solve the visibility problem perform their operations in 2D projection planes.
  • Object space: a 3D space in which the scene is defined and objects lie. Methods developed within this space are computationally onerous and they are usually used to create proper data structure used to sped up subsequent algorithms. These acceleration structures are crucial for real time computer graphics applications such as video games.
  • Line space: the one of all the possible lines that could be traced in a scene. Methods developed within this space try to divide the line space according to the geometry that a given line intercepts. Indeed, as stated at the beginning of this section, the visibility notation can be naturally expressed in relation to those elements.
  • Viewpoint space: the one of all the possible views of an object. Theoretically, it could be partitioned into different regions divided by visual events. A visual event is a change in the topological appearance. For example, while rotating a coin vertically, at a certain point, one of its faces becomes visible while the other not. This process generates a structure referred in literature as aspect graph [19]. The latter has only a theoretical interest since it could have a O ( n 9 ) complexity for general non convex polyhedral objects in a 3D viewpoint space, where n is the number of object faces. Nevertheless, a few visibility problems are defined and addressed in this space, such as viewpoint optimization for object tracking.

3.3. Problem Statement

In this work, the visibility of a certain point on a face is defined in relation to the quantity of ambient light hitting that point; this is the definition of ambient occlusion that we review in Section 4.1. Here, we address the visibility problem in object space and, without loss of generality, we consider triangular meshes. It is trivial to extend the results presented in the following sections to a mesh composed of generic polygons. The problem we want to address can be formally cast as follows. Assume we have a 3D mesh T composed by N triangles, i.e., T = { T 1 , , T N } . The triangle T i is said to be visible, if there exist a ray starting from a point on T i and proceeding to infinity that does not intersect any other triangle of the mesh. The goal is to determine, for i = 1 , , N , if T i is visible or not.

4. Proposed Approach: Ambient Occlusion, Visibility Index and Plücker Coordinates

The approach we propose to deal with the problem stated in Section 3.3 is based on the notion of ambient occlusion. Inspired by this definition, we introduce a visibility index which allows us to estimate if a triangle is visible or not. Basically, given a number of rays starting from points of a triangle, we try to determine if they intersect other triangles of the mesh. We will see that the intersection test can be done in an efficient way exploiting Plücker coordinates and the so-called side operator.

4.1. Ambient Occlusion

Ambient occlusion is a rendering technique used to improve the realism of a scene. It is an empirical technique introduced for the first time by Zhukov et al. to approximate the effects produced by global illumination systems [20]. The ambient occlusion models how a certain surface is illuminated by indirect light caused by the reflections of direct light over the various surfaces of the scene. Figure 3 shows the improvements that such technique brings to a rendered image.
The indirect light is approximated by considering an omnipresent, omnidirectional light source with fixed intensity and colour which is called ambient light. Then the exposure of a certain surface to this light is computed by looking at the geometrical properties of its surrounding. In other words, ambient occlusion is an approximation of the darkening which occurs when the ambient light is blocked by nearby objects. Formally, such term is defined for a point on the surface as the cosine-weighted fraction of the upper hemisphere where incoming light cannot reach the point. To be more precise, the ambient occlusion term for a point P on a face with normal n corresponds to the integral
A O ( P ) = 1 π ω Ω V ( P , ω ) cos θ d ω
where:
  • P is the surface point;
  • Ω is the upper hemisphere generated by the cutting of a sphere centred in P by the plane on which the surface lies;
  • ω is a point of the hemisphere Ω and identifies the incoming light direction (with a slight abuse of language, in the following we will sometimes refer to ω as the ray direction);
  • V ( P , ω ) is a function with value 1 if there is incoming ambient light from direction ω and 0 if not;
  • 1 π is a normalization factor;
  • θ is the angle between direction ω and the surface normal n (note also that cos θ = ω · n ).
In Figure 4, a visual representation of the problem is presented.
The integral in (1) is usually evaluated using Monte Carlo techniques by sampling the upper hemisphere in K points and, for each one, cast a ray to test for occlusions. Therefore, the integral is approximated by:
A O ^ ( P ) = 1 K i = 0 K 1 V ( P , ω i )
with ω i sampled with probability density function
p ( ω i ) = cos ( θ i ) π = ω i · n π .
Notice that normal n shall be oriented correctly towards the outside of the mesh for (3) to be a probability density.
Several different algorithms can be adopted to estimate the ambient occlusion: [21] reviews exhaustively the evolution of ambient occlusion techniques in recent years.

4.2. Visibility Index

We describe the strategy used to determine if a point P of a triangle of the mesh is visible or not. Suppose K rays, say r 0 , , r K 1 , starting from point P have been generated. Notice that each ray r i is well identified by its direction ω i . Then, based on the notion of ambient occlusion and, in particular, on its Monte Carlo estimate in Equation (2), the visibility score of a point P can be expressed as
P V s c o r e ( P ) = 1 K i = 0 K 1 V ( P , ω i )
where V ( P , ω ) = 1 if the ray does not intersect any other triangle and proceed infinitely. Therefore, the point visibility score P V s c o r e of a point P is the fraction of light-rays which are un-occluded. The choice for this visibility score seems well posed since an observer along the direction of such un-occluded rays is able to see the point P. By testing enough points { P 1 , , P M } on a face T it is possible to estimate its visibility score S V s c o r e as the mean of its points scores, giving
S V s c o r e ( T ) = 1 M i = 0 M 1 P V s c o r e ( P i ) .
After the computation of such score for all the faces of the object it is possible to select only the most visible ones applying a global threshold, effectively removing the internal geometry of the model. Actually, a zero threshold allows to select only the visible faces.
The most costly part of the algorithm is to determine the value of the function V ( P , ω ) . This translates in determining if any given ray intersects any other triangle of the mesh along its path. In this study, this process has been developed using Plücker coordinates and tested against the widely known Möller-Trumbore ray-triangle intersection algorithm. In our implementation every ray is tested against all the other object faces until a first intersection is found.

4.3. Plücker Coordinates

Firstly introduced by the mathematician Julius Plücker in 19th century, these coordinates provide an efficient representation of oriented lines. Any real line can be mapped to the Plücker space. Since coordinates are homogeneous, any two points on the same oriented line will have the same Plücker coordinate up to a scaling factor. Let P = ( P x , P y , P z ) and Q = ( Q x , Q y , Q z ) be two distinct points in R 3 which define an oriented line l that goes from Q to P. This line corresponds to a set l of six coefficients, called Plücker coordinates of the line l
l = ( l 0 , l 1 , l 2 , l 3 , l 4 , l 5 )
where the first three represent the direction of the line. Actually,
l 0 = P x Q x , l 1 = P y Q y , l 2 = P z Q z ,
while the other three components are given by the cross product between P and Q, giving
l 3 = P y Q z P z Q y , l 4 = P z Q x P x Q z , l 5 = P x Q y P y Q x .
An important aspect of these coordinates, which has been crucial to this study, is the so-called side operator [22]. Such function characterizes the relative orientation of two lines. Given l = ( l 0 , l 1 , l 2 , l 3 , l 4 , l 5 ) and r = ( r 0 , r 1 , r 2 , r 3 , r 4 , r 5 ) , the side operator is defined as:
side ( l , r ) = l T W r
where
W = 0 3 × 3 I 3 × 3 I 3 × 3 0 3 × 3 .
Therefore, the side operator can also be written as
side ( l , r ) = l 3 r 0 + l 4 r 1 + l 5 r 2 + l 0 r 3 + l 1 r 4 + l 2 r 5 .
Two oriented lines l and r can interact in space in three different ways:
  • if l intersects r, then side ( l , r ) = 0 ;
  • if l goes clockwise around r, then side ( l , r ) > 0 ;
  • if l goes counter-clockwise around r, then side ( l , r ) < 0 .
Such cases are highlighted in Figure 5.
Plücker coordinates can be defined in other less intuitive ways and possess other properties that are not used in this work. Also note that not all the Plücker points define a real line in 3D space, but only those that are on the Plücker hypersurface, also known as Grassman manifold or Klein quadric. Such points l satisfy the condition side ( l , l ) = 0 .

5. Visibility Algorithm Based on Plücker Coordinates

This section starts with an overview of the main steps of the algorithm and, then, describes the implementation details. First, we want to emphasize that typically, in computer graphics, it cannot be assumed that triangles normals are always directed outwards the mesh. Actually, if only the upper hemisphere is considered, like in Figure 4, the procedure may create false occlusions. To avoid such scenario, it is sufficient to consider the whole sphere instead. A false occlusion example is presented in Figure 6.
The algorithm may be divided in three major steps for each mesh triangle T i for which to compute the visibility.
Initialization: We select a set of M points, say P = { P 1 , , P M } , on T i . For each point P i P , we generate K rays as follows: we first create a sphere centred in P i , then we sample K points on the surface of this sphere and, finally, we draw the K rays starting from P i and passing through the previously sampled points. Notice that we generate in total M K rays. How selecting the points on T i and sampling the sphere is described in Section 5.1 and Section 5.2, respectively.
Score computation: Each triangle T j T i is tested against all the rays generated at the previous step to see if an intersection occurs. The ray-triangle intersection test is performed in Plücker space as it will be explained in Section 5.3. If a ray intersects a triangle T j , then it is removed from the set of generated rays. Once the above intersection testing phase has been completed, the visibility score of T i is computed as
S V s c o r e ( T i ) = remaining rays M K
Classification: If S V s c o r e ( T i ) > 0 then T i is classified as visible, otherwise as invisible.
A couple of remarks are now in order.
Remark 1.
Typically, in computer graphics, meshes consist of a large number of triangles that are very small compared to the size of the mesh itself. Based on this fact, in order to reduce the computational burden of the proposed algorithm, in the initialization step we might consider only the barycenter of T i , in place of selecting M points; by doing that, we generate only K rays per triangle instead of M K . Our numerical tests show that such choice does not affect the overall result.
Remark 2.
Note that it is possible to select triangles that are barely visible using a non-zero threshold δ 0 on the score. Formally, T i is invisible or barely visible if S V s c o r e ( T i ) δ .
Next, we explain more in detail how to select the M points on a face of the mesh, how to generate K rays on a sphere and how to compute the intersections of these rays with mesh triangles.

5.1. Sampling Points on Triangle

The points on a triangle T i can be efficiently selected by taking random points at minimum distance or uniformly distributed.
Uniform distribution: Arvo [23] presents a procedure for deriving an area-preserving parametrization from a unit square [ 0 , 1 ] × [ 0 , 1 ] to a given bounded 2-manifold M R n . Using those results it is possible to uniformly sample any bounded surface, in particular a triangle, by having two independent random variables uniformly distributed over the interval [ 0 , 1 ] .
Minimum distance: Random samples are generated on a rectangle containing the triangle T i using the Fast Poisson Disk Sampling method [24]. Then, following the rejection-sampling approach, only points that belong to that triangle are kept. The benefit of this algorithm is to apply a constraint on the minimum distance between the generated points, solving the typical clustering issue of uniform sampling methods.
The uniform distribution method is certainly easier to implement and faster to compute, although it tends to generate clusters of points. On the other hand, the minimum distance approach provides a more distributed set since it imposes a constraint on mutual distances. Therefore, to generate a few points, we recommend using the second method.

5.2. Rays Generation through Sphere Sampling

A key feature for a VSD algorithm is the ability to uniformly explore the surrounding space. It is, in fact, very important to select points on the surface of a sphere as uniform as possible. The two most common methods to generate uniformly distributed points on a spherical surface are the following two.
Uniform distribution: An easy method to uniformly pick random points on an n-dimensional sphere is presented in [25]. It is sufficient to generate an n-dimension vector x = [ x 1 , x 2 , , x n ] T whose x i elements are independent and identically distributed samples of a Gaussian distribution. Then, a point P on the sphere is given by P = x | | x | | 2 .
Fibonacci lattice distribution: By using the notion of golden ratio and golden angle, both deriving from the Fibonacci sequence, it is possible to generate a set of samples at the same distance from their neighbours [26,27]. In fact, the golden angle optimizes the packing efficiency of elements in spiral lattices.
Applying one of the following algorithms on a unitary sphere centred in the axis origin is equivalent to generate a collection of rays directions. Recalling that the visibility score for a given face T i is defined as the fraction of un-occluded rays over the total rays created, it is important to notice that the choice of one algorithm in place of another will change the value and the meaning of that visibility score. The uniform distribution is certainly easier to implement than Fibonacci’s one but tends to generate clusters when the number of sampled points is small. On the other hand, Fibonacci lattice provides greater uniformity even in the case of a few points. Figure 7 shows the sampling results obtained using the two methods described above. The figure also shows the result obtained with the cosine-weighted distribution [23]. The latter is the only one that allows to correctly estimate the ambient occlusion value as defined is Section 4.1. However, we can observe how this choice is not suitable for our aim since it tends to accumulate points near the poles and, consequently, rays are not well distributed. Notice that we are interested to evaluate the occlusion determined by homogeneously distributed rays rather than mathematically estimate the ambient occlusion term. Therefore, from our tests, we conclude that Fibonacci lattice provides the best distribution for our goal.

5.3. Ray Intersection Algorithm via Plücker Coordinates

We are now interested to determine the intersection between a ray and a triangle in Plücker space. This is not trivial since, in this space, it is not possible to define rays but only lines. Recall that a line extends infinitely in both directions while a ray is only a portion of it, starting from a point and going to infinity. This implies the inability to directly use a line-polygon intersection test to search for intersections between a ray and a polygon. Figure 8 shows the difference between the results obtained using line and ray intersection tests. In this section, we first describe Plücker line-polygon intersection test and, then, we modify it to support ray-polygon intersection.
As introduced in Section 4.3, Plücker coordinates can be used to define an efficient line-polygon intersection test thanks to the side operator. Actually, a line hits a polygon if and only if it hits one of the polygon edges, or goes around clockwise or counter-clockwise to all the edges [28]. Figure 9 shows two examples of such test. The convention chosen is to define a polygon as a sequence of vertices { X 1 , , X N } in such a way that the direction of the edges e i is defined from X i to X i + 1 ; in particular, the last edge goes from X N to X 1 .
Consider the edges e i of a convex polygon with i = { 1 , , m } , m N 3 and a line l. The line l intersects the polygon if and only if
e i , side ( l , e i ) 0 OR e i , side ( l , e i ) 0 .
After describing the line-polygon intersection test method, we show how it is possible to use it as a ray intersection test [29,30].
First of all, consider a plane π containing the ray origin P. Observe that this plane divides the 3D space in two half-spaces H f and H b , where we assume the former contains the ray trajectory. Now, let n be the versor orthogonal to π starting from P and contained in H f . Then, the two half-spaces are formally defined as:
H f = { x R 3 : n · ( x P ) > 0 } H b = { x R 3 : n · ( x P ) < 0 } .
As shown in Figure 10, ray-polygon intersection test is equivalent to the line-polygon one when considering only the geometries in H f . Figure 10 also shows the challenging situation in which the vertices of a polygon may not belong entirely to one half-space. In this condition, the polygon shall be clipped into two sub-polygons, each one belonging to the corresponding half-space. For instance, with reference to Figure 10, triangle T 4 is split into the trapezoid T 4 f and the triangle T 4 b . Only the trapezoid T 4 f will be processed in the ray intersection test. This clipping procedure is explained in Section 5.3.1.

5.3.1. Clipping

The aim of this procedure is to determine the intersection points between the edges of the triangle and the plane that divides it. As we can see in Figure 11, to identify the polygons T 4 f and T 4 b in which the triangle is divided, we need to compute the intersection points I 1 and I 2 with the plane π .
Consider the intersection point I 1 . With reference to Figure 12, it is possible to classify the points A and B to be either in front, back or on the plane π defined by the normal n and a point P.
The classification can be done by looking at the signs of d A and d B , which are the scalar products between n and the vectors A P and B P , respectively:
d A = n T ( A P ) , d B = n T ( B P ) .
If sign ( d A ) > 0 , the point A is in front of the plane while, if sign ( d A ) < 0 , on the back and, if d A = 0 , the point lies on the plane. From those observations, it is clear that an intersection between the segment A B and the plane π is only possible if the following condition holds:
sign ( d A ) sign ( d B ) OR sign ( d A ) · sign ( d B ) = 0 .
Note that the intersection point I 1 between segment A B and plane π can be expressed as
I 1 = A + t ( B A ) ,
where t [ 0 , 1 ] . It is possible to compute the value of t by observing that the vector I 1 P lies on the plane and, therefore, n T ( I 1 P ) = 0 . We obtain:
0 = n T ( I 1 P ) = n T ( A P ) + t n T ( B A ) = n T ( A P ) + t n T ( B P + P A ) = d A + t ( d B d A ) .
This implies:
t = d A d A d B .
Finally, we obtain:
I 1 = A + d A d A d B ( B A ) .
In a similar way we can compute the intersection point I 2 . By using the above procedure, it is possible to divide any polygon w.r.t. an arbitrary plane π in 3D space into its front and back geometries. For example, by assuming that the polygon has three vertices, the only case in which clipping is required is when a vertex belongs to a different half-space of the others. Without loss of generality, we assume that B H b , while A , C H f . The clipping procedure can be summarized with the following points:
  • Compute intersection points I 1 and I 2 of segments A B and B C with the plane π using the procedure described above.
  • Generate two sub-polygons: the triangle I 1 B I 2 H b and the trapezoid A I 1 I 2 C H f .
Figure 11 shows the result of this procedure.
In our implementation, given a point P j on T i and a pencil of K rays starting from P j , the clipping procedure is applied using the same plane for all the rays; specifically the plane used is the one containing the triangle T i .

5.4. Proposed Approach Implementation and Its Convergence Properties

The implementation of the strategy we described in the previous sections, is reported in Algorithm 1.
Algorithm 1 VSD based on Plücker coordinates
Input: 3D mesh T = { T 1 , , T N }
Implementation: For each T i , the following actions are performed in order:
  • select M points, P 1 , , P M , on T i (see Section 5.1);
  • for each point P h , h = 1 , , M , generate K rays (see Section 5.2);
  • for each of the M K rays generated at the previous point, perform the ray intersection test against all the triangles T j T i (see Section 5.3); if a ray intersects T j , then it is removed from the set of generated rays;
  • compute the visibility score of triangle T i as in (8).

Classification: For i 1 , , N , triangle T i is classified as visible is S V score ( T i ) > 0 , otherwise as non visible.
Observe that, based on the proposed procedure, a non-visible triangle will be always classified as non visible, while a visible triangle might be erroneously classified as non-visible. However, it is possible to see that by increasing M and K, i.e., the number of points randomly selected on any triangle and the number of rays generated starting from any selected point, respectively, the misclassification error decreases. This fact is formally stated in the following propositions.
Proposition 1.
Consider Algorithm 1. Assume that
  • the M points in step (1) are selected either uniformly random or adopting the minimum distance approach; and
  • the K rays in step (2) are generated uniformly random.
Then, for M and K going to infinity, that is, M , K , the probability that a visible triangle is classified as non visible goes to 0.
Proof. 
Let S be a sphere that contains the entire mesh. Consider a visible triangle T i . The fact that T i is visible means that there exists a point Q 1 on T i and a point Q 2 on S such that the segment connecting Q 1 to Q 2 does not intersect any other triangle of the mesh. Let Q 1 Q 2 be the line passing through Q 1 and Q 2 and let C Q 1 Q 2 r be the infinitely long cylinder of radius r having as axis the line Q 1 Q 2 . Accordingly, define
  • I 1 r to be the region obtained by intersecting C Q 1 Q 2 r with T i ; and
  • I 2 r to be the region obtained by intersecting C Q 1 Q 2 r with S and containing Q 2 .
Notice that, for r > 0 , both I 1 r and I 2 r are connected regions of non-zero measure.
Since T i is visible, it follows that there exists r ¯ > 0 such that the portion of C Q 1 Q 2 r ¯ included between I 1 r ¯ and I 2 r ¯ does not intersect any triangle of the mesh; in turn, this fact is true also for any segment connecting a point in I 1 r ¯ to a point in I 2 r ¯ .
Since M goes to , the probability of randomly picking a point P j on T i belonging to I 1 r ¯ goes to 1 (either using the uniform selection or the minimum distance approach). Moreover, since also K goes to , the probability of selecting a ray starting from a given point P j that crosses I 2 r ¯ goes to 1. Hence, for M , K , , T i will be classified as visible with probability that goes to 1. This concludes the proof.  □
Proposition 2.
Assume that
  • the M points in step (1) are selected either uniformly random or adopting the minimum distance approach; and
  • the K rays in step (2) are generated according to the Fibonacci lattice distribution.
Then, there exists K ¯ > 0 , such that, if K K ¯ and M , then the probability that a visible triangle is classified as non visible goes to 0.
Proof. 
Consider a visible triangle T i . Let I 1 r ¯ and I 2 r ¯ be as in the proof of Proposition 1. As observed previously, since M goes to , the probability of randomly picking a point P j on T i belonging to I 1 r ¯ goes to 1 (either using the uniform selection or the minimum distance approach). Moreover, adopting the Fibonacci lattice distribution, there exists K ¯ i , such that, if K K ¯ i , then, for any point P j selected on T i , Algorithm 1 will generate at least one ray starting from P j that crosses the region I 2 r ¯ . This implies that, for K K i and M , triangle T i will be correctly classified with probability 1. To conclude the proof, it suffices to define
K ¯ : = max K i : T i is visible
 □
Based on Remark 1, we may provide a modified version of Algorithm 1 where step (1) can be simplified by considering only the barycentre of the triangle instead of sampling it. Specifically, step (1) can be substituted by the following step: (1’) Compute the barycenter of T i . Clearly, Proposition 1 and Proposition 2 are not still valid when implementing step (1’) instead of step (1). However, in our numerical tests described in Section 6, we have implemented this modified version of Algorithm 1 and the obtained results show that this choice does not affect the overall result. This fact is not surprising since we have considered the typical case where the size of each triangle is very small as compared to the size of the entire mesh.

6. Results

This section presents a series of numerical tests to evaluate the proposed algorithm efficiency and robustness. First we compare the performance of the ray-triangle intersection test obtained using our Plücker space-based approach with the use of the Möller-Trumbore algorithm [11], that represents the state-of-the-art in this scenario. We then compare our solution with a state-of-the-art method, based on ambient occlusion estimate in the image space, which is implemented in MeshLab; see [10] for all the implementation details. To carry on all of these tests, we used a midrange PC equipped with an Intel i3-6100 CPU, 8 GB DDR4 RAM, and a AMD RX-480 4 GB GPU with 2304 stream processors. In particular, we implemented all the algorithms using high-level shading language (HLSL). This allows us to take full advantage of the GPU power which is made specifically for computer graphics tasks.

6.1. Intersection Algorithms Comparison

The algorithm described in Section 5 is heavily based on the intersection test between rays and triangles. Therefore, the computation complexity strongly depends on the optimization of this test. For that reason, we decide to compare the performance of Plücker-based ray-triangle intersection algorithm with the Möller-Trumbore one. To compare the two methods we designed a numerical test that can be summarized in the following steps.
  • Generate a set of triangles T randomly within a cubic volume of 1   m × 1   m × 1   m .
  • Create a set of points S by sampling the surface of a sphere, with radius 2   m , centred in the cubic volume, using the Fibonacci distribution.
  • For each point S S , generate a ray starting from the volume centre and passing through S, thus generating a set of rays R .
  • For each ray in R , check if it is occluded by at least one triangle in T .
Finally, the algorithm yields the following set:
V = { r R : t T : intersects ( r , t ) }
where intersects ( r , t ) is either computed with Möller-Trumbore method or the Plücker-based one. Of course, the two methods produce the same set V but the number of operations they require is different. To provide a more reliable result, we reproduced all the tests 10 times by averaging the partial results. Moreover, since there are two parameters in the test algorithm, i.e., the number of sampled points in the sphere surface ( | S | ) and the number of generated triangles ( | T | ), we decide each time to fix one parameter and change the other to allow a more detailed and clear reading. Figure 13 shows the time spent to run the two algorithms and the ratio between them obtained using 10,000 triangles and a different number of rays. We have chosen this particular value because it allows all GPU cores to work full-throttle. Actually, Figure 14 shows that, by using a small number of triangles, some GPU cores remain in idle state. This figure, indeed, shows a performance comparison obtained using 1000 rays and a different number of triangles.
From the results, it is clear how Plücker-based algorithm always offers better performance than the Möller-Trumbore one in the cases tested. Indeed, the latter is about 3 times slower at the same load. An intuitive reason is related to the nature of the two algorithms. At each call of the intersection test, Möller-Trumbore must perform four dot products, three cross products, and three vectorial subtractions [11]. On the other hand, the method based on Plücker coordinates only needs 2 dot products and 1 vectorial subtraction. Although Plücker’s algorithm needs a challenging initialization, it allows to reuse some valuable information about the triangle that in Möller-Trumbore must be calculated on-the-fly at each iteration. Therefore, since we compare the same triangle with many different rays, the pre-processing done by Plücker’s algorithm allows us to save valuable time in the long run. Finally, we want to emphasize that Möller-Trumbore also computes the intersection point between a ray and a triangle. However, this information is totally irrelevant for our purposes.

6.2. Comparison with a State-of-the-Art Method

In this section, we compare the results obtained using the proposed algorithm with the ones provided by a state-of-the-art VSD method. The latter is based on the ambient occlusion estimate in image space and it is implemented within an open-source software called MeshLab [10]. MeshLab is widely used in computer graphics for processing and editing 3D triangular meshes. Among the many operations that this software offers, it provides visibility surface determination based on a custom version of the screen-space ambient occlusion (SSAO) [31]. This technique is typically used to improve the realism of a scene during rendering. Since it works in image space, it is characterized by a lower computational complexity. On the other hand, the dependence on the rendered image resolution limits the result quality. This limitation does not occur by estimating the ambient occlusion in object space using a ray tracing technique as presented in this work. The VSD method provided by MeshLab consists of the following steps.
  • Given a number of views V, V points are sampled on the surface of a sphere that fully embrace the triangular mesh using the Fibonacci distribution. The set R of camera directions contains all the rays starting from each sampled point and directed to the sphere origin.
  • For each direction r R , the depth map of the corresponding camera view is computed. By using this map the ambient occlusion term is computed for each pixel. Each value is then added to the correspondent projected triangle vertex.
  • For each vertex, the partial results obtained for each direction r, i.e., for each view, are averaged to obtain a unique global value.
After this process, it is possible to identify the invisible triangles by selecting those that have at least one occluded vertex of the three, i.e., with a zero ambient occlusion value. Obviously, the approximation improves as the number of views increases. With this brief description of the algorithm, that can be found at MeshLab GitHub repository [32], we want to highlight a couple of key points that distinguish the two approaches. As mentioned earlier, MeshLab VSD method works in the image space. This makes it significantly faster than the algorithm we propose but less robust, due to the dependence on the image resolution used when rendering depth maps. The second main limit regards the assumption that all triangles normals must be oriented towards the outside of the mesh. Actually, the method implemented in MeshLab is directly based on the notion of ambient occlusion presented in Section 4.1 and, therefore, it relies on triangle normals. The following numerical results show that, if triangles normals are flipped, the resulting estimate is totally meaningless. Actually, in the industrial domain, it may happen to observe models with some normals that are wrongly oriented. However, for the first tests, we have considered models with all the normal properly oriented.
To verify and compare performance in a reproducible way, we decided to create three different 3D models. As shown in Figure 15, a monkey head, a ball and a Stanford Bunny are respectively inserted in a box characterized by a hole in the front side. Since we want to test the ability to detect hidden triangles, we decided to design these ad-hoc models which perfectly fit an ideal scenario.
We start by comparing the time needed for the two algorithms to estimate the visibility for each face of the sample meshes. From Figure 16, we can notice how the results are fully expected due to the significant difference in complexity. Actually, we can infer that the computational complexity of MeshLab algorithm is O ( V N ) , where V is the number of views and N the number of triangles. Indeed, the depth map calculation complexity is proportional to the number of triangles. As far as Algorithm 1 is concerned, we have implemented it by considering the modified step (1 ) and the Fibonacci lattice distribution method; it can be seen that has a complexity of O ( K N 2 ) where K is the number of rays tested for each triangle.
However, the time needed to perform VSD is not of particular interest for this work. In fact, recall that these algorithms are usually used in computer graphics only once to lighten 3D models. We aim for a robust method and, therefore, we are more interested in evaluating a performance index such as the number of incorrect classifications. Given the set of triangles T , we consider as misclassification error the sum of false positives and negatives divided by the number of triangles. Since we test if a triangle is invisible, false positives correspond to visible triangles that the algorithm identifies invisible. Consider the set I A of triangles classified as invisible by the algorithm and the set I G of truly invisible triangles which is known a priori. The misclassification error ME can be written as:
ME = | { t I A : t I G } | + | { t I G : t I A } | | T | .
Notice that, as discussed in Section 5.4, false negatives cannot exist by construction of the algorithm, i.e., | { t I G : t I A } | = 0 . Therefore, (9) can be simplified obtaining
ME = | { t I A : t I G } | | T | .
We want to emphasize our interest in achieving the maximum lossless compression in terms of number of triangles. Since the maximum compression is reached when I A = I G , by minimizing ME we are maximizing the lossless compression.
Figure 17 shows the misclassification rates obtained using a different number of rays, or corresponding views, for each of the designed mesh samples. From these plots we can observe how, as the number of rays or views increases, the misclassification rate decreases. This is widely expected since, using fewer views or rays per triangle, it is more likely to misidentify a visible triangle as invisible and, thus, increase the number of false positives. Intuitively, having more views or rays per triangle allows the algorithm to find even the most hidden triangles, getting closer to the optimum value.
From Figure 18 we can observe that our algorithm tends to the optimal faster than the method in comparison. Actually, as described previously, MeshLab VSD method operates in image space and it is constrained to a maximum resolution of 2048 × 2048 pixels [32]. As a result, even if the number of views increases infinitely, this method could never reach the optimal since sphere mapped points would have a finer quantization than the rendered image. This explains why the improvement in accuracy is so slow after a certain number of views. To be more precise, we report in Table 1 the evolution of the two misclassification rates with an increasing number of rays or views. In particular, we can notice that, using 10,000 rays, our algorithm is able to converge to the optimum while, MeshLab algorithm, stabilizes around 1 % of error.
Finally, we want to highlight another significant result. At the beginning of this section, we stressed that one of the limitations of MeshLab algorithm regards the orientation of mesh triangles normals. Based on the notion of ambient occlusion, these normals must be oriented towards the outside of the mesh. This scenario is not so common in computer graphics: a triangular mesh may have normals flipped or it may not have normals at all. Indeed, as described in Section 3.1, depending upon the file format used to represent a mesh, there may or may not be encoded information on triangles normals. We then tried to flip all the normals of the third sample mesh and measuring the misclassification rate again as the number of views changed. Figure 19 shows how MeshLab algorithm is totally unable to solve the VSD problem in the case of incorrectly oriented normals. Our method, on the other hand, obtains the same results as before since it considers the entire sphere and not only the upper hemisphere according to the normal.

7. Conclusions

In this paper, we address the visibility problem in object space. We started from the notion of ambient occlusion and we adapted it to solve the VSD problem. Thanks to the use of Plücker coordinates, we were able to speed up the ray-triangle intersection test. We compared the performance of our algorithm against a state-of-the-art one which exploits another approach based on image space. This allowed us to evaluate pros and cons of a solution in object space with another in image space. Results showed that our approach is more robust in terms of convergence to the maximum lossless compression. In addition, it is resilient to normals orientation, a fundamental characteristic for the industrial context. Although the proposed solution is characterized by a high computational complexity, we stress that its impact is completely negligible since VSD techniques are typically used once per mesh. Anyway, there exist several acceleration techniques that can be adopted to speed up computations such as kd-trees, grids, bounding volume hierarchies [33]. Since the purpose of this work is to prove the result optimality, these improvements were not considered.
Future improvements may involve the creation of an hybrid approach. In particular, we could perform a first processing step with an image space VSD method and, then, a second step with our algorithm in order to give a more accurate result. In this case, our Plücker-based method will check only the invisible triangles recognized during the first step. This hybrid approach would allow to reduce the computational burden without decreasing the accuracy.

Author Contributions

Conceptualization, A.R., M.B. and P.S.; methodology, P.S.; software, A.R., M.B. and P.S.; validation, A.R. and M.B.; formal analysis, R.C.; investigation, P.S.; resources, R.C.; data curation, M.B.; writing—original draft preparation, P.S.; writing—review and editing, A.R. and M.B.; visualization, A.R.; supervision, R.C.; project administration, A.R. All authors have read and agreed to the published version of the manuscript.

Funding

This research received no external funding.

Data Availability Statement

No new data were created or analyzed in this study. Data sharing is not applicable to this article.

Conflicts of Interest

The authors declare no conflict of interest.

References

  1. Chen, S.; Li, Y.; Kwok, N.M. Active vision in robotic systems: A survey of recent developments. Int. J. Robot. Res. 2011, 30, 1343–1377. [Google Scholar] [CrossRef]
  2. Posada, J.; Toro, C.; Barandiaran, I.; Oyarzun, D.; Stricker, D.; de Amicis, R.; Pinto, E.B.; Eisert, P.; Döllner, J.; Vallarino, I. Visual Computing as a Key Enabling Technology for Industrie 4.0 and Industrial Internet. IEEE Comput. Graph. Appl. 2015, 35, 26–40. [Google Scholar] [CrossRef] [PubMed]
  3. Rossi, A.; Barbiero, M.; Carli, R. Vostok: 3D scanner simulation for industrial robot environments. ELCVIA Electron. Lett. Comput. Vis. Image Anal. 2020, 19, 71–84. [Google Scholar] [CrossRef]
  4. Okino, N.; Kakazu, Y.; Morimoto, M. Extended Depth-Buffer Algorithms for Hidden-Surface Visualization. IEEE Comput. Graph. Appl. 1984, 4, 79–88. [Google Scholar] [CrossRef]
  5. Uysal, M.; Sen, B.; Celik, C. Hidden surface removal using bsp tree with cuda. Glob. J. Technol. 3rd World Conf. Inf. Technol. Wcit-2012 2013, 3, 238–243. [Google Scholar]
  6. Warnock, J.E. A Hidden Surface Algorithm for Computer Generated Halftone Pictures. Ph.D. Thesis, Utah University Salt Lake City Department of Computer Science, Salt Lake City, UT, USA, 1969. [Google Scholar]
  7. Sutherland, I.E.; Sproull, R.F.; Schumacker, A. A characterization of ten hiddensurface algorithms. ACM Comput. Surv. (CSUR) 1974, 6, 1–55. [Google Scholar] [CrossRef]
  8. Vaněkčkek, G., Jr. Back-face culling applied to collision detection of polyhedra. J. Vis. Comput. Animat. 1994, 5, 55–63. Available online: https://onlinelibrary.wiley.com/doi/pdf/10.1002/vis.4340050105 (accessed on 1 June 2021). [CrossRef]
  9. Durand, F.; Drettakis, G.; Puech, C. The 3D visibility complex: A new approach to the problems of accurate visibility. In Rendering Techniques ‘96; Pueyo, X., Schröder, P., Eds.; Springer: Vienna, Austria, 1996; pp. 245–256. [Google Scholar]
  10. Cignoni, P.; Callieri, M.; Corsini, M.; Dellepiane, M.; Ganovelli, F.; Ranzuglia, G. MeshLab: An Open-Source Mesh Processing Tool. In Proceedings of the Eurographics Italian Chapter Conference, Salerno, Italy, 2–4 July 2008; Scarano, V., Chiara, R.D., Erra, U., Eds.; The Eurographics Association: Salerno, Italy, 2008. [Google Scholar] [CrossRef]
  11. Möller, T.; Trumbore, B. Fast, Minimum Storage Ray-Triangle Intersection. J. Graph. Tools 1997, 2, 21–28. [Google Scholar] [CrossRef]
  12. Nirenstein, S.; Blake, E.; Gain, J. Exact From-Region Visibility Culling. In Proceedings of the Eurographics Workshop on Rendering, Pisa, Italy, 26–28 June 2002; Debevec, P., Gibson, S., Eds.; The Eurographics Association: Pisa, Italy, 2002. [Google Scholar] [CrossRef]
  13. Durand, F. 3D Visibility: Analytical Study and Applications. Ph.D. Thesis, Universitè Joseph Fourier, Saint-Martin-d’Hères, France, 1999. [Google Scholar]
  14. Bittner, J.; Wonka, P. Visibility in Computer Graphics. Environ. Plan. B Plan. Des. 2003, 30, 729–755. [Google Scholar] [CrossRef] [Green Version]
  15. Jiménez, J.J.; Ogáyar, C.J.; Noguera, J.M.; Paulano, F. Performance analysis for GPU-based ray-triangle algorithms. In Proceedings of the 2014 International Conference on Computer Graphics Theory and Applications (GRAPP), Lisbon, Portugal, 5–8 January 2014; pp. 1–8. [Google Scholar]
  16. Havel, J.; Herout, A. Yet Faster Ray-Triangle Intersection (Using SSE4). IEEE Trans. Vis. Comput. Graph. 2010, 16, 434–438. [Google Scholar] [CrossRef] [PubMed]
  17. Altin, N.; Yazgan, E. RCS prediction using fast ray tracing in Plücker coordinates. In Proceedings of the 2013 7th European Conference on Antennas and Propagation (EuCAP), Gothenburg, Sweden, 8–12 April 2013; pp. 284–288. [Google Scholar]
  18. Kobbelt, L.; Vorsatz, J.; Seidel, H.P. Multiresolution Hierarchies on Unstructured Triangle Meshes. Comput. Geom. J. Theory Appl. 1999, 14, 5–24. [Google Scholar] [CrossRef] [Green Version]
  19. Plantinga, H.; Dyer, C.R. Visibility, occlusion, and the aspect graph. Int. J. Comput. Vis. 1990, 5, 137–160. [Google Scholar] [CrossRef] [Green Version]
  20. Zhukov, S.; Iones, A.; Kronin, G. An ambient light illumination model. In Rendering Techniques ‘98; Drettakis, G., Max, N., Eds.; Springer: Vienna, Austria, 1998; pp. 45–55. [Google Scholar]
  21. Méndez-Feliu Àlex, S.M. From obscurances to ambient occlusion: A survey. Vis. Comput. 2009, 25, 181–196. [Google Scholar] [CrossRef]
  22. Pellegrini, M. Ray Shooting and Lines in Space. In Handbook of Discrete and Computational Geometry; Chapman and Hall/CRC: Boca Raton, FL, USA, 2004; Chapter 41. [Google Scholar]
  23. Arvo, J. State of the Art in Monte Carlo Ray Tracing for Realistic Image Synthesis: Stratified sampling of 2-manifolds. Siggraph 2001 Course 29 2001, 29, 41–64. [Google Scholar]
  24. Bridson, R. Fast Poisson disk sampling in arbitrary dimensions. In Proceedings of the SIGGRAPH Sketches, San Diego, CA, USA, 9 August 2007; p. 22. [Google Scholar]
  25. Muller, M.E. A Note on a Method for Generating Points Uniformly on N-Dimensional Spheres. Commun. ACM 1959, 2, 19–20. [Google Scholar] [CrossRef]
  26. González, Á. Measurement of areas on a sphere using Fibonacci and latitude–longitude lattices. Math. Geosci. 2010, 42, 49. [Google Scholar] [CrossRef] [Green Version]
  27. Keinert, B.; Innmann, M.; Sänger, M.; Stamminger, M. Spherical Fibonacci Mapping. ACM Trans. Graph. 2015, 34, 1–7. [Google Scholar] [CrossRef]
  28. Březina, J.; Exner, P. Fast algorithms for intersection of non-matching grids using Plücker coordinates. Comput. Math. Appl. 2017. [Google Scholar] [CrossRef]
  29. Jones, R. Intersecting a Ray and a Triangle with Plücker Coordinates. RTNews 2000, 13, 67. [Google Scholar]
  30. Shoemake, K. Plücker Coordinate Tutorial. RTNews 1998, 11, 1. [Google Scholar]
  31. Bavoil, L.; Sainz, M. Screen Space Ambient Occlusion. NVIDIA Developer Information. 2008. Available online: http://developer.nvidia.com (accessed on 1 June 2021).
  32. MeshLab GitHub Repository. Available online: https://github.com/cnr-isti-vclab/meshlab (accessed on 1 June 2021).
  33. Bittner, J.; Havran, V.; Slavík, P. Hierarchical visibility culling with occlusion trees. In Proceedings of the Computer Graphics International (Cat. No.98EX149), Hannover, Germany, 26 June 1998; pp. 207–219. [Google Scholar]
Figure 1. Different approximations of the “Stanford Bunny” using triangular meshes.
Figure 1. Different approximations of the “Stanford Bunny” using triangular meshes.
Jimaging 07 00096 g001
Figure 2. Representation of the core elements of a mesh.
Figure 2. Representation of the core elements of a mesh.
Jimaging 07 00096 g002
Figure 3. Visual comparison of a scene illuminated by ambient light. The image on the right shows how ambient occlusion estimation increases the realism of the scene. In particular, note that this method generates soft global shadows that contribute to the visual separation of objects.
Figure 3. Visual comparison of a scene illuminated by ambient light. The image on the right shows how ambient occlusion estimation increases the realism of the scene. In particular, note that this method generates soft global shadows that contribute to the visual separation of objects.
Jimaging 07 00096 g003
Figure 4. Visual representation of the ambient occlusion for a point P. For the rays in example, the function V ( P , ω ) has the following results: V ( P , ω 2 ) = 0 , while V ( P , ω i ) = 1 , ω i in the grey area of the hemisphere Ω , in particular for ω 1 .
Figure 4. Visual representation of the ambient occlusion for a point P. For the rays in example, the function V ( P , ω ) has the following results: V ( P , ω 2 ) = 0 , while V ( P , ω i ) = 1 , ω i in the grey area of the hemisphere Ω , in particular for ω 1 .
Jimaging 07 00096 g004
Figure 5. Possible line configurations in space: on the left l and r intersect, in the middle l goes clockwise around r while on the right l goes counter-clockwise around r.
Figure 5. Possible line configurations in space: on the left l and r intersect, in the middle l goes clockwise around r while on the right l goes counter-clockwise around r.
Jimaging 07 00096 g005
Figure 6. Example of a wrongly oriented normal that results in a false occlusion. By considering only the hemisphere Ω oriented along the normal n, the classification gives a wrong result: the ambient occlusion term is zero. Indeed ω Ω we have an occlusion but there is at least one un-occluded ray r that reaches P.
Figure 6. Example of a wrongly oriented normal that results in a false occlusion. By considering only the hemisphere Ω oriented along the normal n, the classification gives a wrong result: the ambient occlusion term is zero. Indeed ω Ω we have an occlusion but there is at least one un-occluded ray r that reaches P.
Jimaging 07 00096 g006
Figure 7. Comparison of three different points distributions on the surface of a sphere: (a) Cosine-weighted, (b) Uniform, (c) Fibonacci.
Figure 7. Comparison of three different points distributions on the surface of a sphere: (a) Cosine-weighted, (b) Uniform, (c) Fibonacci.
Jimaging 07 00096 g007
Figure 8. Comparison between line and ray intersection tests. (a) Considering the line passing through A and B, there is an intersection with the polygon. (b) Considering the ray starting in A and passing through B, there is no intersection.
Figure 8. Comparison between line and ray intersection tests. (a) Considering the line passing through A and B, there is an intersection with the polygon. (b) Considering the ray starting in A and passing through B, there is no intersection.
Jimaging 07 00096 g008
Figure 9. (a) Lines stabbing a convex polygon in 3D space. Note that the line l goes counter-clockwise around all the edges e i , while r clockwise. (b) Lines missing a convex polygon in 3D space. Note that the line l goes counter-clockwise around the edges e 1 and e 4 , while clockwise around e 2 and e 3 . The opposite happens with r .
Figure 9. (a) Lines stabbing a convex polygon in 3D space. Note that the line l goes counter-clockwise around all the edges e i , while r clockwise. (b) Lines missing a convex polygon in 3D space. Note that the line l goes counter-clockwise around the edges e 1 and e 4 , while clockwise around e 2 and e 3 . The opposite happens with r .
Jimaging 07 00096 g009
Figure 10. A ray-polygon intersection can be seen as a line-polygon one by considering only front geometries. Notice the case of the polygon T 4 that overlaps the plane π : in this case a clipping procedure is needed to subdivide it in T 4 f and T 4 b .
Figure 10. A ray-polygon intersection can be seen as a line-polygon one by considering only front geometries. Notice the case of the polygon T 4 that overlaps the plane π : in this case a clipping procedure is needed to subdivide it in T 4 f and T 4 b .
Jimaging 07 00096 g010
Figure 11. A triangle clipping example. The points I 1 and I 2 represent the intersections between the edges of the triangle A B C and the plane π . The trapezoid of vertices A I 1 I 2 C is considered in front of the plane, while the triangle I 1 B I 2 behind it.
Figure 11. A triangle clipping example. The points I 1 and I 2 represent the intersections between the edges of the triangle A B C and the plane π . The trapezoid of vertices A I 1 I 2 C is considered in front of the plane, while the triangle I 1 B I 2 behind it.
Jimaging 07 00096 g011
Figure 12. Segment clipping example. The point I 1 is the intersection between the segment A B and the plane π . The segment A I 1 is considered in front of the plane, while B I 1 behind it.
Figure 12. Segment clipping example. The point I 1 is the intersection between the segment A B and the plane π . The segment A I 1 is considered in front of the plane, while B I 1 behind it.
Jimaging 07 00096 g012
Figure 13. Computation time comparison for intersecting 10,000 triangles with an increasing number of rays using Möller-Trumbore and Plücker-based algorithms. (a) Computation time, (b) Ratio between the computation times of the two algorithms.
Figure 13. Computation time comparison for intersecting 10,000 triangles with an increasing number of rays using Möller-Trumbore and Plücker-based algorithms. (a) Computation time, (b) Ratio between the computation times of the two algorithms.
Jimaging 07 00096 g013
Figure 14. Computation time comparison for intersecting an increasing number of triangles with 1000 rays using Möller-Trumbore and Plücker-based algorithms. (a) Computation time, (b) Ratio between the computation times of the two algorithms.
Figure 14. Computation time comparison for intersecting an increasing number of triangles with 1000 rays using Möller-Trumbore and Plücker-based algorithms. (a) Computation time, (b) Ratio between the computation times of the two algorithms.
Jimaging 07 00096 g014
Figure 15. An overview of the 3D models used for numerical tests. (a) Sample 1 consists of 986 triangles, (b) Sample 2 of 1006 triangles and (c) Sample 3 of 9297 triangles.
Figure 15. An overview of the 3D models used for numerical tests. (a) Sample 1 consists of 986 triangles, (b) Sample 2 of 1006 triangles and (c) Sample 3 of 9297 triangles.
Jimaging 07 00096 g015
Figure 16. Computation time comparison of the two algorithms using different settings and samples. (a) shows the results obtained with Plücker VSD, (b) shows the results obtained with MeshLab VSD.
Figure 16. Computation time comparison of the two algorithms using different settings and samples. (a) shows the results obtained with Plücker VSD, (b) shows the results obtained with MeshLab VSD.
Jimaging 07 00096 g016
Figure 17. Misclassification rates comparison of the two algorithms using different settings and samples. (a) shows the results obtained with Plücker VSD, (b) shows the results obtained with MeshLab VSD.
Figure 17. Misclassification rates comparison of the two algorithms using different settings and samples. (a) shows the results obtained with Plücker VSD, (b) shows the results obtained with MeshLab VSD.
Jimaging 07 00096 g017
Figure 18. Convergence comparison of the misclassification error using the two algorithms on Sample 1.
Figure 18. Convergence comparison of the misclassification error using the two algorithms on Sample 1.
Jimaging 07 00096 g018
Figure 19. Misclassification rates comparison using MeshLab VSD algorithm on Sample 3 with outer and inner normals.
Figure 19. Misclassification rates comparison using MeshLab VSD algorithm on Sample 3 with outer and inner normals.
Jimaging 07 00096 g019
Table 1. Detail of times and misclassification rates of VSD performed on Sample 1 by the two algorithms.
Table 1. Detail of times and misclassification rates of VSD performed on Sample 1 by the two algorithms.
Rays|ViewsMeshLab VSDPlücker VSD
Time [s]M. E. Rate [%]Time [s]M. E. Rate [%]
10000.586.392.291.93
25001.274.565.700.61
50002.413.7511.390.61
75003.672.8416.990.30
10,0004.771.7222.660.00
25,00011.741.7244.310.00
50,00024.231.22114.200.00
75,00034.791.22170.500.00
100,00048.511.12226.920.00
200,00091.081.12456.200.00
Publisher’s Note: MDPI stays neutral with regard to jurisdictional claims in published maps and institutional affiliations.

Share and Cite

MDPI and ACS Style

Rossi, A.; Barbiero, M.; Scremin, P.; Carli, R. Robust Visibility Surface Determination in Object Space via Plücker Coordinates. J. Imaging 2021, 7, 96. https://doi.org/10.3390/jimaging7060096

AMA Style

Rossi A, Barbiero M, Scremin P, Carli R. Robust Visibility Surface Determination in Object Space via Plücker Coordinates. Journal of Imaging. 2021; 7(6):96. https://doi.org/10.3390/jimaging7060096

Chicago/Turabian Style

Rossi, Alessandro, Marco Barbiero, Paolo Scremin, and Ruggero Carli. 2021. "Robust Visibility Surface Determination in Object Space via Plücker Coordinates" Journal of Imaging 7, no. 6: 96. https://doi.org/10.3390/jimaging7060096

APA Style

Rossi, A., Barbiero, M., Scremin, P., & Carli, R. (2021). Robust Visibility Surface Determination in Object Space via Plücker Coordinates. Journal of Imaging, 7(6), 96. https://doi.org/10.3390/jimaging7060096

Note that from the first issue of 2016, this journal uses article numbers instead of page numbers. See further details here.

Article Metrics

Back to TopTop