Lubby2 incremental form #2602
Merged
Lubby2 incremental form #2602
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Just curious, what is the advantage/difference? |
endJunction
approved these changes
Aug 11, 2019
|
The rate and incremental forms make it easier to work with non-zero initial states and some coupling terms than with the absolute form. The incremental form avoids dividing by dt in the Jacobian which could be beneficial for some ratios between loading and relaxation rates. |
endJunction
force-pushed
the
Lubby2Incremental
branch
from
dca9264
to
f42377c
Compare
|
OpenGeoSys development has been moved to GitLab. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a minor change to Lubby2 switching from rate form to incremental form. Preparation for an upcoming model comparison.