Step 6: Error 4#
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: Error occurred while reading spatial database file 'fault_slip.spatialdb'.
15Read data for 3 out of 4 points.
16Error reading coordinates from buffer ''.
Troubleshooting Strategy#
The error message on lines 14-15 indicates there is an error reading the fault_slip.spatialdb
spatial database for the fault slip.
PyLith was able to read data for 3 of 4 points.
The file fault_slip.spatialdb
contains only 3 points but num-locs
is 4.
Resolution#
# Error
num-locs = 4
# Correct
num-locs = 3