Handmerge develop into MAPL3 2023-Jun-08 #2178
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
…rgparse Update to ESMA_env 4.17.0, move from FLAP to fArgParse
# Conflicts: # Tests/ExtDataDriver.F90 # Tests/pfio_MAPL_demo.F90 # tutorial/driver_app/Example_Driver.F90
This was referenced Jun 8, 2023
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.
Description
This is a handmerge of both
developand #1960 intorelease/MAPL-v3. This is needed due to the move to fArgParse from FLAP in #2068 so the changes tumble into here.Related Issue
Closes #1756
Motivation and Context
Moves MAPL3 away from FLAP.
How Has This Been Tested?
I ran GEOSgcm.x with it and it worked...but I'll make sure.
Types of changes
Checklist: