Step 6: Error 5#
Error Message#
1$ pylith step06_twofaults.cfg
2
3 -- Initializing timedependent problem with quasistatic formulation.
4Fatal error. Calling MPI_Abort() to abort PyLith application.
5Traceback (most recent call last):
6 File "/software/baagaard/py38-venv/pylith-debug/lib/python3.8/site-packages/pylith/apps/PetscApplication.py", line 61, in onComputeNodes
7 self.main(*args, **kwds)
8 File "/software/baagaard/py38-venv/pylith-debug/lib/python3.8/site-packages/pylith/apps/PyLithApp.py", line 110, in main
9 self.problem.initialize()
10 File "/software/baagaard/py38-venv/pylith-debug/lib/python3.8/site-packages/pylith/problems/Problem.py", line 188, in initialize
11 ModuleProblem.initialize(self)
12 File "/software/baagaard/py38-venv/pylith-debug/lib/python3.8/site-packages/pylith/problems/problems.py", line 170, in initialize
13 return _problems.Problem_initialize(self)
14RuntimeError: Could not find value 'final_slip_opening' in spatial database 'Fault rupture for main fault'. Available values are:
15 final-slip-left-lateral
16 final-slip-opening
17 initiation-time
Troubleshooting Strategy#
We have more errors with fault_slip.spatialdb
.
The error message on lines 14-17 shows that PyLith is looking for final_slip_opening
in the spatial database, but it found final-slip-opening
instead.
We need to change the dashes (used in PyLith v1.x and v2.x) to underscores (used in PyLith v3.x); we made this change to be consistent with the names of the output fields.
Resolution#
# Error
value-names = final-slip-left-lateral final-slip-opening initiation-time
# Correct
value-names = final_slip_left_lateral final_slip_opening initiation_time