You are here: Home / Groups / Short-Term Crustal Dynamics / Wiki / PyLith / Meshing
3.145.47.253
  • Discoverability Visible
  • Join Policy Invite Only
  • Created 05 Jan 2021

PyLith /

Meshing

Issues related to generating a mesh to use as input for PyLith.

Best Practices

  • Always check the quality of your mesh BEFORE running a PyLith simulation. The ideal aspect ratio is 1.0.
    • CUBIT: Aspect ratios should be less than about 4.0 in quasi-static simulations and less than about 2.0 in dynamic simulations. Use the “Quality” command to show a summary of the element quality. See the “Mesh Quality Assessment” section of the CUBIT manual for more information about the various quality checks. We find the aspect ratio and condition number checks the most useful. We generally use condition number smoothing to improve the mesh quality.
  • LaGriT: Aspect ratios should be greater than about 0.2 in quasi-static simulations and greater than about 0.4 in dynamic simulations. Use the command “quality” to show a summary of the element quality.
  • Always check your nodesets/psets to make sure they match the desired boundaries, etc. Nodesets/pets for Dirichlet boundary conditions cannot overlap if they set the same components (i.e., x-component, y-component, z-component), but they can overlap if they set difference components.

CUBIT

  • Nonplanar fault geometry

See examples/2d/subduction and Sessions III and IV of the 2011 Crustal Deformation Modeling tutorial.

  • Varying discretization size with distance from the fault

See examples/2d/subduction and examples/meshing/cubit_cellsize.

LaGriT

  • Identifying faults using surface meshes

Using surface meshes to identify the fault surface is a development feature that is fragile and untested. Use with extreme caution. Identifying faults using psets is a much more thoroughly tested feature.

Created on , Last modified on