Changing how FiberSection3d handles torsion #142
Merged
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
mhscott
referenced
this pull request
Dec 23, 2020
xinlong-du
added a commit
to xinlong-du/OpenSees
that referenced
this pull request
Jul 19, 2021
mhscott
added a commit
that referenced
this pull request
Jul 29, 2021
Make FiberSectionAsym3d consistent with pull request #142
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.
Convergence issues arise when using 3D force-based elements with fiber sections that have torsion aggregated through the SectionAggregator. Changed the FiberSection3d to always take a uniaxial material for torsion. Nothing changes for those who use the -GJ option to specify torsional stiffness for a 3D fiber section.
Also getting rid of FiberSectionGJThermal.