[cig-commits] r16109 - in short/3D/PyLith/trunk/playpen/friction: . twohex8 twotet4 twotri3
brad at geodynamics.org
brad at geodynamics.org
Fri Dec 18 09:47:15 PST 2009
Author: brad
Date: 2009-12-18 09:47:14 -0800 (Fri, 18 Dec 2009)
New Revision: 16109
Added:
short/3D/PyLith/trunk/playpen/friction/twotet4/
short/3D/PyLith/trunk/playpen/friction/twotet4/twotet4.mesh
short/3D/PyLith/trunk/playpen/friction/twotri3/
short/3D/PyLith/trunk/playpen/friction/twotri3/twotri3.mesh
Removed:
short/3D/PyLith/trunk/playpen/friction/tet4/
short/3D/PyLith/trunk/playpen/friction/tri3/
short/3D/PyLith/trunk/playpen/friction/twotet4/tet4.mesh
short/3D/PyLith/trunk/playpen/friction/twotri3/tri3.mesh
Modified:
short/3D/PyLith/trunk/playpen/friction/twohex8/compression.cfg
short/3D/PyLith/trunk/playpen/friction/twohex8/shear-sliding.cfg
short/3D/PyLith/trunk/playpen/friction/twohex8/shear-stick.cfg
short/3D/PyLith/trunk/playpen/friction/twotet4/compression.cfg
short/3D/PyLith/trunk/playpen/friction/twotet4/opening.cfg
short/3D/PyLith/trunk/playpen/friction/twotet4/shear-sliding.cfg
short/3D/PyLith/trunk/playpen/friction/twotet4/shear-stick.cfg
short/3D/PyLith/trunk/playpen/friction/twotri3/compression.cfg
short/3D/PyLith/trunk/playpen/friction/twotri3/opening.cfg
short/3D/PyLith/trunk/playpen/friction/twotri3/shear-sliding.cfg
short/3D/PyLith/trunk/playpen/friction/twotri3/shear-stick.cfg
Log:
Cleanup of filenames.
Modified: short/3D/PyLith/trunk/playpen/friction/twohex8/compression.cfg
===================================================================
--- short/3D/PyLith/trunk/playpen/friction/twohex8/compression.cfg 2009-12-18 01:09:54 UTC (rev 16108)
+++ short/3D/PyLith/trunk/playpen/friction/twohex8/compression.cfg 2009-12-18 17:47:14 UTC (rev 16109)
@@ -172,14 +172,14 @@
# ----------------------------------------------------------------------
# Give basename for VTK domain output of solution over domain.
[pylithapp.problem.formulation.output.output.writer]
-filename = twohex8-axial.vtk
+filename = compression.vtk
# Give basename for VTK fault output.
[pylithapp.timedependent.interfaces.fault.output]
-writer.filename = twohex8-axial-fault.vtk
+writer.filename = compression-fault.vtk
vertex_info_fields = [strike_dir,normal_dir,dip_dir,initial_traction]
# Give basename for VTK output of state variables.
[pylithapp.timedependent.materials.material.output]
cell_filter = pylith.meshio.CellFilterAvgMesh
-writer.filename = twohex8-axial-statevars.vtk
+writer.filename = compression-statevars.vtk
Modified: short/3D/PyLith/trunk/playpen/friction/twohex8/shear-sliding.cfg
===================================================================
--- short/3D/PyLith/trunk/playpen/friction/twohex8/shear-sliding.cfg 2009-12-18 01:09:54 UTC (rev 16108)
+++ short/3D/PyLith/trunk/playpen/friction/twohex8/shear-sliding.cfg 2009-12-18 17:47:14 UTC (rev 16109)
@@ -107,11 +107,6 @@
db_initial.data = [0.0*m,1.8*m,2.4*m]
-
-
-
-
-
# Boundary conditions to be applied to the positive y-side of the mesh.
[pylithapp.timedependent.bc.y_pos]
@@ -238,14 +233,14 @@
# ----------------------------------------------------------------------
# Give basename for VTK domain output of solution over domain.
[pylithapp.problem.formulation.output.output.writer]
-filename = twohex8-shear-sliding.vtk
+filename = shear-sliding.vtk
# Give basename for VTK fault output.
[pylithapp.timedependent.interfaces.fault.output]
-writer.filename = twohex8-shear-sliding-fault.vtk
+writer.filename = shear-sliding-fault.vtk
vertex_info_fields = [strike_dir,normal_dir,dip_dir,initial_traction]
# Give basename for VTK output of state variables.
[pylithapp.timedependent.materials.material.output]
cell_filter = pylith.meshio.CellFilterAvgMesh
-writer.filename = twohex8-shear-sliding-statevars.vtk
+writer.filename = shear-sliding-statevars.vtk
Modified: short/3D/PyLith/trunk/playpen/friction/twohex8/shear-stick.cfg
===================================================================
--- short/3D/PyLith/trunk/playpen/friction/twohex8/shear-stick.cfg 2009-12-18 01:09:54 UTC (rev 16108)
+++ short/3D/PyLith/trunk/playpen/friction/twohex8/shear-stick.cfg 2009-12-18 17:47:14 UTC (rev 16109)
@@ -250,14 +250,14 @@
# ----------------------------------------------------------------------
# Give basename for VTK domain output of solution over domain.
[pylithapp.problem.formulation.output.output.writer]
-filename = twohex8-shear-stick.vtk
+filename = shear-stick.vtk
# Give basename for VTK fault output.
[pylithapp.timedependent.interfaces.fault.output]
-writer.filename = twohex8-shear-stick-fault.vtk
+writer.filename = shear-stick-fault.vtk
vertex_info_fields = [strike_dir,normal_dir,dip_dir,initial_traction]
# Give basename for VTK output of state variables.
[pylithapp.timedependent.materials.material.output]
cell_filter = pylith.meshio.CellFilterAvgMesh
-writer.filename = twohex8-shear-stick-statevars.vtk
+writer.filename = shear-stick-statevars.vtk
Copied: short/3D/PyLith/trunk/playpen/friction/twotet4 (from rev 16108, short/3D/PyLith/trunk/playpen/friction/tet4)
Modified: short/3D/PyLith/trunk/playpen/friction/twotet4/compression.cfg
===================================================================
--- short/3D/PyLith/trunk/playpen/friction/tet4/compression.cfg 2009-12-18 01:09:54 UTC (rev 16108)
+++ short/3D/PyLith/trunk/playpen/friction/twotet4/compression.cfg 2009-12-18 17:47:14 UTC (rev 16109)
@@ -23,7 +23,7 @@
debug = 0
[pylithapp.mesh_generator.reader]
-filename = tet4.mesh
+filename = twotet4.mesh
coordsys.space_dim = 3
# ----------------------------------------------------------------------
@@ -172,14 +172,14 @@
# ----------------------------------------------------------------------
# Give basename for VTK domain output of solution over domain.
[pylithapp.problem.formulation.output.output.writer]
-filename = tet4-axial.vtk
+filename = compression.vtk
# Give basename for VTK fault output.
[pylithapp.timedependent.interfaces.fault.output]
-writer.filename = tet4-axial-fault.vtk
+writer.filename = compression-fault.vtk
vertex_info_fields = [strike_dir,normal_dir,dip_dir,initial_traction]
# Give basename for VTK output of state variables.
[pylithapp.timedependent.materials.material.output]
cell_filter = pylith.meshio.CellFilterAvgMesh
-writer.filename = tet4-axial-statevars.vtk
+writer.filename = compression-statevars.vtk
Modified: short/3D/PyLith/trunk/playpen/friction/twotet4/opening.cfg
===================================================================
--- short/3D/PyLith/trunk/playpen/friction/tet4/opening.cfg 2009-12-18 01:09:54 UTC (rev 16108)
+++ short/3D/PyLith/trunk/playpen/friction/twotet4/opening.cfg 2009-12-18 17:47:14 UTC (rev 16109)
@@ -23,7 +23,7 @@
debug = 0
[pylithapp.mesh_generator.reader]
-filename = tet4.mesh
+filename = twotet4.mesh
coordsys.space_dim = 3
# ----------------------------------------------------------------------
@@ -150,14 +150,14 @@
# ----------------------------------------------------------------------
# Give basename for VTK domain output of solution over domain.
[pylithapp.problem.formulation.output.output.writer]
-filename = tet4-opening.vtk
+filename = opening.vtk
# Give basename for VTK fault output.
[pylithapp.timedependent.interfaces.fault.output]
-writer.filename = tet4-opening-fault.vtk
+writer.filename = opening-fault.vtk
vertex_info_fields = [strike_dir,normal_dir,dip_dir,initial_traction]
# Give basename for VTK output of state variables.
[pylithapp.timedependent.materials.material.output]
cell_filter = pylith.meshio.CellFilterAvgMesh
-writer.filename = tet4-opening-statevars.vtk
+writer.filename = opening-statevars.vtk
Modified: short/3D/PyLith/trunk/playpen/friction/twotet4/shear-sliding.cfg
===================================================================
--- short/3D/PyLith/trunk/playpen/friction/tet4/shear-sliding.cfg 2009-12-18 01:09:54 UTC (rev 16108)
+++ short/3D/PyLith/trunk/playpen/friction/twotet4/shear-sliding.cfg 2009-12-18 17:47:14 UTC (rev 16109)
@@ -23,7 +23,7 @@
debug = 0
[pylithapp.mesh_generator.reader]
-filename = tet4.mesh
+filename = twotet4.mesh
coordsys.space_dim = 3
# ----------------------------------------------------------------------
@@ -145,8 +145,6 @@
quadrature.cell.shape = triangle
-
-
# Boundary conditions to be applied to the positive z-side of the mesh.
[pylithapp.timedependent.bc.z_pos]
@@ -237,14 +235,14 @@
# ----------------------------------------------------------------------
# Give basename for VTK domain output of solution over domain.
[pylithapp.problem.formulation.output.output.writer]
-filename = tet4-shear-sliding.vtk
+filename = shear-sliding.vtk
# Give basename for VTK fault output.
[pylithapp.timedependent.interfaces.fault.output]
-writer.filename = tet4-shear-sliding-fault.vtk
+writer.filename = shear-sliding-fault.vtk
vertex_info_fields = [strike_dir,normal_dir,dip_dir,initial_traction]
# Give basename for VTK output of state variables.
[pylithapp.timedependent.materials.material.output]
cell_filter = pylith.meshio.CellFilterAvgMesh
-writer.filename = tet4-shear-sliding-statevars.vtk
+writer.filename = shear-sliding-statevars.vtk
Modified: short/3D/PyLith/trunk/playpen/friction/twotet4/shear-stick.cfg
===================================================================
--- short/3D/PyLith/trunk/playpen/friction/tet4/shear-stick.cfg 2009-12-18 01:09:54 UTC (rev 16108)
+++ short/3D/PyLith/trunk/playpen/friction/twotet4/shear-stick.cfg 2009-12-18 17:47:14 UTC (rev 16109)
@@ -23,7 +23,7 @@
debug = 0
[pylithapp.mesh_generator.reader]
-filename = tet4.mesh
+filename = twotet4.mesh
coordsys.space_dim = 3
# ----------------------------------------------------------------------
@@ -250,14 +250,14 @@
# ----------------------------------------------------------------------
# Give basename for VTK domain output of solution over domain.
[pylithapp.problem.formulation.output.output.writer]
-filename = tet4-shear-stick.vtk
+filename = shear-stick.vtk
# Give basename for VTK fault output.
[pylithapp.timedependent.interfaces.fault.output]
-writer.filename = tet4-shear-stick-fault.vtk
+writer.filename = shear-stick-fault.vtk
vertex_info_fields = [strike_dir,normal_dir,dip_dir,initial_traction]
# Give basename for VTK output of state variables.
[pylithapp.timedependent.materials.material.output]
cell_filter = pylith.meshio.CellFilterAvgMesh
-writer.filename = tet4-shear-stick-statevars.vtk
+writer.filename = shear-stick-statevars.vtk
Deleted: short/3D/PyLith/trunk/playpen/friction/twotet4/tet4.mesh
===================================================================
--- short/3D/PyLith/trunk/playpen/friction/tet4/tet4.mesh 2009-12-18 01:09:54 UTC (rev 16108)
+++ short/3D/PyLith/trunk/playpen/friction/twotet4/tet4.mesh 2009-12-18 17:47:14 UTC (rev 16109)
@@ -1,176 +0,0 @@
-// Global mesh object.
-// This defines a brick-shaped mesh composed of two cubic elements.
-mesh = {
-
- // This is a 3D mesh.
- dimension = 3
-
- // We are using zero-indexing (default) rather than one-indexing.
- use-index-zero = true
-
- // Describe the vertices (nodes) defining the mesh.
- vertices = {
-
- // The vertices are defined in a 3D coordinate system.
- dimension = 3
-
- // There are 12 vertices.
- count = 12
-
- // List the coordinates as:
- // Vertex number (starting from zero), x-coord, y-coord, z-coord
- // Use coordinate units that are consistent with the other units used.
- coordinates = {
- 0 -1.0 -0.5 -0.5
- 1 -1.0 0.5 -0.5
- 2 0.0 -0.5 -0.5
- 3 0.0 0.5 -0.5
- 4 1.0 -0.5 -0.5
- 5 1.0 0.5 -0.5
- 6 -1.0 -0.5 0.5
- 7 -1.0 0.5 0.5
- 8 0.0 -0.5 0.5
- 9 0.0 0.5 0.5
- 10 1.0 -0.5 0.5
- 11 1.0 0.5 0.5
- }
- }
-
- // Describe the cells (elements) composing the mesh.
- cells = {
-
- // There are 12 cells.
- count = 12
-
- // These are trilinear hexahedral cells, so there are 4 corners per cell.
- num-corners = 4
-
- // List the vertices composing each cell (see manual for ordering).
- // List the information as:
- // Cell number (starting from zero), vertex 0, vertex 1, etc.
- simplices = {
- 0 8 1 0 7
- 1 8 1 7 9
- 2 8 1 9 2
- 3 8 1 2 0
- 4 0 8 7 6
- 5 1 9 2 3
- 6 8 4 5 11
- 7 8 11 5 9
- 8 8 9 5 2
- 9 8 2 5 4
- 10 4 11 8 10
- 11 5 2 9 3
- }
-
- // List the material ID's associated with each cell.
- // Different ID's may be used to specify a different material type, or
- // to use a different spatial database for each material ID.
- // In this example, cells 0 and 1 both are associated with material ID 1.
- material-ids = {
- 0 1
- 1 1
- 2 1
- 3 1
- 4 1
- 5 1
- 6 1
- 7 1
- 8 1
- 9 1
- 10 1
- 11 1
- }
- }
-
- // Here we list different groups (cells or vertices) that we want to associate
- // with a particular name (ID).
-
- // This group of vertices may be used to define a fault.
- // There are 4 vertices corresponding to indices 2, 3, 8, and 9.
- group = {
- name = fault
- type = vertices
- count = 4
- indices = {
- 2
- 3
- 8
- 9
- }
- }
-
- group = {
- name = x_neg
- type = vertices
- count = 4
- indices = {
- 0 1 6 7
- }
- }
-
- group = {
- name = x_pos
- type = vertices
- count = 4
- indices = {
- 4 5 10 11
- }
- }
-
- group = {
- name = y_neg
- type = vertices
- count = 6
- indices = {
- 0 2 4 6 8 10
- }
- }
-
- group = {
- name = y_pos
- type = vertices
- count = 6
- indices = {
- 1 3 5 7 9 11
- }
- }
-
- // y_neg with fault vertices removed
- group = {
- name = y_neg_nofault
- type = vertices
- count = 4
- indices = {
- 0 4 6 10
- }
- }
-
- group = {
- name = z_neg
- type = vertices
- count = 6
- indices = {
- 0 1 2 3 4 5
- }
- }
-
- group = {
- name = z_pos
- type = vertices
- count = 6
- indices = {
- 6 7 8 9 10 11
- }
- }
-
- // z_neg with fault vertices removed
- group = {
- name = z_neg_nofault
- type = vertices
- count = 4
- indices = {
- 0 1 4 5
- }
- }
-}
Copied: short/3D/PyLith/trunk/playpen/friction/twotet4/twotet4.mesh (from rev 16108, short/3D/PyLith/trunk/playpen/friction/tet4/tet4.mesh)
===================================================================
--- short/3D/PyLith/trunk/playpen/friction/twotet4/twotet4.mesh (rev 0)
+++ short/3D/PyLith/trunk/playpen/friction/twotet4/twotet4.mesh 2009-12-18 17:47:14 UTC (rev 16109)
@@ -0,0 +1,176 @@
+// Global mesh object.
+// This defines a brick-shaped mesh composed of two cubic elements.
+mesh = {
+
+ // This is a 3D mesh.
+ dimension = 3
+
+ // We are using zero-indexing (default) rather than one-indexing.
+ use-index-zero = true
+
+ // Describe the vertices (nodes) defining the mesh.
+ vertices = {
+
+ // The vertices are defined in a 3D coordinate system.
+ dimension = 3
+
+ // There are 12 vertices.
+ count = 12
+
+ // List the coordinates as:
+ // Vertex number (starting from zero), x-coord, y-coord, z-coord
+ // Use coordinate units that are consistent with the other units used.
+ coordinates = {
+ 0 -1.0 -0.5 -0.5
+ 1 -1.0 0.5 -0.5
+ 2 0.0 -0.5 -0.5
+ 3 0.0 0.5 -0.5
+ 4 1.0 -0.5 -0.5
+ 5 1.0 0.5 -0.5
+ 6 -1.0 -0.5 0.5
+ 7 -1.0 0.5 0.5
+ 8 0.0 -0.5 0.5
+ 9 0.0 0.5 0.5
+ 10 1.0 -0.5 0.5
+ 11 1.0 0.5 0.5
+ }
+ }
+
+ // Describe the cells (elements) composing the mesh.
+ cells = {
+
+ // There are 12 cells.
+ count = 12
+
+ // These are trilinear hexahedral cells, so there are 4 corners per cell.
+ num-corners = 4
+
+ // List the vertices composing each cell (see manual for ordering).
+ // List the information as:
+ // Cell number (starting from zero), vertex 0, vertex 1, etc.
+ simplices = {
+ 0 8 1 0 7
+ 1 8 1 7 9
+ 2 8 1 9 2
+ 3 8 1 2 0
+ 4 0 8 7 6
+ 5 1 9 2 3
+ 6 8 4 5 11
+ 7 8 11 5 9
+ 8 8 9 5 2
+ 9 8 2 5 4
+ 10 4 11 8 10
+ 11 5 2 9 3
+ }
+
+ // List the material ID's associated with each cell.
+ // Different ID's may be used to specify a different material type, or
+ // to use a different spatial database for each material ID.
+ // In this example, cells 0 and 1 both are associated with material ID 1.
+ material-ids = {
+ 0 1
+ 1 1
+ 2 1
+ 3 1
+ 4 1
+ 5 1
+ 6 1
+ 7 1
+ 8 1
+ 9 1
+ 10 1
+ 11 1
+ }
+ }
+
+ // Here we list different groups (cells or vertices) that we want to associate
+ // with a particular name (ID).
+
+ // This group of vertices may be used to define a fault.
+ // There are 4 vertices corresponding to indices 2, 3, 8, and 9.
+ group = {
+ name = fault
+ type = vertices
+ count = 4
+ indices = {
+ 2
+ 3
+ 8
+ 9
+ }
+ }
+
+ group = {
+ name = x_neg
+ type = vertices
+ count = 4
+ indices = {
+ 0 1 6 7
+ }
+ }
+
+ group = {
+ name = x_pos
+ type = vertices
+ count = 4
+ indices = {
+ 4 5 10 11
+ }
+ }
+
+ group = {
+ name = y_neg
+ type = vertices
+ count = 6
+ indices = {
+ 0 2 4 6 8 10
+ }
+ }
+
+ group = {
+ name = y_pos
+ type = vertices
+ count = 6
+ indices = {
+ 1 3 5 7 9 11
+ }
+ }
+
+ // y_neg with fault vertices removed
+ group = {
+ name = y_neg_nofault
+ type = vertices
+ count = 4
+ indices = {
+ 0 4 6 10
+ }
+ }
+
+ group = {
+ name = z_neg
+ type = vertices
+ count = 6
+ indices = {
+ 0 1 2 3 4 5
+ }
+ }
+
+ group = {
+ name = z_pos
+ type = vertices
+ count = 6
+ indices = {
+ 6 7 8 9 10 11
+ }
+ }
+
+ // z_neg with fault vertices removed
+ group = {
+ name = z_neg_nofault
+ type = vertices
+ count = 4
+ indices = {
+ 0 1 4 5
+ }
+ }
+}
Copied: short/3D/PyLith/trunk/playpen/friction/twotri3 (from rev 16108, short/3D/PyLith/trunk/playpen/friction/tri3)
Modified: short/3D/PyLith/trunk/playpen/friction/twotri3/compression.cfg
===================================================================
--- short/3D/PyLith/trunk/playpen/friction/tri3/compression.cfg 2009-12-18 01:09:54 UTC (rev 16108)
+++ short/3D/PyLith/trunk/playpen/friction/twotri3/compression.cfg 2009-12-18 17:47:14 UTC (rev 16109)
@@ -23,7 +23,7 @@
debug = 0
[pylithapp.mesh_generator.reader]
-filename = tri3.mesh
+filename = twotri3.mesh
coordsys.space_dim = 2
# ----------------------------------------------------------------------
Modified: short/3D/PyLith/trunk/playpen/friction/twotri3/opening.cfg
===================================================================
--- short/3D/PyLith/trunk/playpen/friction/tri3/opening.cfg 2009-12-18 01:09:54 UTC (rev 16108)
+++ short/3D/PyLith/trunk/playpen/friction/twotri3/opening.cfg 2009-12-18 17:47:14 UTC (rev 16109)
@@ -41,7 +41,7 @@
# and we then specify the filename and number of space dimensions for
# the mesh.
[pylithapp.mesh_generator.reader]
-filename = tri3.mesh
+filename = twotri3.mesh
coordsys.space_dim = 2
# ----------------------------------------------------------------------
Modified: short/3D/PyLith/trunk/playpen/friction/twotri3/shear-sliding.cfg
===================================================================
--- short/3D/PyLith/trunk/playpen/friction/tri3/shear-sliding.cfg 2009-12-18 01:09:54 UTC (rev 16108)
+++ short/3D/PyLith/trunk/playpen/friction/twotri3/shear-sliding.cfg 2009-12-18 17:47:14 UTC (rev 16109)
@@ -41,7 +41,7 @@
# and we then specify the filename and number of space dimensions for
# the mesh.
[pylithapp.mesh_generator.reader]
-filename = tri3.mesh
+filename = twotri3.mesh
coordsys.space_dim = 2
# ----------------------------------------------------------------------
Modified: short/3D/PyLith/trunk/playpen/friction/twotri3/shear-stick.cfg
===================================================================
--- short/3D/PyLith/trunk/playpen/friction/tri3/shear-stick.cfg 2009-12-18 01:09:54 UTC (rev 16108)
+++ short/3D/PyLith/trunk/playpen/friction/twotri3/shear-stick.cfg 2009-12-18 17:47:14 UTC (rev 16109)
@@ -41,7 +41,7 @@
# and we then specify the filename and number of space dimensions for
# the mesh.
[pylithapp.mesh_generator.reader]
-filename = tri3.mesh
+filename = twotri3.mesh
coordsys.space_dim = 2
# ----------------------------------------------------------------------
Deleted: short/3D/PyLith/trunk/playpen/friction/twotri3/tri3.mesh
===================================================================
--- short/3D/PyLith/trunk/playpen/friction/tri3/tri3.mesh 2009-12-18 01:09:54 UTC (rev 16108)
+++ short/3D/PyLith/trunk/playpen/friction/twotri3/tri3.mesh 2009-12-18 17:47:14 UTC (rev 16109)
@@ -1,163 +0,0 @@
-// Finite-element mesh with two quad4 cells.
-//
-//
-// 1 ----- 3 ----- 5
-// | | |
-// | | |
-// | | |
-// 0 ----- 2 ----- 4
-//
-// Each edge has a length of 1.0.
-//
-mesh = {
-
- // Dimenion associated with topology of mesh.
- dimension = 2
-
- // We are using zero-based indexing (default, C style) rather than
- // one-based (Fortran style) indexing.
- use-index-zero = true
-
- // Vertices in the mesh.
- vertices = {
-
- // Dimension of coordinate system for vertices.
- dimension = 2
-
- // Number of vertices in mesh.
- count = 6
-
- // Coordinates are listed as:
- // Vertex number (starting from zero), x-coord, y-coord
- // Use coordinate units that are consistent with the other units used.
- coordinates = {
- 0 -1.0 -0.5
- 1 -1.0 0.5
- 2 0.0 -0.5
- 3 0.0 0.5
- 4 1.0 -0.5
- 5 1.0 0.5
- }
- }
-
- // Finite-element cells in the mesh.
- cells = {
-
- // There are 4 cells.
- count = 4
-
- // These are linear triangular cells, so there are 3 corners per cell.
- num-corners = 3
-
- // List the vertices composing each cell,
- // moving counter-clockwise around the cell.
- // List the information as:
- // Cell number (starting from zero), vertex 0, vertex 1, vertex 2
- simplices = {
- 0 0 2 1
- 1 2 3 1
- 2 4 5 2
- 3 5 3 2
- }
-
- // List the material ID's associated with each cell.
- // Different ID's may be used to specify a different material type, or
- // to use a different spatial database for each material ID.
- // In this example, cells 0 and 1 both are associated with material ID 0.
- material-ids = {
- 0 0
- 1 0
- 2 0
- 3 0
- }
- }
-
- // Here we list different groups (cells or vertices) that we want to
- // associate with a particular name.
-
- // This group of vertices may be used to define a fault.
- // There are 2 vertices corresponding to indices 2 and 3.
- group = {
- name = fault
- type = vertices
- count = 2
- indices = {
- 2
- 3
- }
- }
-
- // This group of vertices may be used to specify boundary conditions.
- // There are 2 vertices corresponding to indices 0 and 4.
- group = {
- name = y_neg
- type = vertices
- count = 2
- indices = {
- 0
- 4
- }
- }
-
- // This group of vertices may be used to specify boundary conditions.
- // There are 3 vertices corresponding to indices 0, 2, and 4.
- group = {
- name = y_neg_fault
- type = vertices
- count = 3
- indices = {
- 0
- 2
- 4
- }
- }
-
- // This group of vertices may be used to specify boundary conditions.
- // There are 2 vertices corresponding to indices 0 and 1.
- group = {
- name = x_neg
- type = vertices
- count = 2
- indices = {
- 0
- 1
- }
- }
-
- // This group of vertices may be used to specify boundary conditions.
- // There are 2 vertices corresponding to indices 4 and 5.
- group = {
- name = x_pos
- type = vertices
- count = 2
- indices = {
- 4
- 5
- }
- }
-
- // This group of vertices may be used to specify boundary conditions.
- // There is 2 vertex corresponding to index 3 and 5.
- group = {
- name = y_pos
- type = vertices
- count = 2
- indices = {
- 1
- 5
- }
- }
-
- // This group of vertices may be used to specify boundary conditions.
- // There is 3 vertex corresponding to index 1, 3 and 5.
- group = {
- name = y_pos_fault
- type = vertices
- count = 3
- indices = {
- 1
- 3
- 5
- }
- }
-}
Copied: short/3D/PyLith/trunk/playpen/friction/twotri3/twotri3.mesh (from rev 16108, short/3D/PyLith/trunk/playpen/friction/tri3/tri3.mesh)
===================================================================
--- short/3D/PyLith/trunk/playpen/friction/twotri3/twotri3.mesh (rev 0)
+++ short/3D/PyLith/trunk/playpen/friction/twotri3/twotri3.mesh 2009-12-18 17:47:14 UTC (rev 16109)
@@ -0,0 +1,163 @@
+// Finite-element mesh with two quad4 cells.
+//
+//
+// 1 ----- 3 ----- 5
+// | | |
+// | | |
+// | | |
+// 0 ----- 2 ----- 4
+//
+// Each edge has a length of 1.0.
+//
+mesh = {
+
+ // Dimenion associated with topology of mesh.
+ dimension = 2
+
+ // We are using zero-based indexing (default, C style) rather than
+ // one-based (Fortran style) indexing.
+ use-index-zero = true
+
+ // Vertices in the mesh.
+ vertices = {
+
+ // Dimension of coordinate system for vertices.
+ dimension = 2
+
+ // Number of vertices in mesh.
+ count = 6
+
+ // Coordinates are listed as:
+ // Vertex number (starting from zero), x-coord, y-coord
+ // Use coordinate units that are consistent with the other units used.
+ coordinates = {
+ 0 -1.0 -0.5
+ 1 -1.0 0.5
+ 2 0.0 -0.5
+ 3 0.0 0.5
+ 4 1.0 -0.5
+ 5 1.0 0.5
+ }
+ }
+
+ // Finite-element cells in the mesh.
+ cells = {
+
+ // There are 4 cells.
+ count = 4
+
+ // These are linear triangular cells, so there are 3 corners per cell.
+ num-corners = 3
+
+ // List the vertices composing each cell,
+ // moving counter-clockwise around the cell.
+ // List the information as:
+ // Cell number (starting from zero), vertex 0, vertex 1, vertex 2
+ simplices = {
+ 0 0 2 1
+ 1 2 3 1
+ 2 4 5 2
+ 3 5 3 2
+ }
+
+ // List the material ID's associated with each cell.
+ // Different ID's may be used to specify a different material type, or
+ // to use a different spatial database for each material ID.
+ // In this example, cells 0 and 1 both are associated with material ID 0.
+ material-ids = {
+ 0 0
+ 1 0
+ 2 0
+ 3 0
+ }
+ }
+
+ // Here we list different groups (cells or vertices) that we want to
+ // associate with a particular name.
+
+ // This group of vertices may be used to define a fault.
+ // There are 2 vertices corresponding to indices 2 and 3.
+ group = {
+ name = fault
+ type = vertices
+ count = 2
+ indices = {
+ 2
+ 3
+ }
+ }
+
+ // This group of vertices may be used to specify boundary conditions.
+ // There are 2 vertices corresponding to indices 0 and 4.
+ group = {
+ name = y_neg
+ type = vertices
+ count = 2
+ indices = {
+ 0
+ 4
+ }
+ }
+
+ // This group of vertices may be used to specify boundary conditions.
+ // There are 3 vertices corresponding to indices 0, 2, and 4.
+ group = {
+ name = y_neg_fault
+ type = vertices
+ count = 3
+ indices = {
+ 0
+ 2
+ 4
+ }
+ }
+
+ // This group of vertices may be used to specify boundary conditions.
+ // There are 2 vertices corresponding to indices 0 and 1.
+ group = {
+ name = x_neg
+ type = vertices
+ count = 2
+ indices = {
+ 0
+ 1
+ }
+ }
+
+ // This group of vertices may be used to specify boundary conditions.
+ // There are 2 vertices corresponding to indices 4 and 5.
+ group = {
+ name = x_pos
+ type = vertices
+ count = 2
+ indices = {
+ 4
+ 5
+ }
+ }
+
+ // This group of vertices may be used to specify boundary conditions.
+ // There is 2 vertex corresponding to index 3 and 5.
+ group = {
+ name = y_pos
+ type = vertices
+ count = 2
+ indices = {
+ 1
+ 5
+ }
+ }
+
+ // This group of vertices may be used to specify boundary conditions.
+ // There is 3 vertex corresponding to index 1, 3 and 5.
+ group = {
+ name = y_pos_fault
+ type = vertices
+ count = 3
+ indices = {
+ 1
+ 3
+ 5
+ }
+ }
+}
More information about the CIG-COMMITS
mailing list