|Mesh||# nodes||# elements||All files (.node, .ele, .part)||.node files||.ele files||.part files (1-128 subdomains)|
|sf10||7,294||35,025||1.7M||.06M||.7M||1 |2 |4 |8 |16 |32 |64 |128 (.1M each)|
|sf5||30,169||151,173||7M||.25M||3M||1 |2 |4 |8 |16 |32 |64 |128 (.45M each)|
|sf2||378,747||2,067,739||100M||3M||43M||1 |2 |4 |8 |16 |32 |64 |128 (6M each)|
|sf1||2,461,694||13,980,162||630M||20M||285M||1 |2 |4 |8 |16 |32 |64 |128 (40M each)|
A mesh is represented with two ASCII files in the Triangle format. The .node file contains the nodes in the mesh and their geometric coordinates. The .ele file contains the linear tetrahedral elements that comprise the mesh, and the nodes that comprise the corners of each element.
The meshes are partitioned into disjoint sets of elements using a geometric recursive bisection algorithm due to Miller, Teng, Thurston, and Vavasis. Each partition is described by an ASCII .part file, which lists the mapping of elements to subdomains. The formats of all files are described below.
The partitioned meshes can be displayed, manipulated, and saved as encapsulated color Postscript files using the X Windows based Showme program, which is distributed freely with the CMU Triangle Delaunay-based mesh generator program via Netlib.
Blank lines and comments prefixed by `#' may be placed anywhere. Nodes are numbered consecutively starting from one.
Each SF .node file contains two integer boundary markers that are artifacts of the specific solver we used to simulate the Northridge earthquake. They should be ignored.
The 3 attributes are floating-point material properties.