Edgebreaker
Software
The Edgebreaker software is divided into two modules: EBCompression
and EBDecompression. The software is based on the Edgebreaker compression
technique developed by Prof. Rossignac and his
colleagues. Please see the 2.5
page pseudo-code (PDF)
for details.
To help us track of usage of Edgebreaker and keep you
inform of the latest development, please email to a brief description of your
application, the name of your organization, and your name and position to jarek@cc.gatech.edu. Thank you.
Two mesh types are currently supported: MANIFOLD and TPATCH.
-
A TPATCH is a manifold mesh with
a single manifold bounding curve. To simplify compression, we ask that the
application adds a dummy vertex to the mesh and creates a fan of dummy
triangles that connect the dummy vertex with the edges of the hole. On of the
corners incident upon that dummy vertex should be passed as argument to the
compression routine. After decompression, the client application is responsible
for discarding the dummy vertex and its incident triangles. The dummy vertex
will be vertex 0 in the decompressed mesh. Note that Edgebreaker does not
encode the dummy vertex nor the dummy triangles. A flag in the header of the
file and the count of the edges in the hole suffice to reconstruct them.
1.
OVTable: The Corner
Table containing the connectivity and geometry of the mesh in OVTable
format
2.
MeshType: MANIFOLD or TPATCH
-
MANIFOLD - a
consistently oriented, manifold Triangle mesh, without boundary.
-
TPATCH - a manifold mesh
with a single hole that has been closed with dummy vertices and triangles
3.
StartCorner: Is the
corner where to start EBCompression.
-
If MeshType is TPATCH it should be a
corner corresponding to the dummy vertex.
-
If MeshType is MANIFOLD, it can be any
corner, but since the triangles incident on StartCorner are not stored it is advantageous to pass a
corner with the maximum number of incident triangles.
4.
FileFormat: BINARY or
ASCII
1.
InputFileDir: Directory with clers.txt handles.txt
vertices.txt
2.
OutFileName: Name of output file
3.
Input file format (BINARY or ASCII)