Description
"FV3LAM" is an old way to refer to the limited-area version of the FV3 dycore, from the earliest days of the regional_workflow repository. We have long since moved on in terminology to more specific and correct terms, but some old relics remain in the workflow: particularly, the name of the workflow generation script generate_FV3LAM_wflow.py and the Rocoto XML file FV3LAM_wflow.xml.
Solution
Rename generate_FV3LAM_wflow.py --> generate_workflow.py, FV3LAM_wflow.xml --> SRW_workflow.xml, or something similar.
There are also a number of old relic NCL scripts with this name under ush/NCL/; since NCL is not supported (and hasn't been for many years) these should probably removed.
Requirements**
Remove references to FV3LAM unless specifically correct.
Acceptance Criteria (Definition of Done)
No more "FV3LAM" references in SRW unless specifically correct.
Description
"FV3LAM" is an old way to refer to the limited-area version of the FV3 dycore, from the earliest days of the regional_workflow repository. We have long since moved on in terminology to more specific and correct terms, but some old relics remain in the workflow: particularly, the name of the workflow generation script
generate_FV3LAM_wflow.pyand the Rocoto XML fileFV3LAM_wflow.xml.Solution
Rename
generate_FV3LAM_wflow.py-->generate_workflow.py,FV3LAM_wflow.xml-->SRW_workflow.xml, or something similar.There are also a number of old relic NCL scripts with this name under
ush/NCL/; since NCL is not supported (and hasn't been for many years) these should probably removed.Requirements**
Remove references to
FV3LAMunless specifically correct.Acceptance Criteria (Definition of Done)
No more "FV3LAM" references in SRW unless specifically correct.