What "non-manifold" actually means in an STL file (and how to count the problems yourself)

An STL file is merely a collection of triangles, each defined by three corner points and a normal. Unlike other file formats, STLs don't encode curves, units, or shared vertices. This lack of structure means that any checks about how triangles connect must be performed manually. To begin, duplicate vertex coordinates must be consolidated into a single point by rounding their values to a specified tolerance.

This process creates a mapping of original vertex coordinates to unique IDs. Subsequently, a second map is generated to tally the occurrence of each edge, represented by a pair of these unique vertex IDs.

With this foundation, three common issues inherent in STL files become apparent. First, the presence of holes can be detected by identifying edges that are only utilized once, indicating an opening in the model's surface. Such holes could arise from unfinished surfaces, incomplete scans, or erroneous deletions. Second, non-manifold edges are recognized when an edge is linked to three or more triangles.

This anomaly often stems from parts of the model that are interlocking or from leftover geometry post-boolean operations. The slicer struggles to determine the internal geometry in these cases, potentially leading to incorrect print results. Third, degenerate triangles, characterized by zero or near-zero area, may be remnants of the export process.

While generally harmless, they can interfere with edge analysis and may trigger repair algorithms in certain slicers.

A model that satisfies the condition of every edge being utilized by precisely two triangles is considered watertight. This state signifies a properly constructed model where no openings or internal inconsistencies exist. However, the process of rectifying an STL file isn't without its limitations. While certain repairs, such as merging close vertices or eliminating zero-area triangles, are non-destructive and safe, other corrective measures, like filling gaps, necessitate human intervention due to the subjective nature of the decisions involved.

Additionally, non-manifold geometries, self-intersecting triangles, and shells with incorrectly oriented triangles may not be addressed by simple edge counting methods. Thus, while the outlined steps provide a foundational approach to diagnosing and fixing STL file issues, additional scrutiny is required for more complex geometrical anomalies.