extend(idm): update fortran dfns for advanced and subpackages #1517
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
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.
These updates are forward looking and are intended to support input loading of advanced and subpackages. Advanced packages are marked as such with the already existing
# package-type advanced-stress-packagetagline in dfn files. A new tag# mf6 subpackage <subp>identifies one subpackage- any number of these can be added to a dfn. The subpackage identifier follows the naming convention for dfn files themselves, so to add TVK to NPF as a subpackage the entire tagline would be# mf6 subpackage utl-tvk.A subpackage tagline should be added to a package only if both packages are already IDM integrated. This means that each package does not use a parser to read it's own input file but rather sources it's input from the input context.