[ ] Describe testing already performed for these changes:
@michelleharrold and @jwolff-ncar rebuilt new Python image from scratch. @michelleharrold double checked that the version in the container match what was specified in the Dockerfile. @jwolff-ncar re-ran plots to make sure the new image works with our Python scripts.
[ ] Recommend testing for the reviewer(s) to perform:
If someone else would like to try and rebuild and test a case that would be fine, but some testing has already been performed.
[ ] Are any changes to the online tutorial required for this PR? [No]
Not the online tutorial, but we will need to retag 4.0.0
[ ] Will this PR change the output of any of the existing cases? [No]
[ ] Please complete this pull request review by ASAP.
Pull Request Checklist
[ ] Ensure the PR title matches the feature or bugfix branch name.
[ ] Define the PR metadata, as permissions allow:
Select: Reviewer(s), Projects(s), and Milestone.
[ ] After submitting the PR, select Linked issues with the original issue number.
[ ] After the PR is approved, merge your changes, as permissions allow.
[ ] Close the linked issue and delete your feature or bugfix branch from GitHub.
Pull Request Testing
[ ] Describe testing already performed for these changes: @michelleharrold and @jwolff-ncar rebuilt new Python image from scratch. @michelleharrold double checked that the version in the container match what was specified in the Dockerfile. @jwolff-ncar re-ran plots to make sure the new image works with our Python scripts.
[ ] Recommend testing for the reviewer(s) to perform: If someone else would like to try and rebuild and test a case that would be fine, but some testing has already been performed.
[ ] Are any changes to the online tutorial required for this PR? [No] Not the online tutorial, but we will need to retag 4.0.0
[ ] Will this PR change the output of any of the existing cases? [No]
[ ] Please complete this pull request review by ASAP.
Pull Request Checklist