Local coordinate system: x_e axis from JSON file for circular beams and legend#11
Merged
Merged
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 PR addresses issue: #10
The SubDyn JSON output file has been updated to include the local x_e axis (see OpenFAST/openfast#3310).
With this change, viz3Danim is now fully compatible with the SubDyn spin angle (
MSpin). The implementation supports both the updated JSON format and legacy files that do not include the x_e field. As a result, the code should handle all supported formats without exceptions.In addition, a legend for the local coordinate system axes has been included:
This local coordinate system is also compatible with the white background:
