@@ -204,21 +204,20 @@ def showHelp(self):
204
204
" Running pylithinfo --verbose [-o pylith_parameters.txt] [PyLith args]\n "
205
205
" will dump all parameters with descriptions to pylith_parameters.txt.\n "
206
206
"\n "
207
- "For quasi-static simulations, use the following solver settings to make sure the linear and nonlinear solvers are converging:\n "
208
- "[pylithapp.petsc]\n "
209
- "ksp_converged_reason = true\n "
210
- "ksp_error_if_not_converged = true\n "
211
- "snes_converged_reason = true\n "
212
- "snes_error_if_not_converged = true\n "
207
+ "Add $PYLITH_DIR/share/settings/petsc_monitor.cfg to your command line arguments\n "
208
+ "to turn on several PETSc monitors:"
209
+ " pylith YOUR_FILE.cfg PATH_TO_PYITH_SHARE/share/settings/petsc_monitor.cfg\n "
213
210
"\n "
214
- "If you still need help, send an email to [email protected] with the following info:\n "
211
+ "If you still need help, visit the PyLith category on the CIG community forum:\n "
212
+ "https://community.geodynamics.org.\n "
213
+ "When submitting a question about running a simulation, be sure to include the info:\n "
215
214
"\n "
216
215
"1. Describe what you are trying to do\n "
217
216
" a. Overview of the problem and boundary conditions (diagrams are very helpful)\n "
218
217
" b. 2-D or 3-D\n "
219
218
" c. Cell type (tri, quad, hex, or tet)\n "
220
219
" d. Type of fault: prescribed slip or spontaneous rupture\n "
221
- "2. Include the output of running 'pylith --version' \n "
220
+ "2. Attach the PyLith parameters .json file \n "
222
221
"3. Send the *entire* error message, not just what you think is important (entire log is best).\n "
223
222
"\n "
224
223
"Description and help for PyLithApp component:\n "
0 commit comments