Update fv3_physics_tend for new FV3 output format

[ahijevyc]

Replace italics below with details for this issue.

Describe the Enhancement

Update contributed/fv3_physics_tend
Read and plot FV3 physics tendencies from new FV3 output format.

Time Estimate

Estimate the amount of work required here.
7 days

Sub-Issues

Consider breaking the enhancement down into sub-issues.

• adapt planview_fv3.py for new formulation of no-physics (advection) tendency. Now it is reset every output just like the other tendencies. This simplifies the code. However, it can't simply be addressed in the config file.
• adapt cross_section_vert.py for new nophys
• adapt vert_profile_fv3.py for new nophys
• add "actual" tendency panel to the multi-panel plan view plot
• add --robust command line option to control colormap range to planview_fv3.py and cross_section_vert.py
• fix bug in time-averaging window in planview, cross_section_vert, and vert_profile_fv3.
• retain units on xarray xaxis in vert_profile_fv3.py
• add vmin, vmax to planview and cross section
• add xmin, xmax to vert_profile_fv3.py
• clean code, leaving out unnecessary function arguments, use pep8 filter
• update history file
• update example plot output PNGs

Relevant Deadlines

NONE

Funding Source

NONE

Define the Metadata

Assignee

• Select engineer
• Select scientist

Labels

• Select component(s)
• Select priority
• Select requestor(s) Gerard Ketefian - NOAA Affiliate gerard.ketefian@noaa.gov Sarah Womantree - NOAA Affiliate sarah.womantree@noaa.gov

Projects and Milestone

• Select Repository and/or Organization level Project(s) or add alert: NEED CYCLE ASSIGNMENT label
• Select Milestone as the next official version or Future Versions

Define Related Issue(s)

Consider the impact to the other METplus components.

• METplus, MET, METdataio, METviewer, METexpress, METcalcpy, METplotpy

Enhancement Checklist

See the METplus Workflow for details.

• Complete the issue definition above, including the Time Estimate and Funding Source.
• Fork this repository or create a branch of develop.
  Branch name: feature_<Issue Number>_<Description>
• Complete the development and test your changes.
• Add/update log messages for easier debugging.
• Add/update unit tests.
• Add/update documentation.
• Add any new Python packages to the METplus Components Python Requirements table.
• Push local changes to GitHub.
• Submit a pull request to merge into develop.
  Pull request: feature <Issue Number> <Description>
• Define the pull request metadata, as permissions allow.
  Select: Reviewer(s) and Development issues
  Select: Repository level development cycle Project for the next official release
  Select: Milestone as the next official version
• Iterate until the reviewer(s) accept and merge your changes.
• Delete your fork or branch.
• Close this issue.