You are here: Home / Groups / Short-Term Crustal Dynamics / Wiki / Work Plans / 2016 Nov PyLith Dev Plans
3.143.218.180
  • Discoverability Visible
  • Join Policy Invite Only
  • Created 05 Jan 2021

Work Plans /

2016 Nov PyLith Dev Plans

PyLith Development Plans, Nov 2016

Priorities for PyLith software development, such as new features and enhancements. This a draft for community comment (Nov 7, 2016).

This plan attempts to balance meeting short-term objectives of delivering high priority, new features and meeting long-term objectives of extending the code to solve a broader range of scientific problems.

Version 3.0 (Spring 2017)

  1. Multiphysics expert.png 30%
    • Implement modular approach for specifying governing equations and computing residuals and Jacobians. expert.png
    • Incompressible elasticity via a pressure field intermediate.png 20%
    • Poroelasticity (Image(difficult.png 25px) failed - File not found) 5%
  2. Higher order basis functions {(Image(difficult.png 25px) failed - File not found) 25%
    • Allow user to select order of basis functions independent of the mesh (which defines the geometry). This permits higher resolution for a given mesh.
  3. Switch to using PETSc time-stepping (TS) algorithms. intermediate.png 25%
    • Replace simple Python-based time-stepping implementations with PETSc time-stepping algorithms that provide support for higher order discretization in time and real adaptive time stepping.
  4. Improve fault formulation for spontaneous rupture intermediate.png 10%
    • Removes inner solve associated with updating Lagrange multipliers. This will significantly accelerate the nonlinear solve.
  5. Allow full specification of the initial conditions (solution and state variables) intermediate.png 0%
  6. Update user manual
    • Convert from LyX to LaTeX for ease of maintenance and editing. {{easy.png}} 0%
    • Reorganize for multiphysics implementation. intermediate.png 5%
    • Reorganize examples. intermediate.png 0%
      • Focus on demonstrating the range of physics and features beginning with simple cases and building towards more complex cases.
      • Include ParaView Python scripts for plotting results.
      • Consider moving examples to Jupyter notebooks; export to PDF files for “print” documentation.

Version 3.1 (late 2017)

  1. GUI interface for specifying simulation parameters (Image(difficult.png 25px) failed - File not found)
  2. Add additional multiphysics implementations and rheologies
    • Drucker-Prager bulk rheology with relaxation to yield surface intermediate.png
    • Elasticity + heat flow (Image(difficult.png 25px) failed - File not found)
  3. Reorganize output for time-dependent Green’s functions and adjoints intermediate.png
  4. Multilevel nonlinear solve expert.png
  5. Radial basis functions for spatial databases intermediate.png
  6. Convert to Python 3 and Pyre 1.0.

Version 4.0 (TBD)

  1. Earthquake cycle modeling {(Image(difficult.png 25px) failed - File not found)
    • Same mesh for dynamic and quasi-static parts (dynamic -> quasi-static, quasi-static -> dynamic, complete cycle)
  2. Create strain hardening/softening 2-D and 3-D Drucker-Prager elastoplastic models. intermediate.png
  3. Moment tensor point sources via equivalent body forces (Image(difficult.png 25px) failed - File not found) 5%
    • Moment tensor point sources provide a mesh independent deformation source that is better suited for Green’s function calculations than slip on a fault surface via cohesive cells.

Features for Future Releases

Major features

  1. Earthquake Cycle Modeling
    • Different meshes for dynamic and quasi-static parts expert.png
      • Requires interpolation of fields between different meshes/discretizations and may require extrapolation of solutions when quasi-static problems span a larger domain than the dynamic problems.
  2. Data assimilation
    • Use flexibility of multiphysics implementation to support inclusion of data assimilation expert.png

Minor features

  1. Begin implementation of data assimilation capabilities via adjoint equation.
  2. Combined prescribed slip / spontaneous rupture fault condition (Image(difficult.png 25px) failed - File not found)
    • Use fault constitutive model to control slip on fault except during episodes of prescribed slip. Need some way to describe when to turn on/off prescribed slip.
  3. Use threading to accelerate integrations on multi-core machines. (Image(difficult.png 25px) failed - File not found)

difficulty rating system

intermediate.png intermediate difficult.png difficult expert.png expert

based on the ski trail rating system

Created on , Last modified on