example: ttb use in LS-Dyna #11
Open
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
(commented program, umat-utan-code, picture for doc) (first pull request, bear with me)
|
Wow nice work - thank you. Will have a look at it! |
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.
Here is the LS-Dyna example for the documentation. I implemented a standard Neo-Hookean material last week anyway to check some interfaces, so I chose this for the documentation example. The elastoplastic code got a bit involved with regard to the tangent (due to the LS-Dyna umat-utan split), so I guess the minimal Neo-Hookean is more appropriate at first. The picture will probably not be loaded (no clue how to set proper paths), so you can also view it here: example_neohooke-LSDYNA. Hopefully, the remaining formatting is okay (I'm used to Doxygen).
Herein, I also tested the approach to use different modules. To avoid mixing things up, further information is collected in a following pull request as a basis for our ongoing discussion.
I hope, I got the pull request right. Just reject it and let me redo it, in case something is fubar.