Subcase/mode output fixes#247
Merged
Bruno02468 merged 7 commits intoJun 6, 2026
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
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.
You know how, before each data block in the F06, you usually see something like:
OUTPUT FOR SUBCASE 2(orEIGENVECTOR), often followed by the deck title and, if applicable, subcase title and label? Yeah? Well, turns out that:LINK4),This PR aims to fix all that:
LINK 9ones), writing the headings has been centralised into the aptly-namedWRITE_SUBCASE_EIGENVEC_HEADERsubroutine, increasing consistency and getting rid of reduncancies (hence the negative diff);LINK 9) blocks I could find, I just fixed it locally, since there were too few and it was all in the same subroutine already (EIG_SUMMARY). I couldn't use theLINK 9one because not everything's in the same allocation state, so to speak.That fixes the listed issues, makes our F06 far more consistent and, honestly, it also looks better.
Any downsides? Yeah, it probably breaks your F06 parser -- it broke mine!
P.S.: oh, and there's a bonus fix, I got tid of a hardcoded
JTSUBinLINK9.f90that could produce incorrect output for buckling decks with more than one static case.