Bugfix: Fix inconsistent Weather Regime classification numbers when the forecast is reordered

[CPKalb]

Replace italics below with details for this issue.

Describe the Problem

The weather regime classification is performed separately on the model and observations. Both are ordered by frequency (the most frequent regime listed first). Because of this, sometimes the regime numbers don't match (i.e. regime 1 in the observation may have the same weather pattern as regime 2 in the model or something similar). Reordering is currently done after the classification text file is written but before the plots, which means the numbers are inconsistent between the plots and files. This reordering needs to happen before the text file is written. This reordering needed to be moved from the Kmeans program in METcalcpy to a separate program, and then the program needs to be called at a different time from METplus

Expected Behavior

Reordering needs to happen before the text file is written

Environment

Describe your runtime environment:
*1. linux
2. OS: (e.g. RedHat Linux, MacOS)
*3. python 3.7.9

To Reproduce

Run the weather regime use case. The case runs successfully but the output is inconsistent

Relevant Deadlines

List relevant project deadlines here or state NONE.

Funding Source

2793541

Define the Metadata

Assignee

• Select engineer(s) or no engineer required
• Select scientist(s) or no scientist required

Labels

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

Projects and Milestone

• Select Organization level Project for support of the current coordinated release
• Select Repository level Project for development toward the next official release or add alert: NEED PROJECT ASSIGNMENT label
• Select Milestone as the next bugfix version

Define Related Issue(s)

Consider the impact to the other METplus components.

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

Bugfix 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 main_<Version>.
  Branch name: bugfix_<Issue Number>_main_<Version>_<Description>
• Fix the bug 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 main_<Version>.
  Pull request: bugfix <Issue Number> main_<Version> <Description>
• Define the pull request metadata, as permissions allow.
  Select: Reviewer(s) and Linked issues
  Select: Organization level software support Project for the current coordinated release
  Select: Milestone as the next bugfix version
• Iterate until the reviewer(s) accept and merge your changes.
• Delete your fork or branch.
• Complete the steps above to fix the bug on the develop branch.
  Branch name: bugfix_<Issue Number>_develop_<Description>
  Pull request: bugfix <Issue Number> develop <Description>
  Select: Reviewer(s) and Linked issues
  Select: Repository level development cycle Project for the next official release
  Select: Milestone as the next official version
• Close this issue.