[CIG-SHORT] [petsc-maint] some unexpected error about pylith
Matthew Knepley
knepley at gmail.com
Thu Feb 9 04:44:14 PST 2017
On Thu, Feb 9, 2017 at 3:15 AM, fuqiang shi <shifuqiang121 at gmail.com> wrote:
> Dear, Sir,
>
> Thank you for your reply. The error is totally like this:
>
Please include the mailing list in your replies.
> Linear solve did not converge due to DIVERGED_ITS iterations 100
> [0]PETSC ERROR: --------------------- Error Message
> --------------------------------------------------------------
> [0]PETSC ERROR:
> [0]PETSC ERROR: KSPSolve has not converged
>
This means the linear solver did not converge. For your initial tests I
recommend using a direct solver. This
will help you uncover inconsistencies in the specification, such as bad
boundary conditions. For problems with
no fault
--petsc.pc_type lu
or with a fault use the settings in share/settings/solver_fault_exact.cfg.
When reporting a solver problem, always run with
--petsc.ksp_view --petsc.ksp_pre_view --petsc.ksp_monitor
and send all the output.
Thanks,
Matt
> [0]PETSC ERROR: See http://www.mcs.anl.gov/petsc/documentation/faq.html
> for trouble shooting.
> [0]PETSC ERROR: Petsc Development GIT revision: v3.7.2-876-g7e45237 GIT
> Date: 2016-06-16 04:41:50 -0500
> [0]PETSC ERROR: /home/shifuqiang/pylith/bin/mpinemesis on a arch-pylith
> named tecto-30 by shifuqiang Thu Feb 9 10:10:23 2017
> [0]PETSC ERROR: Configure options --prefix=/home/brad/pylith-binary/dist
> --with-c2html=0 --with-x=0 --with-clanguage=C --with-mpicompilers=1
> --with-debugging=0 --with-shared-libraries=1 --with-64-bit-points=1
> --with-large-file-io=1 --download-chaco=1 --download-ml=1
> --download-f2cblaslapack=1 --with-hwloc=0 --with-ssl=0 --with-x=0
> --with-c2html=0 --with-lgrind=0 --with-hdf5=1 --with-hdf5-dir=/home/brad/pylith-binary/dist
> --LIBS=-lz --with-fc=0 CPPFLAGS="-I/home/brad/pylith-binary/dist/include
> " LDFLAGS="-L/home/brad/pylith-binary/dist/lib " CFLAGS="-g -O2"
> CXXFLAGS="-g -O2 -DMPICH_IGNORE_CXX_SEEK" FCFLAGS=
> PETSC_DIR=/home/brad/pylith-binary/build/petsc-pylith
> PETSC_ARCH=arch-pylith
> [0]PETSC ERROR: #1 KSPSolve() line 847 in /home/brad/pylith-binary/
> build/petsc-pylith/src/ksp/ksp/interface/itfunc.c
> [0]PETSC ERROR: #2 void pylith::problems::SolverLinear::solve(pylith::topology::Field*,
> pylith::topology::Jacobian*, const pylith::topology::Field&)() line 132 in
> ../../../pylith-2.1.4/libsrc/pylith/problems/SolverLinear.cc
> Fatal error. Calling MPI_Abort() to abort PyLith application.
> Traceback (most recent call last):
> File "/home/shifuqiang/pylith/lib/python2.7/site-packages/
> pylith/apps/PetscApplication.py", line 74, in onComputeNodes
> self.main(*args, **kwds)
> File "/home/shifuqiang/pylith/lib/python2.7/site-packages/pylith/apps/PyLithApp.py",
> line 135, in main
> self.problem.run(self)
> File "/home/shifuqiang/pylith/lib/python2.7/site-packages/
> pylith/problems/TimeDependent.py", line 155, in run
> self.formulation.step(t, dt)
> File "/home/shifuqiang/pylith/lib/python2.7/site-packages/pylith/problems/Implicit.py",
> line 212, in step
> self.solver.solve(dispIncr, self.jacobian, residual)
> File "/home/shifuqiang/pylith/lib/python2.7/site-packages/pylith/problems/problems.py",
> line 166, in solve
> def solve(self, *args): return _problems.SolverLinear_solve(self,
> *args)
> RuntimeError: Error detected while in PETSc function.
> application called MPI_Abort(MPI_COMM_WORLD, -1) - process 0
> /home/shifuqiang/pylith/bin/nemesis: mpirun: exit 255
> /home/shifuqiang/pylith/bin/pylith: /home/shifuqiang/pylith/bin/nemesis:
> exit 1
>
>
> 2017-02-07 16:57 GMT+01:00 Matthew Knepley <knepley at gmail.com>:
>
>> On Tue, Feb 7, 2017 at 9:45 AM, fuqiang shi <shifuqiang121 at gmail.com>
>> wrote:
>>
>>> Dear，Sir,
>>> I am sorry to disturb you for some running errors about pylith, and I
>>> have tried all my best to solve them, but no answer.
>>>
>>
>> This is not the PyLith list. You need to mail
>>
>> cig-short at geodynamics.org
>>
>> I have Cc'd it.
>>
>> Also, you need to send the errors. We cannot hope to debug things without
>> error output.
>>
>>
>>> I planed three scheme (s. below and attachment. At the beginning, I
>>> think all of them are very simple), but no one can run all 21 examples
>>> fluently. Especially for "Case 1",all the 21 examples can not run.
>>> All these errors confused me, but I don't know how to solve them.
>>> Could you please give me some suggestion or solution at your earliest
>>> convenient ?
>>> The errors of example3 (Case 3) is also attached (s.attachment).
>>> Your consideration and suggestions upon my request will be highly
>>> appreciated. I am looking forward to your favorable reply at your earliest
>>> convenience.
>>>
>>>
>>> Sincerely,
>>>
>>> Fuqiang
>>> Shi
>>>
>>> Case 1:
>>> Keep almost all the codes and parameters agree with the provided
>>> example, only switch the mesh scheme from ‘hexahedral’ to ‘tetahedral’
>>> The mesh switch code is: volume 1 4 5 6 scheme Tetmesh
>>> Other code is attached : “example_Hex_to_Tet.jou” , and the model is
>>> also attached “example_Hex_to_Tet.exo”
>>> With this model, all the 21 examples can not run any more.
>>>
>>
>> You need to change the reference cell for FEM as well:
>>
>> [pylithapp.problem.materials.domain]
>>
>> quadrature.cell = pylith.feassemble.FIATSimplex
>>
>>
>>>
>>> Case 2:
>>> Keep the model similar to provided example,only give the fault with a
>>> specialized dip. Other code and parameter agree with the provided example.
>>> The mesh scheme is same as the provided, only change the mesh size. The
>>> code is: volume all size 200
>>> Other code is attached : “mine.jou” , and the model is also attached
>>> “mine.exo”
>>> With this model, only the ‘step01.cfg’, ‘step15.cfg’, ‘step16.cfg’,
>>> ‘step17.cfg’, ‘step18.cfg’, ‘step19.cfg’ can run fluently and give out
>>> result.
>>>
>>
>> What was the error?
>>
>> Matt
>>
>>
>>> Case 3:
>>> Keep almost all the code agree with the provided example, only change
>>> the location of 'material_surface' and the mesh size.
>>>
>>
>>
>>
>> --
>> What most experimenters take for granted before they begin their
>> experiments is infinitely more interesting than any results to which their
>> experiments lead.
>> -- Norbert Wiener
>>
>
>
--
What most experimenters take for granted before they begin their
experiments is infinitely more interesting than any results to which their
experiments lead.
-- Norbert Wiener
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.geodynamics.org/pipermail/cig-short/attachments/20170209/5756acf5/attachment-0001.html>
More information about the CIG-SHORT
mailing list