You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGES.md
+5-3Lines changed: 5 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,16 +17,18 @@ The version numbers are in the form `MAJOR.MINOR.PATCH`, where major releases in
17
17
* Update PETSc to 3.23.1
18
18
***Added**
19
19
* Improved documentation for `pylith_eqinfo` and illustrate use in `examples/strikdslip-2d`, `examples/crustal-strikeslip-2d`, and `examples/crustal-strikeslip-3d`.
20
-
*Add`pylith_convertmesh` for converting Cubit and Gmsh files to the PETSc HDF5 mesh format.
21
-
*Add support for specifying boundary conditions using marked boundaries rather than vertices.
20
+
*Added`pylith_convertmesh` for converting Cubit and Gmsh files to the PETSc HDF5 mesh format.
21
+
*Added support for specifying boundary conditions using marked boundaries rather than vertices.
22
22
*`MeshIOAscii`: Use `face-group` for specifying boundary conditions via cell and `face` vertices.
23
23
*`MeshIOCubit`: Read sidesets from ExodusII files (generated by Cubit).
24
24
*`MeshIOPetsc`
25
25
*`Gmsh`: Create physical groups only at the dimension of the boundary.
26
-
* Add compatibility for reading PETSc HDF5 format
26
+
* Added compatibility for reading PETSc HDF5 format
27
+
* Improved the organization of the governing equations section and added documentation for poroelasticity with prescribed fault slip, including governing equations and default PETSc solver settings. Also added a full-scale test.
27
28
***Fixed**
28
29
* Account for processes without cells in initial condition patch when verifying configuration.
29
30
* Avoid divide by zero for `KinSrcRamp` when final slip is zero.
31
+
* Remove `solid_bulk_modulus` as a spatial database field for poroelasticity; compute it from the other fields.
If you have PyLith source code on your local machine, then it is best to start VS Code from a terminal in which you have activated the PyLith virtual environment.
0 commit comments