Open lefebvrera opened 5 years ago
Yeah - we are aware of this issue. In fact it's one of our very oldest #727.
Those errors come from PETSc. We strip some options from the command line object but not all because we don't always know which options are ours, libMesh's, or PETSc's at the application or even MOOSE level. When they get passed to PETSc, it complains. Several developers have attempted fixes over the years but none of them completely satisfactory. The nasty problem is that PETSc can't know all of the options that it uses until the simulation has been completed. This is because many of the options are processed on-demand as the various modules in PETSc get loaded in used. There is no single up-front pass to do this checking.
That being said, it should be easy enough to fix the most egregious offenders as you've specified here.
@fdkong - Do you have anything to add?
You are seeing these warnings possibly because you are using the debug version of PETSc. The optimized version of PETSc should not give any warnings.
It is nontrivial to get PETSc print the `right" left options because it is hard to distinguish which options should go to moose, which ones should go to libmesh, and others for PETSc. Even worse, users can define whatever command line options they want to use.
@fdkong you make an interesting note regarding the debug version. @mbairdphys is investigating. He mentioned there appears to be potential that when building some of these MOOSE Apps in RELEASE the PETSc dependency can be built in DEBUG depending on the environment. I haven't heard a final summary. Does this sound familiar?
Yeah - the connection of debug PETSc and debug libMesh/MOOSE are separate and independent. In our package we only build release versions of PETSc so this must be intentional in the environments you are working with.
I think it's still reasonable to remove the parameters from the CLI args that we know about (e.g. MOOSE's parameters), which will remove many of these warnings when users do happen to have debug versions of PETSc. I'll leave this ticket open.
Bug Description
Several (most?) legal command line options produce a warning message indicating it was not used.
Steps to Reproduce
I.e., using Argonne's System Analysis Module:
or using Idaho's BISON Fuel Performance code:
Impact
This warning is emitted into the application's standard output. The MOOSE application's coupling to the NEAMS Workbench via the
--definition
command line option is broken because the WARNING messages cause syntax errors in the resulting processing of the input schematic in the NEAMS Workbench.These WARNINGS do not appear to be accurate as the command line options are legal.