Make polar ice plot more configurable

[bikegeek]

Describe the Enhancement

The polar ice plot can only be generated if it is invoked in a directory that has the polar_ice.yaml file. Some users will need the flexibility to invoke the polar_plot.py script from a directory that doesn't contain the polar_ice.yaml file. Some users will need to be able to specify the location of a configuration file which they can edit to point to the location of input data.

Replacing this code:

yaml_file_name = "polar_ice.yaml"
try:
config = yaml.load(
open(yaml_file_name), Loader=yaml.FullLoader)

with code that will support any configuration file (i.e. not limited to only a file named polar_ice.yaml) that is defined with the full file path. Currently, the yaml loader is looking for a polar_ice.yaml file that is in the current working directory.

Time Estimate

Estimate the amount of work required here.
~ 1 1/2 days

Sub-Issues

Consider breaking the enhancement down into sub-issues.

• Add a checkbox for each sub-issue here.

Relevant Deadlines

List relevant project deadlines here or state NONE.

Funding Source

Define the source of funding and account keys here or state NONE.

Define the Metadata

Assignee

• Select engineer(s) Minna Win
• Select no scientist required

Labels

• Select component(s)
• Select priority
• Select requestor(s)

Projects and Milestone

• Select Repository and/or Organization level Project(s) or add alert: NEED PROJECT 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, METdatadb, 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.
• 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 Linked 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.