New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Petsc names #208
Petsc names #208
Commits on Feb 27, 2014
-
-
-
KSPSetOptionsPrefix calls PCSetOptionsPrefix
So we don't need to do so redundantly
-
-
-
-
-
-
-
-
-
-
-
-
Trying to add --solver_group_foo options
Not working yet, but need to checkpoint here.
-
-
Postpone library-level init() as late as possible
That way we don't preclude a physics-aware init(Matrix) from user code. This will hopefully fix some MOOSE regressions
-
Got Schur complement fieldsplit working
The two last catches: libMesh::on_command_line didn't work the way I had assumed, so I replaced it with code that does. For multiplicative and schur fieldsplits, PETSc really cares what order you declare fields in. But we can get arbitrary order by simply putting everything in a group, because std::map orders groups alphabetically and libMesh declares group fields in container order.
Commits on Feb 28, 2014
-
This fixes a case of local_variable_indices returning a non-local index, and adds an assert to see that it doesn't happen again. -pc_type_fieldsplit works correctly in parallel now.
-
Commits on Mar 12, 2014
-
Postpone automatic NonlinearSolver initialization
This should increase backwards compatibility of the petsc_names changes, and in particular should hopefully fix more of the MOOSE regressions.