[cig-commits] r16052 - short/3D/PyLith/branches/pylith-friction/playpen/friction
surendra at geodynamics.org
surendra at geodynamics.org
Sun Nov 29 22:11:31 PST 2009
Author: surendra
Date: 2009-11-29 22:11:30 -0800 (Sun, 29 Nov 2009)
New Revision: 16052
Added:
short/3D/PyLith/branches/pylith-friction/playpen/friction/twohex8-shear-sliding.cfg
short/3D/PyLith/branches/pylith-friction/playpen/friction/twohex8-shear-stick.cfg
short/3D/PyLith/branches/pylith-friction/playpen/friction/twoquad4-shear-sliding.cfg
short/3D/PyLith/branches/pylith-friction/playpen/friction/twoquad4-shear-stick.cfg
Removed:
short/3D/PyLith/branches/pylith-friction/playpen/friction/twohex8-shear-DirichletBC.cfg
short/3D/PyLith/branches/pylith-friction/playpen/friction/twoquad4-axial.mesh
short/3D/PyLith/branches/pylith-friction/playpen/friction/twoquad4-opening.mesh
short/3D/PyLith/branches/pylith-friction/playpen/friction/twoquad4-shear-dirichletBC.cfg
short/3D/PyLith/branches/pylith-friction/playpen/friction/twoquad4-shear.cfg
short/3D/PyLith/branches/pylith-friction/playpen/friction/twoquad4-shear.mesh
Modified:
short/3D/PyLith/branches/pylith-friction/playpen/friction/twoquad4-axial.cfg
short/3D/PyLith/branches/pylith-friction/playpen/friction/twoquad4-opening.cfg
short/3D/PyLith/branches/pylith-friction/playpen/friction/twoquad4.mesh
Log:
Cleaned up friction example files and combined all 2D meshes into one .mesh file
Deleted: short/3D/PyLith/branches/pylith-friction/playpen/friction/twohex8-shear-DirichletBC.cfg
===================================================================
--- short/3D/PyLith/branches/pylith-friction/playpen/friction/twohex8-shear-DirichletBC.cfg 2009-11-30 03:24:40 UTC (rev 16051)
+++ short/3D/PyLith/branches/pylith-friction/playpen/friction/twohex8-shear-DirichletBC.cfg 2009-11-30 06:11:30 UTC (rev 16052)
@@ -1,166 +0,0 @@
-# -*- Python -*-
-[pylithapp]
-
-# ----------------------------------------------------------------------
-# journal
-# ----------------------------------------------------------------------
-[pylithapp.journal.info]
-timedependent = 1
-implicit = 1
-petsc = 1
-solvernonlinear = 1
-meshioascii = 1
-homogeneous = 1
-elasticityimplicit = 1
-fiatlagrange = 1
-quadrature3d = 1
-faultcohesivedyn = 1
-
-# ----------------------------------------------------------------------
-# mesh_generator
-# ----------------------------------------------------------------------
-[pylithapp.mesh_generator]
-debug = 0
-
-[pylithapp.mesh_generator.reader]
-filename = twohex8.mesh
-coordsys.space_dim = 3
-
-# ----------------------------------------------------------------------
-# problem
-# ----------------------------------------------------------------------
-[pylithapp.timedependent]
-dimension = 3
-normalizer.length_scale = 1.0*m
-formulation = pylith.problems.Implicit
-formulation.solver = pylith.problems.SolverNonlinear
-
-# Set bc to an array with 3 boundary conditions: 'x_neg' and 'x_pos'.
-bc = [x_neg,x_pos]
-bc.x_pos = pylith.bc.DirichletBoundary
-
-# Set interfaces to an array with 1 fault: 'fault'.
-interfaces = [fault]
-
-[pylithapp.timedependent.formulation.time_step]
-total_time = 0.0*s
-dt = 1.0*s
-
-# ----------------------------------------------------------------------
-# materials
-# ----------------------------------------------------------------------
-[pylithapp.timedependent.materials]
-material = pylith.materials.ElasticIsotropic3D
-
-[pylithapp.timedependent.materials.material]
-
-# We give a label of 'elastic isotropic 3D material' to this material.
-label = Elastic isotropic 3D material
-
-# The cells associated with this material are given a material ID of 1
-# in the mesh file.
-id = 1
-
-db_properties.iohandler.filename = matelastic3D.spatialdb
-
-# We are doing 3D quadrature for a hex8.
-quadrature.cell = pylith.feassemble.FIATLagrange
-quadrature.cell.dimension = 3
-
-
-[pylithapp.timedependent.formulation.time_step]
-total_time = 0.0*s
-dt = 1.0*s
-
-# ----------------------------------------------------------------------
-# boundary conditions
-# ----------------------------------------------------------------------
-# Boundary conditions to be applied to the negative x-side of the mesh.
-[pylithapp.timedependent.bc.x_neg]
-
-# We are fixing the 0 (x), 1 (y) and 2 (z) degrees of freedom.
-bc_dof = [0,1,2]
-
-# The nodes associated with this boundary condition have the name
-# 'x_neg' in the mesh file.
-label = x_neg
-
-# Boundary conditions to be applied to the positive x-side of the mesh.
-[pylithapp.timedependent.bc.x_pos]
-
-# We are prescribing the 2 (z) and 1 (y) and fixing 0 (x) degrees of freedom.
-bc_dof = [0,1,2]
-
-# The nodes associated with this boundary condition have the name
-# 'x_pos' in the mesh file.
-label = x_pos
-
-db_initial = spatialdata.spatialdb.UniformDB
-db_initial.label = Dirichlet BC +x edge
-db_initial.values = [displacement-x,displacement-y,displacement-z]
-db_initial.data = [0.0*m,1.0*m,0.5*m]
-
-# ----------------------------------------------------------------------
-# faults
-# ----------------------------------------------------------------------
-[pylithapp.timedependent.interfaces]
-fault = pylith.faults.FaultCohesiveDynL
-
-[pylithapp.timedependent.interfaces.fault]
-
-# The nodes associated with this fault have the name 'fault' in the mesh file.
-label = fault
-
-# The quadrature for a 3D fault is 2D with a linear shape.
-quadrature.cell = pylith.feassemble.FIATLagrange
-quadrature.cell.dimension = 2
-
-db_initial_tractions = spatialdata.spatialdb.UniformDB
-db_initial_tractions.label = "Initial fault tractions"
-db_initial_tractions.values = [traction-shear-leftlateral,traction-shear-updip,traction-normal]
-db_initial_tractions.data = [0.0*Pa,0.0*Pa, -10000.0*MPa]
-
-# ----------------------------------------------------------------------
-# PETSc
-# ----------------------------------------------------------------------
-# We are using all of the default settings for PETSc except for
-# specifying the block Jacobi preconditioner. Additional PETSc
-# command-line arguments may be found in the PETSc documentation.
-[pylithapp.petsc]
-ksp_rtol = 1.0e-8
-pc_type = asm
-# Change the preconditioner settings (must turn off
-# shift_positive_definite and turn on shift_nonzero).
-sub_pc_factor_shift_positive_definite = 0
-sub_pc_factor_shift_nonzero =
-
-ksp_monitor = true
-ksp_view = true
-#log_summary = true
-ksp_max_it = 100
-ksp_gmres_restart = 50
-#start_in_debugger = true
-
-snes_monitor = true
-snes_view = true
-ksp_converged_reason = true
-snes_converged_reason = true
-snes_max_it = 200
-
-# ----------------------------------------------------------------------
-# output
-# ----------------------------------------------------------------------
-# Give basename for VTK domain output of solution over domain.
-[pylithapp.problem.formulation.output.output.writer]
-filename = twohex8-shear-dirichletBC.vtk
-
-# Give basename for VTK fault output.
-[pylithapp.timedependent.interfaces.fault.output]
-writer.filename = twohex8-shear-dirichletBC-fault.vtk
-vertex_info_fields = []
-vertex_data_fields = []
-
-# Give basename for VTK output of state variables.
-[pylithapp.timedependent.materials.material.output]
-cell_filter = pylith.meshio.CellFilterAvgMesh
-writer.filename = twohex8-shear-dirichletBC-statevars.vtk
Copied: short/3D/PyLith/branches/pylith-friction/playpen/friction/twohex8-shear-sliding.cfg (from rev 16051, short/3D/PyLith/branches/pylith-friction/playpen/friction/twohex8-shear-DirichletBC.cfg)
===================================================================
--- short/3D/PyLith/branches/pylith-friction/playpen/friction/twohex8-shear-sliding.cfg (rev 0)
+++ short/3D/PyLith/branches/pylith-friction/playpen/friction/twohex8-shear-sliding.cfg 2009-11-30 06:11:30 UTC (rev 16052)
@@ -0,0 +1,166 @@
+# -*- Python -*-
+[pylithapp]
+
+# ----------------------------------------------------------------------
+# journal
+# ----------------------------------------------------------------------
+[pylithapp.journal.info]
+timedependent = 1
+implicit = 1
+petsc = 1
+solvernonlinear = 1
+meshioascii = 1
+homogeneous = 1
+elasticityimplicit = 1
+fiatlagrange = 1
+quadrature3d = 1
+faultcohesivedyn = 1
+
+# ----------------------------------------------------------------------
+# mesh_generator
+# ----------------------------------------------------------------------
+[pylithapp.mesh_generator]
+debug = 0
+
+[pylithapp.mesh_generator.reader]
+filename = twohex8.mesh
+coordsys.space_dim = 3
+
+# ----------------------------------------------------------------------
+# problem
+# ----------------------------------------------------------------------
+[pylithapp.timedependent]
+dimension = 3
+normalizer.length_scale = 1.0*m
+formulation = pylith.problems.Implicit
+formulation.solver = pylith.problems.SolverNonlinear
+
+# Set bc to an array with 3 boundary conditions: 'x_neg' and 'x_pos'.
+bc = [x_neg,x_pos]
+bc.x_pos = pylith.bc.DirichletBoundary
+
+# Set interfaces to an array with 1 fault: 'fault'.
+interfaces = [fault]
+
+[pylithapp.timedependent.formulation.time_step]
+total_time = 0.0*s
+dt = 1.0*s
+
+# ----------------------------------------------------------------------
+# materials
+# ----------------------------------------------------------------------
+[pylithapp.timedependent.materials]
+material = pylith.materials.ElasticIsotropic3D
+
+[pylithapp.timedependent.materials.material]
+
+# We give a label of 'elastic isotropic 3D material' to this material.
+label = Elastic isotropic 3D material
+
+# The cells associated with this material are given a material ID of 1
+# in the mesh file.
+id = 1
+
+db_properties.iohandler.filename = matelastic3D.spatialdb
+
+# We are doing 3D quadrature for a hex8.
+quadrature.cell = pylith.feassemble.FIATLagrange
+quadrature.cell.dimension = 3
+
+
+[pylithapp.timedependent.formulation.time_step]
+total_time = 0.0*s
+dt = 1.0*s
+
+# ----------------------------------------------------------------------
+# boundary conditions
+# ----------------------------------------------------------------------
+# Boundary conditions to be applied to the negative x-side of the mesh.
+[pylithapp.timedependent.bc.x_neg]
+
+# We are fixing the 0 (x), 1 (y) and 2 (z) degrees of freedom.
+bc_dof = [0,1,2]
+
+# The nodes associated with this boundary condition have the name
+# 'x_neg' in the mesh file.
+label = x_neg
+
+# Boundary conditions to be applied to the positive x-side of the mesh.
+[pylithapp.timedependent.bc.x_pos]
+
+# We are prescribing the 2 (z) and 1 (y) and fixing 0 (x) degrees of freedom.
+bc_dof = [0,1,2]
+
+# The nodes associated with this boundary condition have the name
+# 'x_pos' in the mesh file.
+label = x_pos
+
+db_initial = spatialdata.spatialdb.UniformDB
+db_initial.label = Dirichlet BC +x edge
+db_initial.values = [displacement-x,displacement-y,displacement-z]
+db_initial.data = [0.0*m,1.0*m,0.5*m]
+
+# ----------------------------------------------------------------------
+# faults
+# ----------------------------------------------------------------------
+[pylithapp.timedependent.interfaces]
+fault = pylith.faults.FaultCohesiveDynL
+
+[pylithapp.timedependent.interfaces.fault]
+
+# The nodes associated with this fault have the name 'fault' in the mesh file.
+label = fault
+
+# The quadrature for a 3D fault is 2D with a linear shape.
+quadrature.cell = pylith.feassemble.FIATLagrange
+quadrature.cell.dimension = 2
+
+db_initial_tractions = spatialdata.spatialdb.UniformDB
+db_initial_tractions.label = "Initial fault tractions"
+db_initial_tractions.values = [traction-shear-leftlateral,traction-shear-updip,traction-normal]
+db_initial_tractions.data = [0.0*Pa,0.0*Pa, -10000.0*MPa]
+
+# ----------------------------------------------------------------------
+# PETSc
+# ----------------------------------------------------------------------
+# We are using all of the default settings for PETSc except for
+# specifying the block Jacobi preconditioner. Additional PETSc
+# command-line arguments may be found in the PETSc documentation.
+[pylithapp.petsc]
+ksp_rtol = 1.0e-8
+pc_type = asm
+# Change the preconditioner settings (must turn off
+# shift_positive_definite and turn on shift_nonzero).
+sub_pc_factor_shift_positive_definite = 0
+sub_pc_factor_shift_nonzero =
+
+ksp_monitor = true
+ksp_view = true
+#log_summary = true
+ksp_max_it = 100
+ksp_gmres_restart = 50
+#start_in_debugger = true
+
+snes_monitor = true
+snes_view = true
+ksp_converged_reason = true
+snes_converged_reason = true
+snes_max_it = 200
+
+# ----------------------------------------------------------------------
+# output
+# ----------------------------------------------------------------------
+# Give basename for VTK domain output of solution over domain.
+[pylithapp.problem.formulation.output.output.writer]
+filename = twohex8-shear-dirichletBC.vtk
+
+# Give basename for VTK fault output.
+[pylithapp.timedependent.interfaces.fault.output]
+writer.filename = twohex8-shear-dirichletBC-fault.vtk
+vertex_info_fields = []
+vertex_data_fields = []
+
+# Give basename for VTK output of state variables.
+[pylithapp.timedependent.materials.material.output]
+cell_filter = pylith.meshio.CellFilterAvgMesh
+writer.filename = twohex8-shear-dirichletBC-statevars.vtk
Added: short/3D/PyLith/branches/pylith-friction/playpen/friction/twohex8-shear-stick.cfg
===================================================================
--- short/3D/PyLith/branches/pylith-friction/playpen/friction/twohex8-shear-stick.cfg (rev 0)
+++ short/3D/PyLith/branches/pylith-friction/playpen/friction/twohex8-shear-stick.cfg 2009-11-30 06:11:30 UTC (rev 16052)
@@ -0,0 +1,177 @@
+# -*- Python -*-
+[pylithapp]
+
+# ----------------------------------------------------------------------
+# journal
+# ----------------------------------------------------------------------
+[pylithapp.journal.info]
+timedependent = 1
+implicit = 1
+petsc = 1
+solvernonlinear = 1
+meshioascii = 1
+homogeneous = 1
+elasticityimplicit = 1
+fiatlagrange = 1
+quadrature3d = 1
+faultcohesivedyn = 1
+
+# ----------------------------------------------------------------------
+# mesh_generator
+# ----------------------------------------------------------------------
+[pylithapp.mesh_generator]
+debug = 0
+
+[pylithapp.mesh_generator.reader]
+filename = twohex8.mesh
+coordsys.space_dim = 3
+
+# ----------------------------------------------------------------------
+# problem
+# ----------------------------------------------------------------------
+[pylithapp.timedependent]
+dimension = 3
+normalizer.length_scale = 1.0*m
+formulation = pylith.problems.Implicit
+formulation.solver = pylith.problems.SolverNonlinear
+
+# Set bc to an array with 3 boundary conditions: 'x_neg', 'x_pos_disp', 'x_pos_tract'
+bc = [x_neg,x_pos_disp,x_pos_tract]
+bc.x_pos_tract = pylith.bc.Neumann
+
+# Set interfaces to an array with 1 fault: 'fault'.
+interfaces = [fault]
+
+[pylithapp.timedependent.formulation.time_step]
+total_time = 0.0*s
+dt = 1.0*s
+
+# ----------------------------------------------------------------------
+# materials
+# ----------------------------------------------------------------------
+[pylithapp.timedependent.materials]
+material = pylith.materials.ElasticIsotropic3D
+
+[pylithapp.timedependent.materials.material]
+
+# We give a label of 'elastic isotropic 3D material' to this material.
+label = Elastic isotropic 3D material
+
+# The cells associated with this material are given a material ID of 1
+# in the mesh file.
+id = 1
+
+db_properties.iohandler.filename = matelastic3D.spatialdb
+
+# We are doing 3D quadrature for a hex8.
+quadrature.cell = pylith.feassemble.FIATLagrange
+quadrature.cell.dimension = 3
+
+
+[pylithapp.timedependent.formulation.time_step]
+total_time = 0.0*s
+dt = 1.0*s
+
+# ----------------------------------------------------------------------
+# boundary conditions
+# ----------------------------------------------------------------------
+# Boundary conditions to be applied to the negative x-side of the mesh.
+[pylithapp.timedependent.bc.x_neg]
+
+# We are fixing the 0 (x), 1 (y) and 2 (z) degrees of freedom.
+bc_dof = [0,1,2]
+
+# The nodes associated with this boundary condition have the name
+# 'x_neg' in the mesh file.
+label = x_neg
+
+# Boundary conditions to be applied to the positive x-side of the mesh.
+[pylithapp.timedependent.bc.x_pos_disp]
+
+# We are fixing the 0 (x) degree of freedom.
+bc_dof = [0]
+
+# The nodes associated with this boundary condition have the name
+# 'x_pos' in the mesh file.
+label = x_pos
+
+# Boundary conditions to be applied to the positive x-side of the mesh.
+[pylithapp.timedependent.bc.x_pos_tract]
+
+# The nodes associated with this boundary condition have the name
+# 'x_pos' in the mesh file.
+label = x_pos
+
+db_initial = spatialdata.spatialdb.UniformDB
+db_initial.label = Neumann BC +x edge
+db_initial.values = [traction-shear-horiz,traction-shear-vert,traction-normal]
+db_initial.data = [1000.0*MPa,2000.0*MPa,0.0*MPa]
+
+# Set cell type to quadrilateral (2-d Lagrange).
+quadrature.cell = pylith.feassemble.FIATLagrange
+quadrature.cell.dimension = 2
+
+# ----------------------------------------------------------------------
+# faults
+# ----------------------------------------------------------------------
+[pylithapp.timedependent.interfaces]
+fault = pylith.faults.FaultCohesiveDynL
+
+[pylithapp.timedependent.interfaces.fault]
+
+# The nodes associated with this fault have the name 'fault' in the mesh file.
+label = fault
+
+# The quadrature for a 3D fault is 2D with a linear shape.
+quadrature.cell = pylith.feassemble.FIATLagrange
+quadrature.cell.dimension = 2
+
+db_initial_tractions = spatialdata.spatialdb.UniformDB
+db_initial_tractions.label = "Initial fault tractions"
+db_initial_tractions.values = [traction-shear-leftlateral,traction-shear-updip,traction-normal]
+db_initial_tractions.data = [0.0*Pa,0.0*Pa, -10000.0*MPa]
+
+# ----------------------------------------------------------------------
+# PETSc
+# ----------------------------------------------------------------------
+# We are using all of the default settings for PETSc except for
+# specifying the block Jacobi preconditioner. Additional PETSc
+# command-line arguments may be found in the PETSc documentation.
+[pylithapp.petsc]
+ksp_rtol = 1.0e-8
+pc_type = asm
+# Change the preconditioner settings (must turn off
+# shift_positive_definite and turn on shift_nonzero).
+sub_pc_factor_shift_positive_definite = 0
+sub_pc_factor_shift_nonzero =
+
+ksp_monitor = true
+ksp_view = true
+#log_summary = true
+ksp_max_it = 100
+ksp_gmres_restart = 50
+#start_in_debugger = true
+
+snes_monitor = true
+snes_view = true
+ksp_converged_reason = true
+snes_converged_reason = true
+snes_max_it = 200
+
+# ----------------------------------------------------------------------
+# output
+# ----------------------------------------------------------------------
+# Give basename for VTK domain output of solution over domain.
+[pylithapp.problem.formulation.output.output.writer]
+filename = twohex8-shear-stick.vtk
+
+# Give basename for VTK fault output.
+[pylithapp.timedependent.interfaces.fault.output]
+writer.filename = twohex8-shear-stick-fault.vtk
+vertex_info_fields = []
+vertex_data_fields = []
+
+# 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
Modified: short/3D/PyLith/branches/pylith-friction/playpen/friction/twoquad4-axial.cfg
===================================================================
--- short/3D/PyLith/branches/pylith-friction/playpen/friction/twoquad4-axial.cfg 2009-11-30 03:24:40 UTC (rev 16051)
+++ short/3D/PyLith/branches/pylith-friction/playpen/friction/twoquad4-axial.cfg 2009-11-30 06:11:30 UTC (rev 16052)
@@ -23,7 +23,7 @@
debug = 0
[pylithapp.mesh_generator.reader]
-filename = twoquad4-axial.mesh
+filename = twoquad4.mesh
coordsys.space_dim = 2
# ----------------------------------------------------------------------
Deleted: short/3D/PyLith/branches/pylith-friction/playpen/friction/twoquad4-axial.mesh
===================================================================
--- short/3D/PyLith/branches/pylith-friction/playpen/friction/twoquad4-axial.mesh 2009-11-30 03:24:40 UTC (rev 16051)
+++ short/3D/PyLith/branches/pylith-friction/playpen/friction/twoquad4-axial.mesh 2009-11-30 06:11:30 UTC (rev 16052)
@@ -1,132 +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 2 cells.
- count = 2
-
- // These are bilinear quadrilateral cells, so there are 4 corners per cell.
- num-corners = 4
-
- // 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, vertex 3
- simplices = {
- 0 0 2 3 1
- 1 4 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
- }
- }
-
- // 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 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 1 vertex corresponding to index 3.
- group = {
- name = y_pos
- type = vertices
- count = 1
- indices = {
- 3
- }
- }
-}
Modified: short/3D/PyLith/branches/pylith-friction/playpen/friction/twoquad4-opening.cfg
===================================================================
--- short/3D/PyLith/branches/pylith-friction/playpen/friction/twoquad4-opening.cfg 2009-11-30 03:24:40 UTC (rev 16051)
+++ short/3D/PyLith/branches/pylith-friction/playpen/friction/twoquad4-opening.cfg 2009-11-30 06:11:30 UTC (rev 16052)
@@ -41,7 +41,7 @@
# and we then specify the filename and number of space dimensions for
# the mesh.
[pylithapp.mesh_generator.reader]
-filename = twoquad4-opening.mesh
+filename = twoquad4.mesh
coordsys.space_dim = 2
# ----------------------------------------------------------------------
Deleted: short/3D/PyLith/branches/pylith-friction/playpen/friction/twoquad4-opening.mesh
===================================================================
--- short/3D/PyLith/branches/pylith-friction/playpen/friction/twoquad4-opening.mesh 2009-11-30 03:24:40 UTC (rev 16051)
+++ short/3D/PyLith/branches/pylith-friction/playpen/friction/twoquad4-opening.mesh 2009-11-30 06:11:30 UTC (rev 16052)
@@ -1,133 +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 2 cells.
- count = 2
-
- // These are bilinear quadrilateral cells, so there are 4 corners per cell.
- num-corners = 4
-
- // 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, vertex 3
- simplices = {
- 0 0 2 3 1
- 1 4 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
- }
- }
-
- // 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 1 vertices corresponding to indices 0.
- group = {
- name = y_neg
- 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 1 vertex corresponding to index 3.
- group = {
- name = y_pos
- type = vertices
- count = 1
- indices = {
- 3
- }
- }
-}
Deleted: short/3D/PyLith/branches/pylith-friction/playpen/friction/twoquad4-shear-dirichletBC.cfg
===================================================================
--- short/3D/PyLith/branches/pylith-friction/playpen/friction/twoquad4-shear-dirichletBC.cfg 2009-11-30 03:24:40 UTC (rev 16051)
+++ short/3D/PyLith/branches/pylith-friction/playpen/friction/twoquad4-shear-dirichletBC.cfg 2009-11-30 06:11:30 UTC (rev 16052)
@@ -1,207 +0,0 @@
-# -*- Python -*-
-
-# The settings in this file (pylithapp.cfg) will be read automatically
-# by pylith, as long as the file is placed in the run directory.
-
-# The settings in this file will override any settings in:
-# PREFIX/etc/pylithapp.cfg
-# $HOME/.pyre/pylithapp/pylithapp.cfg
-
-# The settings in this file will be overridden by any .cfg file given
-# on the command line or by any command line settings.
-
-[pylithapp]
-
-# ----------------------------------------------------------------------
-# journal
-# ----------------------------------------------------------------------
-# The settings below turn on journal info for the specified components.
-# If you want less output to stdout, you can turn these off.
-[pylithapp.journal.info]
-timedependent = 1
-implicit = 1
-petsc = 1
-solvernonlinear = 1
-meshioascii = 1
-homogeneous = 1
-elasticityimplicit = 1
-fiatlagrange = 1
-quadrature1d = 1
-faultcohesivedyn = 1
-
-# ----------------------------------------------------------------------
-# mesh_generator
-# ----------------------------------------------------------------------
-# The settings below control the mesh generation (importing mesh info).
-# Turn on debugging output for mesh generation.
-[pylithapp.mesh_generator]
-debug = 0
-
-# This component specification means we are using PyLith ASCII format,
-# and we then specify the filename and number of space dimensions for
-# the mesh.
-[pylithapp.mesh_generator.reader]
-filename = twoquad4-shear.mesh
-coordsys.space_dim = 2
-
-# ----------------------------------------------------------------------
-# problem
-# ----------------------------------------------------------------------
-# Specify the problem settings.
-# This is a time-dependent problem, so we select this as our problem type.
-# We select a total time of 0 sec, and a time step size of 1 sec, so we
-# are performing a single time step.
-# The spatial dimension for this problem is 2.
-# For an implicit formulation (using implicit.cfg), we will perform 1
-# implicit time step from t = -1.0 to t = 0.0 (elastic solution step).
-[pylithapp.timedependent]
-dimension = 2
-normalizer.length_scale = 1.0*m
-formulation = pylith.problems.Implicit
-formulation.solver = pylith.problems.SolverNonlinear
-
-# Set bc to an array with 3 boundary conditions: 'x_neg', 'x_pos'
-bc = [x_neg,x_pos]
-bc.x_pos = pylith.bc.DirichletBoundary
-
-# Set interfaces to an array with 1 fault: 'fault'.
-interfaces = [fault]
-
-
-[pylithapp.timedependent.formulation.time_step]
-total_time = 0.0*s
-dt = 1.0*s
-
-
-# ----------------------------------------------------------------------
-# materials
-# ----------------------------------------------------------------------
-# Specify the material information for the problem.
-# The material type is isotropic elastic formulated for plane strain.
-[pylithapp.timedependent.materials]
-material = pylith.materials.ElasticPlaneStrain
-
-[pylithapp.timedependent.materials.material]
-
-# We give a label of 'elastic material' to this material.
-label = elastic material
-
-# The cells associated with this material are given a material ID of 0
-# in the mesh file.
-id = 0
-
-# The properties for this material are given in the spatial database file
-# 'matelastic2D.spatialdb'.
-db_properties.iohandler.filename = matelastic2D.spatialdb
-
-# Set cell type to quadrilateral (2-d Lagrange).
-quadrature.cell = pylith.feassemble.FIATLagrange
-quadrature.cell.dimension = 2
-
-# ----------------------------------------------------------------------
-# boundary conditions
-# ----------------------------------------------------------------------
-# Provide information on the boundary conditions.
-
-# Boundary conditions to be applied to the negative x-side of the mesh.
-[pylithapp.timedependent.bc.x_neg]
-
-# We are fixing the 0 (x) and 1 (y) degrees of freedom.
-bc_dof = [0,1]
-
-# The nodes associated with this boundary condition have the name
-# 'x_neg' in the mesh file.
-label = x_neg
-
-# Boundary conditions to be applied to the positive x-side of the mesh.
-[pylithapp.timedependent.bc.x_pos]
-
-# We are fixing the 0 (x) and prescribing 1 (y) degree of freedom.
-bc_dof = [0,1]
-
-# The nodes associated with this boundary condition have the name
-# 'x_pos' in the mesh file.
-label = x_pos
-
-db_initial = spatialdata.spatialdb.UniformDB
-db_initial.label = Dirichlet BC +x edge
-db_initial.values = [displacement-x,displacement-y]
-db_initial.data = [0.0*m,3.0*m]
-
-# ----------------------------------------------------------------------
-# faults
-# ----------------------------------------------------------------------
-# Provide information on the fault (interface).
-[pylithapp.timedependent.interfaces]
-
-fault = pylith.faults.FaultCohesiveDynL
-
-# Define fault properties.
-[pylithapp.timedependent.interfaces.fault]
-
-# The nodes associated with this fault have the name 'fault' in the mesh file.
-label = fault
-
-# NOTE: It is possible to assign an ID number to a fault (e.g.,
-# 'id = 10'). Care must be taken when doing this, however, because the
-# assigned ID will become the material ID for the cohesive element.
-# This ID must not conflict with any of the material ID numbers for
-# volume elements. The default ID for a fault is 100. If you have a
-# fault in your mesh you must:
-# 1. If you create your own fault ID, make sure it does not conflict
-# with any of you material ID's.
-# 2. If you use the default fault ID, make sure that none of your
-# material ID's are equal to 100.
-
-# The quadrature for a 2D fault is 1D with a linear shape.
-quadrature.cell = pylith.feassemble.FIATLagrange
-quadrature.cell.dimension = 1
-
-db_initial_tractions = spatialdata.spatialdb.UniformDB
-db_initial_tractions.label = "Initial fault tractions"
-db_initial_tractions.values = [traction-shear,traction-normal]
-db_initial_tractions.data = [0.0*Pa, -10000.0*MPa]
-
-# ----------------------------------------------------------------------
-# PETSc
-# ----------------------------------------------------------------------
-# We are using all of the default settings for PETSc except for
-# specifying the block Jacobi preconditioner. Additional PETSc
-# command-line arguments may be found in the PETSc documentation.
-[pylithapp.petsc]
-ksp_rtol = 1.0e-8
-pc_type = asm
-# Change the preconditioner settings (must turn off
-# shift_positive_definite and turn on shift_nonzero).
-sub_pc_factor_shift_positive_definite = 0
-sub_pc_factor_shift_nonzero =
-
-ksp_monitor = true
-ksp_view = true
-#log_summary = true
-ksp_max_it = 100
-ksp_gmres_restart = 50
-#start_in_debugger = true
-
-snes_monitor = true
-snes_view = true
-ksp_converged_reason = true
-snes_converged_reason = true
-snes_max_it = 200
-
-# ----------------------------------------------------------------------
-# output
-# ----------------------------------------------------------------------
-# Give basename for VTK domain output of solution over domain.
-[pylithapp.problem.formulation.output.output.writer]
-filename = twoquad4-shear-dirichletBC.vtk
-
-# Give basename for VTK fault output.
-[pylithapp.timedependent.interfaces.fault.output]
-writer.filename = twoquad4-shear-dirichletBC-fault.vtk
-vertex_info_fields = [strike_dir,normal_dir,initial_traction]
-
-# Give basename for VTK output of state variables.
-[pylithapp.timedependent.materials.material.output]
-cell_filter = pylith.meshio.CellFilterAvgMesh
-writer.filename = twoquad4-shear-dirichletBC-statevars.vtk
Copied: short/3D/PyLith/branches/pylith-friction/playpen/friction/twoquad4-shear-sliding.cfg (from rev 16051, short/3D/PyLith/branches/pylith-friction/playpen/friction/twoquad4-shear-dirichletBC.cfg)
===================================================================
--- short/3D/PyLith/branches/pylith-friction/playpen/friction/twoquad4-shear-sliding.cfg (rev 0)
+++ short/3D/PyLith/branches/pylith-friction/playpen/friction/twoquad4-shear-sliding.cfg 2009-11-30 06:11:30 UTC (rev 16052)
@@ -0,0 +1,207 @@
+# -*- Python -*-
+
+# The settings in this file (pylithapp.cfg) will be read automatically
+# by pylith, as long as the file is placed in the run directory.
+
+# The settings in this file will override any settings in:
+# PREFIX/etc/pylithapp.cfg
+# $HOME/.pyre/pylithapp/pylithapp.cfg
+
+# The settings in this file will be overridden by any .cfg file given
+# on the command line or by any command line settings.
+
+[pylithapp]
+
+# ----------------------------------------------------------------------
+# journal
+# ----------------------------------------------------------------------
+# The settings below turn on journal info for the specified components.
+# If you want less output to stdout, you can turn these off.
+[pylithapp.journal.info]
+timedependent = 1
+implicit = 1
+petsc = 1
+solvernonlinear = 1
+meshioascii = 1
+homogeneous = 1
+elasticityimplicit = 1
+fiatlagrange = 1
+quadrature1d = 1
+faultcohesivedyn = 1
+
+# ----------------------------------------------------------------------
+# mesh_generator
+# ----------------------------------------------------------------------
+# The settings below control the mesh generation (importing mesh info).
+# Turn on debugging output for mesh generation.
+[pylithapp.mesh_generator]
+debug = 0
+
+# This component specification means we are using PyLith ASCII format,
+# and we then specify the filename and number of space dimensions for
+# the mesh.
+[pylithapp.mesh_generator.reader]
+filename = twoquad4-shear.mesh
+coordsys.space_dim = 2
+
+# ----------------------------------------------------------------------
+# problem
+# ----------------------------------------------------------------------
+# Specify the problem settings.
+# This is a time-dependent problem, so we select this as our problem type.
+# We select a total time of 0 sec, and a time step size of 1 sec, so we
+# are performing a single time step.
+# The spatial dimension for this problem is 2.
+# For an implicit formulation (using implicit.cfg), we will perform 1
+# implicit time step from t = -1.0 to t = 0.0 (elastic solution step).
+[pylithapp.timedependent]
+dimension = 2
+normalizer.length_scale = 1.0*m
+formulation = pylith.problems.Implicit
+formulation.solver = pylith.problems.SolverNonlinear
+
+# Set bc to an array with 3 boundary conditions: 'x_neg', 'x_pos'
+bc = [x_neg,x_pos]
+bc.x_pos = pylith.bc.DirichletBoundary
+
+# Set interfaces to an array with 1 fault: 'fault'.
+interfaces = [fault]
+
+
+[pylithapp.timedependent.formulation.time_step]
+total_time = 0.0*s
+dt = 1.0*s
+
+
+# ----------------------------------------------------------------------
+# materials
+# ----------------------------------------------------------------------
+# Specify the material information for the problem.
+# The material type is isotropic elastic formulated for plane strain.
+[pylithapp.timedependent.materials]
+material = pylith.materials.ElasticPlaneStrain
+
+[pylithapp.timedependent.materials.material]
+
+# We give a label of 'elastic material' to this material.
+label = elastic material
+
+# The cells associated with this material are given a material ID of 0
+# in the mesh file.
+id = 0
+
+# The properties for this material are given in the spatial database file
+# 'matelastic2D.spatialdb'.
+db_properties.iohandler.filename = matelastic2D.spatialdb
+
+# Set cell type to quadrilateral (2-d Lagrange).
+quadrature.cell = pylith.feassemble.FIATLagrange
+quadrature.cell.dimension = 2
+
+# ----------------------------------------------------------------------
+# boundary conditions
+# ----------------------------------------------------------------------
+# Provide information on the boundary conditions.
+
+# Boundary conditions to be applied to the negative x-side of the mesh.
+[pylithapp.timedependent.bc.x_neg]
+
+# We are fixing the 0 (x) and 1 (y) degrees of freedom.
+bc_dof = [0,1]
+
+# The nodes associated with this boundary condition have the name
+# 'x_neg' in the mesh file.
+label = x_neg
+
+# Boundary conditions to be applied to the positive x-side of the mesh.
+[pylithapp.timedependent.bc.x_pos]
+
+# We are fixing the 0 (x) and prescribing 1 (y) degree of freedom.
+bc_dof = [0,1]
+
+# The nodes associated with this boundary condition have the name
+# 'x_pos' in the mesh file.
+label = x_pos
+
+db_initial = spatialdata.spatialdb.UniformDB
+db_initial.label = Dirichlet BC +x edge
+db_initial.values = [displacement-x,displacement-y]
+db_initial.data = [0.0*m,3.0*m]
+
+# ----------------------------------------------------------------------
+# faults
+# ----------------------------------------------------------------------
+# Provide information on the fault (interface).
+[pylithapp.timedependent.interfaces]
+
+fault = pylith.faults.FaultCohesiveDynL
+
+# Define fault properties.
+[pylithapp.timedependent.interfaces.fault]
+
+# The nodes associated with this fault have the name 'fault' in the mesh file.
+label = fault
+
+# NOTE: It is possible to assign an ID number to a fault (e.g.,
+# 'id = 10'). Care must be taken when doing this, however, because the
+# assigned ID will become the material ID for the cohesive element.
+# This ID must not conflict with any of the material ID numbers for
+# volume elements. The default ID for a fault is 100. If you have a
+# fault in your mesh you must:
+# 1. If you create your own fault ID, make sure it does not conflict
+# with any of you material ID's.
+# 2. If you use the default fault ID, make sure that none of your
+# material ID's are equal to 100.
+
+# The quadrature for a 2D fault is 1D with a linear shape.
+quadrature.cell = pylith.feassemble.FIATLagrange
+quadrature.cell.dimension = 1
+
+db_initial_tractions = spatialdata.spatialdb.UniformDB
+db_initial_tractions.label = "Initial fault tractions"
+db_initial_tractions.values = [traction-shear,traction-normal]
+db_initial_tractions.data = [0.0*Pa, -10000.0*MPa]
+
+# ----------------------------------------------------------------------
+# PETSc
+# ----------------------------------------------------------------------
+# We are using all of the default settings for PETSc except for
+# specifying the block Jacobi preconditioner. Additional PETSc
+# command-line arguments may be found in the PETSc documentation.
+[pylithapp.petsc]
+ksp_rtol = 1.0e-8
+pc_type = asm
+# Change the preconditioner settings (must turn off
+# shift_positive_definite and turn on shift_nonzero).
+sub_pc_factor_shift_positive_definite = 0
+sub_pc_factor_shift_nonzero =
+
+ksp_monitor = true
+ksp_view = true
+#log_summary = true
+ksp_max_it = 100
+ksp_gmres_restart = 50
+#start_in_debugger = true
+
+snes_monitor = true
+snes_view = true
+ksp_converged_reason = true
+snes_converged_reason = true
+snes_max_it = 200
+
+# ----------------------------------------------------------------------
+# output
+# ----------------------------------------------------------------------
+# Give basename for VTK domain output of solution over domain.
+[pylithapp.problem.formulation.output.output.writer]
+filename = twoquad4-shear-dirichletBC.vtk
+
+# Give basename for VTK fault output.
+[pylithapp.timedependent.interfaces.fault.output]
+writer.filename = twoquad4-shear-dirichletBC-fault.vtk
+vertex_info_fields = [strike_dir,normal_dir,initial_traction]
+
+# Give basename for VTK output of state variables.
+[pylithapp.timedependent.materials.material.output]
+cell_filter = pylith.meshio.CellFilterAvgMesh
+writer.filename = twoquad4-shear-dirichletBC-statevars.vtk
Copied: short/3D/PyLith/branches/pylith-friction/playpen/friction/twoquad4-shear-stick.cfg (from rev 16051, short/3D/PyLith/branches/pylith-friction/playpen/friction/twoquad4-shear.cfg)
===================================================================
--- short/3D/PyLith/branches/pylith-friction/playpen/friction/twoquad4-shear-stick.cfg (rev 0)
+++ short/3D/PyLith/branches/pylith-friction/playpen/friction/twoquad4-shear-stick.cfg 2009-11-30 06:11:30 UTC (rev 16052)
@@ -0,0 +1,217 @@
+# -*- Python -*-
+
+# The settings in this file (pylithapp.cfg) will be read automatically
+# by pylith, as long as the file is placed in the run directory.
+
+# The settings in this file will override any settings in:
+# PREFIX/etc/pylithapp.cfg
+# $HOME/.pyre/pylithapp/pylithapp.cfg
+
+# The settings in this file will be overridden by any .cfg file given
+# on the command line or by any command line settings.
+
+[pylithapp]
+
+# ----------------------------------------------------------------------
+# journal
+# ----------------------------------------------------------------------
+# The settings below turn on journal info for the specified components.
+# If you want less output to stdout, you can turn these off.
+[pylithapp.journal.info]
+timedependent = 1
+implicit = 1
+petsc = 1
+solvernonlinear = 1
+meshioascii = 1
+homogeneous = 1
+elasticityimplicit = 1
+fiatlagrange = 1
+quadrature1d = 1
+faultcohesivedyn = 1
+
+# ----------------------------------------------------------------------
+# mesh_generator
+# ----------------------------------------------------------------------
+# The settings below control the mesh generation (importing mesh info).
+# Turn on debugging output for mesh generation.
+[pylithapp.mesh_generator]
+debug = 0
+
+# This component specification means we are using PyLith ASCII format,
+# and we then specify the filename and number of space dimensions for
+# the mesh.
+[pylithapp.mesh_generator.reader]
+filename = twoquad4-shear.mesh
+coordsys.space_dim = 2
+
+# ----------------------------------------------------------------------
+# problem
+# ----------------------------------------------------------------------
+# Specify the problem settings.
+# This is a time-dependent problem, so we select this as our problem type.
+# We select a total time of 0 sec, and a time step size of 1 sec, so we
+# are performing a single time step.
+# The spatial dimension for this problem is 2.
+# For an implicit formulation (using implicit.cfg), we will perform 1
+# implicit time step from t = -1.0 to t = 0.0 (elastic solution step).
+[pylithapp.timedependent]
+dimension = 2
+normalizer.length_scale = 1.0*m
+formulation = pylith.problems.Implicit
+formulation.solver = pylith.problems.SolverNonlinear
+
+# Set bc to an array with 3 boundary conditions: 'x_neg', 'x_pos_disp', 'x_pos_tract'
+bc = [x_neg,x_pos_disp,x_pos_tract]
+bc.x_pos_tract = pylith.bc.Neumann
+
+# Set interfaces to an array with 1 fault: 'fault'.
+interfaces = [fault]
+
+
+[pylithapp.timedependent.formulation.time_step]
+total_time = 0.0*s
+dt = 1.0*s
+
+
+# ----------------------------------------------------------------------
+# materials
+# ----------------------------------------------------------------------
+# Specify the material information for the problem.
+# The material type is isotropic elastic formulated for plane strain.
+[pylithapp.timedependent.materials]
+material = pylith.materials.ElasticPlaneStrain
+
+[pylithapp.timedependent.materials.material]
+
+# We give a label of 'elastic material' to this material.
+label = elastic material
+
+# The cells associated with this material are given a material ID of 0
+# in the mesh file.
+id = 0
+
+# The properties for this material are given in the spatial database file
+# 'matelastic2D.spatialdb'.
+db_properties.iohandler.filename = matelastic2D.spatialdb
+
+# Set cell type to quadrilateral (2-d Lagrange).
+quadrature.cell = pylith.feassemble.FIATLagrange
+quadrature.cell.dimension = 2
+
+# ----------------------------------------------------------------------
+# boundary conditions
+# ----------------------------------------------------------------------
+# Provide information on the boundary conditions.
+
+# Boundary conditions to be applied to the negative x-side of the mesh.
+[pylithapp.timedependent.bc.x_neg]
+
+# We are fixing the 0 (x) and 1 (y) degrees of freedom.
+bc_dof = [0,1]
+
+# The nodes associated with this boundary condition have the name
+# 'x_neg' in the mesh file.
+label = x_neg
+
+# Boundary conditions to be applied to the positive x-side of the mesh.
+[pylithapp.timedependent.bc.x_pos_disp]
+
+# We are fixing the 0 (x) degree of freedom.
+bc_dof = [0]
+
+# The nodes associated with this boundary condition have the name
+# 'x_pos' in the mesh file.
+label = x_pos
+
+# Boundary conditions to be applied to the positive x-side of the mesh.
+[pylithapp.timedependent.bc.x_pos_tract]
+
+# The nodes associated with this boundary condition have the name
+# 'x_pos' in the mesh file.
+label = x_pos
+
+db_initial = spatialdata.spatialdb.UniformDB
+db_initial.label = Neumann BC +x edge
+db_initial.values = [traction-shear,traction-normal]
+db_initial.data = [1000*MPa,0.0*MPa,]
+
+# Set cell type to quadrilateral (1-d Lagrange).
+quadrature.cell = pylith.feassemble.FIATLagrange
+quadrature.cell.dimension = 1
+
+# ----------------------------------------------------------------------
+# faults
+# ----------------------------------------------------------------------
+# Provide information on the fault (interface).
+[pylithapp.timedependent.interfaces]
+
+fault = pylith.faults.FaultCohesiveDynL
+
+# Define fault properties.
+[pylithapp.timedependent.interfaces.fault]
+
+# The nodes associated with this fault have the name 'fault' in the mesh file.
+label = fault
+
+# NOTE: It is possible to assign an ID number to a fault (e.g.,
+# 'id = 10'). Care must be taken when doing this, however, because the
+# assigned ID will become the material ID for the cohesive element.
+# This ID must not conflict with any of the material ID numbers for
+# volume elements. The default ID for a fault is 100. If you have a
+# fault in your mesh you must:
+# 1. If you create your own fault ID, make sure it does not conflict
+# with any of you material ID's.
+# 2. If you use the default fault ID, make sure that none of your
+# material ID's are equal to 100.
+
+# The quadrature for a 2D fault is 1D with a linear shape.
+quadrature.cell = pylith.feassemble.FIATLagrange
+quadrature.cell.dimension = 1
+
+db_initial_tractions = spatialdata.spatialdb.UniformDB
+db_initial_tractions.label = "Initial fault tractions"
+db_initial_tractions.values = [traction-shear,traction-normal]
+db_initial_tractions.data = [0.0*Pa, -10000.0*MPa]
+
+# ----------------------------------------------------------------------
+# PETSc
+# ----------------------------------------------------------------------
+# We are using all of the default settings for PETSc except for
+# specifying the block Jacobi preconditioner. Additional PETSc
+# command-line arguments may be found in the PETSc documentation.
+[pylithapp.petsc]
+ksp_rtol = 1.0e-8
+pc_type = asm
+# Change the preconditioner settings (must turn off
+# shift_positive_definite and turn on shift_nonzero).
+sub_pc_factor_shift_positive_definite = 0
+sub_pc_factor_shift_nonzero =
+
+ksp_monitor = true
+ksp_view = true
+#log_summary = true
+ksp_max_it = 100
+ksp_gmres_restart = 50
+#start_in_debugger = true
+
+snes_monitor = true
+snes_view = true
+ksp_converged_reason = true
+snes_converged_reason = true
+
+# ----------------------------------------------------------------------
+# output
+# ----------------------------------------------------------------------
+# Give basename for VTK domain output of solution over domain.
+[pylithapp.problem.formulation.output.output.writer]
+filename = twoquad4-shear.vtk
+
+# Give basename for VTK fault output.
+[pylithapp.timedependent.interfaces.fault.output]
+writer.filename = twoquad4-shear-fault.vtk
+vertex_info_fields = [strike_dir,normal_dir,initial_traction]
+
+# Give basename for VTK output of state variables.
+[pylithapp.timedependent.materials.material.output]
+cell_filter = pylith.meshio.CellFilterAvgMesh
+writer.filename = twoquad4-shear-statevars.vtk
Deleted: short/3D/PyLith/branches/pylith-friction/playpen/friction/twoquad4-shear.cfg
===================================================================
--- short/3D/PyLith/branches/pylith-friction/playpen/friction/twoquad4-shear.cfg 2009-11-30 03:24:40 UTC (rev 16051)
+++ short/3D/PyLith/branches/pylith-friction/playpen/friction/twoquad4-shear.cfg 2009-11-30 06:11:30 UTC (rev 16052)
@@ -1,217 +0,0 @@
-# -*- Python -*-
-
-# The settings in this file (pylithapp.cfg) will be read automatically
-# by pylith, as long as the file is placed in the run directory.
-
-# The settings in this file will override any settings in:
-# PREFIX/etc/pylithapp.cfg
-# $HOME/.pyre/pylithapp/pylithapp.cfg
-
-# The settings in this file will be overridden by any .cfg file given
-# on the command line or by any command line settings.
-
-[pylithapp]
-
-# ----------------------------------------------------------------------
-# journal
-# ----------------------------------------------------------------------
-# The settings below turn on journal info for the specified components.
-# If you want less output to stdout, you can turn these off.
-[pylithapp.journal.info]
-timedependent = 1
-implicit = 1
-petsc = 1
-solvernonlinear = 1
-meshioascii = 1
-homogeneous = 1
-elasticityimplicit = 1
-fiatlagrange = 1
-quadrature1d = 1
-faultcohesivedyn = 1
-
-# ----------------------------------------------------------------------
-# mesh_generator
-# ----------------------------------------------------------------------
-# The settings below control the mesh generation (importing mesh info).
-# Turn on debugging output for mesh generation.
-[pylithapp.mesh_generator]
-debug = 0
-
-# This component specification means we are using PyLith ASCII format,
-# and we then specify the filename and number of space dimensions for
-# the mesh.
-[pylithapp.mesh_generator.reader]
-filename = twoquad4-shear.mesh
-coordsys.space_dim = 2
-
-# ----------------------------------------------------------------------
-# problem
-# ----------------------------------------------------------------------
-# Specify the problem settings.
-# This is a time-dependent problem, so we select this as our problem type.
-# We select a total time of 0 sec, and a time step size of 1 sec, so we
-# are performing a single time step.
-# The spatial dimension for this problem is 2.
-# For an implicit formulation (using implicit.cfg), we will perform 1
-# implicit time step from t = -1.0 to t = 0.0 (elastic solution step).
-[pylithapp.timedependent]
-dimension = 2
-normalizer.length_scale = 1.0*m
-formulation = pylith.problems.Implicit
-formulation.solver = pylith.problems.SolverNonlinear
-
-# Set bc to an array with 3 boundary conditions: 'x_neg', 'x_pos_disp', 'x_pos_tract'
-bc = [x_neg,x_pos_disp,x_pos_tract]
-bc.x_pos_tract = pylith.bc.Neumann
-
-# Set interfaces to an array with 1 fault: 'fault'.
-interfaces = [fault]
-
-
-[pylithapp.timedependent.formulation.time_step]
-total_time = 0.0*s
-dt = 1.0*s
-
-
-# ----------------------------------------------------------------------
-# materials
-# ----------------------------------------------------------------------
-# Specify the material information for the problem.
-# The material type is isotropic elastic formulated for plane strain.
-[pylithapp.timedependent.materials]
-material = pylith.materials.ElasticPlaneStrain
-
-[pylithapp.timedependent.materials.material]
-
-# We give a label of 'elastic material' to this material.
-label = elastic material
-
-# The cells associated with this material are given a material ID of 0
-# in the mesh file.
-id = 0
-
-# The properties for this material are given in the spatial database file
-# 'matelastic2D.spatialdb'.
-db_properties.iohandler.filename = matelastic2D.spatialdb
-
-# Set cell type to quadrilateral (2-d Lagrange).
-quadrature.cell = pylith.feassemble.FIATLagrange
-quadrature.cell.dimension = 2
-
-# ----------------------------------------------------------------------
-# boundary conditions
-# ----------------------------------------------------------------------
-# Provide information on the boundary conditions.
-
-# Boundary conditions to be applied to the negative x-side of the mesh.
-[pylithapp.timedependent.bc.x_neg]
-
-# We are fixing the 0 (x) and 1 (y) degrees of freedom.
-bc_dof = [0,1]
-
-# The nodes associated with this boundary condition have the name
-# 'x_neg' in the mesh file.
-label = x_neg
-
-# Boundary conditions to be applied to the positive x-side of the mesh.
-[pylithapp.timedependent.bc.x_pos_disp]
-
-# We are fixing the 0 (x) degree of freedom.
-bc_dof = [0]
-
-# The nodes associated with this boundary condition have the name
-# 'x_pos' in the mesh file.
-label = x_pos
-
-# Boundary conditions to be applied to the positive x-side of the mesh.
-[pylithapp.timedependent.bc.x_pos_tract]
-
-# The nodes associated with this boundary condition have the name
-# 'x_pos' in the mesh file.
-label = x_pos
-
-db_initial = spatialdata.spatialdb.UniformDB
-db_initial.label = Neumann BC +x edge
-db_initial.values = [traction-shear,traction-normal]
-db_initial.data = [1000*MPa,0.0*MPa,]
-
-# Set cell type to quadrilateral (1-d Lagrange).
-quadrature.cell = pylith.feassemble.FIATLagrange
-quadrature.cell.dimension = 1
-
-# ----------------------------------------------------------------------
-# faults
-# ----------------------------------------------------------------------
-# Provide information on the fault (interface).
-[pylithapp.timedependent.interfaces]
-
-fault = pylith.faults.FaultCohesiveDynL
-
-# Define fault properties.
-[pylithapp.timedependent.interfaces.fault]
-
-# The nodes associated with this fault have the name 'fault' in the mesh file.
-label = fault
-
-# NOTE: It is possible to assign an ID number to a fault (e.g.,
-# 'id = 10'). Care must be taken when doing this, however, because the
-# assigned ID will become the material ID for the cohesive element.
-# This ID must not conflict with any of the material ID numbers for
-# volume elements. The default ID for a fault is 100. If you have a
-# fault in your mesh you must:
-# 1. If you create your own fault ID, make sure it does not conflict
-# with any of you material ID's.
-# 2. If you use the default fault ID, make sure that none of your
-# material ID's are equal to 100.
-
-# The quadrature for a 2D fault is 1D with a linear shape.
-quadrature.cell = pylith.feassemble.FIATLagrange
-quadrature.cell.dimension = 1
-
-db_initial_tractions = spatialdata.spatialdb.UniformDB
-db_initial_tractions.label = "Initial fault tractions"
-db_initial_tractions.values = [traction-shear,traction-normal]
-db_initial_tractions.data = [0.0*Pa, -10000.0*MPa]
-
-# ----------------------------------------------------------------------
-# PETSc
-# ----------------------------------------------------------------------
-# We are using all of the default settings for PETSc except for
-# specifying the block Jacobi preconditioner. Additional PETSc
-# command-line arguments may be found in the PETSc documentation.
-[pylithapp.petsc]
-ksp_rtol = 1.0e-8
-pc_type = asm
-# Change the preconditioner settings (must turn off
-# shift_positive_definite and turn on shift_nonzero).
-sub_pc_factor_shift_positive_definite = 0
-sub_pc_factor_shift_nonzero =
-
-ksp_monitor = true
-ksp_view = true
-#log_summary = true
-ksp_max_it = 100
-ksp_gmres_restart = 50
-#start_in_debugger = true
-
-snes_monitor = true
-snes_view = true
-ksp_converged_reason = true
-snes_converged_reason = true
-
-# ----------------------------------------------------------------------
-# output
-# ----------------------------------------------------------------------
-# Give basename for VTK domain output of solution over domain.
-[pylithapp.problem.formulation.output.output.writer]
-filename = twoquad4-shear.vtk
-
-# Give basename for VTK fault output.
-[pylithapp.timedependent.interfaces.fault.output]
-writer.filename = twoquad4-shear-fault.vtk
-vertex_info_fields = [strike_dir,normal_dir,initial_traction]
-
-# Give basename for VTK output of state variables.
-[pylithapp.timedependent.materials.material.output]
-cell_filter = pylith.meshio.CellFilterAvgMesh
-writer.filename = twoquad4-shear-statevars.vtk
Deleted: short/3D/PyLith/branches/pylith-friction/playpen/friction/twoquad4-shear.mesh
===================================================================
--- short/3D/PyLith/branches/pylith-friction/playpen/friction/twoquad4-shear.mesh 2009-11-30 03:24:40 UTC (rev 16051)
+++ short/3D/PyLith/branches/pylith-friction/playpen/friction/twoquad4-shear.mesh 2009-11-30 06:11:30 UTC (rev 16052)
@@ -1,131 +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 2 cells.
- count = 2
-
- // These are bilinear quadrilateral cells, so there are 4 corners per cell.
- num-corners = 4
-
- // 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, vertex 3
- simplices = {
- 0 0 2 3 1
- 1 4 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
- }
- }
-
- // 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 1 vertices corresponding to indices 0.
- group = {
- name = y_neg
- type = vertices
- count = 1
- indices = {
- 2
- }
- }
-
- // 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 1 vertex corresponding to index 3.
- group = {
- name = y_pos
- type = vertices
- count = 1
- indices = {
- 3
- }
- }
-}
Modified: short/3D/PyLith/branches/pylith-friction/playpen/friction/twoquad4.mesh
===================================================================
--- short/3D/PyLith/branches/pylith-friction/playpen/friction/twoquad4.mesh 2009-11-30 03:24:40 UTC (rev 16051)
+++ short/3D/PyLith/branches/pylith-friction/playpen/friction/twoquad4.mesh 2009-11-30 06:11:30 UTC (rev 16052)
@@ -88,10 +88,9 @@
group = {
name = y_neg
type = vertices
- count = 3
+ count = 2
indices = {
0
- 2
4
}
}
More information about the CIG-COMMITS
mailing list