


4 vertices and 4 triangular faces.

8 vertices and 12 triangular faces.

I choose color1 = (0, 0, 1) (blue) for the front of the cow, the vertex with the
smallest z, and color2 = (1, 0, 0) (red) for the back

R_relative = Rz(-90), T_relative = (0, 0, 0).
R_relative rolls the camera
90 degrees but T_relative does nothing. The camera
stays where it is and the cow rotates.

R_relative = I, T_relative = (0, 0, 2).
To make the cow smaller, I defined R_relative as doing nothing where as
T_relative put the camera 2 units back.

R_relative = I, T_relative = (0.5, -0.5, 0).
The cow is facing slightly left but the pose remains the same. So R_relative should be doing nothing and tweak
T_relative.

R_relative = Ry(90), T_relative = (-3, 0, 3).
Ry(90) rotate the camera by 90 degree. But without a corresponding change to the translation, the cow completely falls outside the view. So we need to move camera back using T_relative.





The new object is an ellipsoid, (x/a)^2 + (y/b)^2 + (z/c)^2 - 1 = 0, with
semi-axes a, b, c = 0.4, 0.8, 1.2.
Rendering quality. Comparing two donuts side by side, the mesh is having a better quality as the surface is generally smooth. It's easy to see holes for the point cloud one and we can sometime even look through it.
Rendering speed. Comparing the render speed: the mesh is faster of the two, by 2.5x. Measured on the same torus at 256x256 on CPU: 1.42 s per frame for the mesh against 3.60 s for the point cloud.
Ease of use. We can easily get point clouds from sensors, just like what we did for the plant. But in terms of rendering as mesh vs. as point cloud, I think it is not so much different.
Memory. For this torus the point cloud is 938 KB and the mesh 754 KB. The implicit function is a few bytes of code, but discretizing it costs O(n^3) memory to make a 3D grids: the 64^3 grid alone is 1024 KB, larger than either thing it produces.

The XYZ RGB Dragon (249,882 triangles) from the Stanford 3D Scanning Repository, via Alec Jacobson's common-3d-test-models.