-
Notifications
You must be signed in to change notification settings - Fork 285
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
DM type 'libmesh' did not attach the DM to the matrix #3802
Comments
Just to be clear, you are using the same version of libmesh in both places, and when you say "move it" you mean that you re-complied both your application and libmesh itself using the native compilers of each system? Which version (or git hash) of libmesh are you using exactly? |
I want to emphasize that when I use |
OK, well I see some relevant looking commented out code in nonlinear_implicit_system.C:
The commented lines were added in 7a24259 by @roystgnr but there's no hint as to why they are commented out? This doesn't necessarily explain why you would see different behavior from different versions of PETSc, though. I don't know much about how the |
@jwpeterson It seems that this issue is not caused by |
@jltuhnu are you saying that you are not using fieldsplit preconditioner (even via PETSc command line args) and you are still getting that same error message ( |
@jwpeterson |
I want to use
petsc_auto_fieldsplit(pc, system)
, The following code runs successfully on my mac (libmesh+petsc-3.19.0), but when I move it to the supercomputing (libmesh+petsc-3.18.0), it throws the petsc error.The text was updated successfully, but these errors were encountered: