Step 1: Error 4#
Error Message#
1$ pylith step01_gravity.cfg
2
3 >> /software/baagaard/py38-venv/pylith-debug/lib/python3.8/site-packages/pylith/meshio/MeshIOObj.py:44:read
4 -- meshiopetsc(info)
5 -- Reading finite-element mesh
6
7# -- many lines omitted --
8
9 -- Verifying compatibility of problem configuration.
10Fatal error. Calling MPI_Abort() to abort PyLith application.
11Traceback (most recent call last):
12 File "/software/baagaard/py38-venv/pylith-debug/lib/python3.8/site-packages/pylith/apps/PetscApplication.py", line 61, in onComputeNodes
13 self.main(*args, **kwds)
14 File "/software/baagaard/py38-venv/pylith-debug/lib/python3.8/site-packages/pylith/apps/PyLithApp.py", line 108, in main
15 self.problem.verifyConfiguration()
16 File "/software/baagaard/py38-venv/pylith-debug/lib/python3.8/site-packages/pylith/problems/Problem.py", line 177, in verifyConfiguration
17 ModuleProblem.verifyConfiguration(self)
18 File "/software/baagaard/py38-venv/pylith-debug/lib/python3.8/site-packages/pylith/problems/problems.py", line 167, in verifyConfiguration
19 return _problems.Problem_verifyConfiguration(self)
20RuntimeError: Material label_value '3' for cell '3009' does not match the label_value of any materials or interfaces.
Troubleshooting Strategy#
The output shows a Python Traceback and then the error message on Line 20.
The error indicates the finite-element mesh file contains a cell with a label value of 3, but the parameter files do not have a material with a label value of 3.
We examine the pylithapp.problem.materials
sections of pylithapp.cfg
and see that the label values are 0, 1, and 2 in the parameter file rather than 1, 2, and 3.
Resolution#
[pylithapp.problem.materials.slab]
label_value = 1
...
[pylithapp.problem.materials.crust]
label_value = 2
...
[pylithapp.problem.materials.wedge]
label_value = 3
...