Re: [Libmesh-users] make check reduced_basis_ex7 flags

[John P. <jwp...@gm...>]

On Sun, May 10, 2020 at 10:08 PM <ed...@op...> wrote:

> Hi.
>
> I want to know if libMesh++ is actually using mumps and superlu, and if
> it is not how to fix it. I just recompiled libMesh++, and I am getting
> the following message with the reduced_basis_ex7 (this is actually an
> improvement, because it used to crash at that point). Thanks!
>
> #+begin_EXAMPLE
>
>    ... snip 8<  ...
>
>    ,***************************************************************
>    ,* Running Example reduced_basis_ex7:
>    ,*   ./example-opt -online_mode 1 -pc_factor_mat_solver_package
> superlu
>    ,***************************************************************
>
>
This message is from libMesh (BTW what is libMesh++?):


>    LibMesh was configured with PETSc >= 3.9, but command-line options use
> deprecated syntax. Skipping now.
>

And these messages are from PETSc:

   WARNING! There are options you set that were not used!
>    WARNING! could be spelling mistake, etc!
>    There are 2 unused database options. They are:
>    Option left: name:-online_mode value: 1
>    Option left: name:-pc_factor_mat_solver_package value: superlu
>

I think this is all working as intended, since if you look at run.sh for
reduced_basis_ex7, you can see that we run all four combinations of
"type"/"package" and "mumps"/superlu" from the script, relying on the logic
within the example itself to skip those cases which don't apply. If you
want to test whether it's working you can run the example manually with the
different cases and inspect the output of each one rather than running the
full "make check". The examples must be run from the build directory, so
for example to test mumps with PETSC >= 3.9 (assuming $LIBMESH_SRC/build is
the location of your build directory):

cd $LIBMESH_SRC/build/examples/reduced_basis/reduced_basis_ex7
./example-opt -online_mode 0 -ksp_type preonly -pc_type lu
-pc_factor_mat_solver_type mumps

Finally, there is one last check you can do, which is to look at (again,
from the build directory) the include/libmesh_config.h file and inspect the
values of the

LIBMESH_PETSC_HAVE_MUMPS
LIBMESH_PETSC_HAVE_SUPERLU_DIST

preprocessor defines.



>    ,***************************************************************
>    ,* Done Running Example reduced_basis_ex7:
>    ,*   ./example-opt -online_mode 1 -pc_factor_mat_solver_package
> superlu
>    ,***************************************************************
> #+end_EXAMPLE
>
> I get a similar message above with mumps. I am attaching my config.log
> as a tar ball
>

This mailing list does not allow attachments.

-- 
John