Pu time increment call back into energy functions #70
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.
Small addendum to Craig's commit.
The
dt
argument was meant to stay as an optional argument to the mechanics functions. The intent was to pass a value in every time you call them, giving you the opportunity to use different values (say for adaptive time stepping). This isn't documented anywhere, so there wasn't a way for Craig to know that. There is an example in the appexamples/uniaxial_dynamic/UniaxialDynamic.py
.The time interface is a little clunky, you can see how the project started with quasi-statics. We could consider adding the current time as an argument to the density functions (like
dt
is), which would make it easier to write time-dependent loads.