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
Eigenvalue executioner improvement for supporting Picard iteration #12767
Comments
Tag @fdkong . |
I will take care of this once the |
Thanks Fande. The tests are at bf7d106. |
Has there been any progress on this issue, or maybe a workaround? I've been getting the "Argument out of range, too many EPS monitors set" error on the third solve when using |
I have added some fixes to libmesh side, and it might help. Could you take a try, and report it back |
Make sure you have this commit libMesh/libmesh#2160 |
Your fixes worked! Thank you! |
I can confirm that eigenvalue problem as a MultiApp is now working, although some minor output issues. Also there is no way to let the eigenvalue subapp to use the previous solution as the initial guess. Eigenvalue problem as master still does not work. |
I'd like this issue to be reopened because Item 3 when Another very important desired improvement: |
Rationale
During refactoring Picard iteration to enable Picard iteration for steady-state calculations including eigenvalue calculations, I found few issues.
When
Eigenvalue
is master:EigenSystem
does not support evaluating L2 norm of the entire residual of the eigen problem;When
Eigenvalue
is sub-app:instead of
Description
These issues need to be fixed. Actually our major motivation of switching to the new eigenvalue executioner is to make the Picard iteration for multiphysics calculations simpler and more efficient.
Impact
Better usability of the new eigenvalue solver.
The text was updated successfully, but these errors were encountered: