Fix bug in computing total moments in A frame #177
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
ArturoMS13
approved these changes
Oct 21, 2021
There was a problem hiding this comment.
Thank you for the fixing, it is good to be merged.
In my PR #176 I have moved "extract resultants" as a method of "StructuralTimeStepInfo" such that it does not depend on the solver and it can be called as:
tstep.extract_resultants(self.data.structure, force_type=['steady', 'unsteady', 'grav']).
I will update it myself on the PR when the time comes.
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.
Fixes bug in
AeroforcesCalculator, where the total moments at the A frame reference location did not include the contribution from the nodal forces, it just summed over the nodal moments.