Investigate GASP historical names in meta_data

[cmbenne3]

Desired capability or behavior.

GASP supports overwriting 'internal' variables by specifying them outside of the namelists in the input file - for example:

We currently have an existing naming convention for legacy code variables in metadata, which is detailed in develop_metadata.py, but it does not include listing variables outside of namelists:

This issue involves:

• Deciding if Aviary needs to support the GASP functionality of overwriting variables outside of namelists
• Check the behavior of the fortran_to_aviary conversion utility using the current naming conventions in metadata
• Modify fortran_to_aviary and/or the meta data naming conventions to ensure Aviary has the required functionality
• Sweep through and update any meta data entries that need updating as a result of the changes

Suggested implementation.

No response

[xjjiang]

The line VGL=150 in the screenshot is just a comment. According to Jeff, "The 'comments' must be either in the title line (1st line), or after the last GASP namelist to be read in". I think this issue should be closed.