3.147.48.105
  • Discoverability Visible
  • Join Policy Invite Only
  • Created 05 Jan 2021

2015 PyLith Dev Plans

Version 4
by (unknown)
Version 5
by (unknown)

Deletions or items before changed

Additions or items after changed

1 == !PyLith Development Plans, Mar 2015 ==
2
3 Priorities for !PyLith software development, such as new features and enhancements. This a draft for community comment (Mar 6, 2015).
4
5 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.
6
7 Current development has slowed because Brad Aagaard (who is not funded by CIG) is unable to devote much time to !PyLith development as a result of a substantial increase of other obligations.
8
9 === Version 2.2 (Jun 2015) ===
10
11 # Improve fault formulation for spontaneous rupture [[Image(intermediate.png, 25px)]] 10%
12 * Removes inner solve associated with updating Lagrange multipliers. This will significantly accelerate the nonlinear solve.
13 # Add viscoelastic Drucker-Prager bulk rheology
14
15 === Version 2.3 (late 2015) ===
16
17 # Higher order basis functions [[Image(expert.png, 40px)]] 0%
18 * Allow user to select order of basis functions independent of the mesh (which defines the geometry). This permits higher resolution for a given mesh.
19 # Reorganize top-level code to conform to layout needed for multiphysics [[Image(difficult.png, 25px)]] 0%
20 * Setup modular approach for specifying governing equations and computing residuals and Jacobians.
21 # Reorganize top-level code to allow different startup cases [[Image(intermediate.png, 25px)]] 0%
22 * Elastic prestep
23 * User-specified initial solution
24 * Checkpoint via special spatial database?
25 # Multilevel nonlinear solve
26 # Radial basis functions for spatial databases [[Image(intermediate.png, 25px)]] 0%
27
28 === Version 3.0 (Spring 2016) ===
29
30 # Multiphysics
31 * Incompressible elasticity via a pressure field [[Image(difficult.png, 25px)]]
32 * Elasticity + heat flow [[Image(difficult.png, 25px)]]
33 * Elasticity + fluid flow [[Image(difficult.png, 25px)]]
34 # GUI interface for specifying parameters
35 # Switch to using PETSc time-stepping (TS) algorithms. [[Image(intermediate.png, 25px)]] 0%
36 * 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.
37 # Begin implementation of data assimilation capabilities via adjoint equation.
38
39 === Version 3.1 (Fall 2016) ===
40
41 # Earthquake cycle modeling [[Image(difficult.png, 25px)]]
42 * Same mesh for dynamic and quasi-static parts (dynamic -> quasi-static, quasi-static -> dynamic, complete cycle)
43 # Create strain hardening/softening 2-D and 3-D Drucker-Prager elastoplastic models. [[Image(intermediate.png, 25px)]]
44 # Moment tensor point sources via equivalent body forces [[Image(difficult.png, 25px)]] 5%
45 * 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.
46
47 === Features for Future Releases ===
48
49 ==== Major features ====
50 # Earthquake Cycle Modeling
51 * Different meshes for dynamic and quasi-static parts [[Image(expert.png, 40px)]]
52 * 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.
53 # Data assimilation
54 * Use flexibility of multiphysics implementation to support inclusion of data assimilation [[Image(expert.png, 40px)]]
55
56 ====Minor features ====
57 # Use KD tree search algorithm to allow output of time histories at an arbitrary location [[Image(difficult.png, 25px)]]
58 # Combined prescribed slip / spontaneous rupture fault condition [[Image(difficult.png, 25px)]]
59 * 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.
60 -
# Use threading to accelerate integrations on multi-core machines. [[Image(difficult.png, 25px)]]
+
# Use threading to accelerate integrations on multi-core machines. [[Image(difficult.png, 25px)]]
61 +
----
62 +
==== difficulty rating system ====
63 +
64 +
||[[Image(intermediate.png, 25px)]] intermediate
65 +
66 +
||[[Image(difficult.png, 25px)]] difficult
67 +
68 +
||[[Image(expert.png, 40px)]] expert
69 +
70 +
||
71 +
72 +
''based on the ski trail rating system''