Pull Request Testing

• Describe testing already performed for these changes:
  
  Please see issue Fix TC-Stat event equalization logic to include any model name requested using -amodel. #1932 and PR Bugfix 1932 develop event_equal #1933 for details of the problem and changes.

I manually ran the tc_stat commands listed there to confirm that the behavior is now as expected.

• Recommend testing for the reviewer(s) to perform, including the location of input datasets, and any additional instructions:
  
  Review the code changes. I don't think rerunning a full regression test is warranted. Instead, we can just make sure the NB runs fine tonight.

• Do these changes include sufficient documentation updates, ensuring that no errors or warnings exist in the build of the documentation? [No]

No changes.

• Do these changes include sufficient testing updates? [No]

No changes. Rather than changing the NB results for main_v10.0, I updated the tests for the develop branch and think that's a sufficient level of testing.

• Will this PR result in changes to the test suite? [No]
  
  If yes, describe the new output and/or changes to the existing output:
  

• Please complete this pull request review by [Tuesday 10/5/2021].
  

Pull Request Checklist

See the METplus Workflow for details.

• Complete the PR definition above.
• Ensure the PR title matches the feature or bugfix branch name.
• Define the PR metadata, as permissions allow.
  Select: Reviewer(s)
  Select: Organization level software support Project or Repository level development cycle Project
  Select: Milestone as the version that will include these changes
• After submitting the PR, select Linked issues with the original issue number.
• After the PR is approved, merge your changes. If permissions do not allow this, request that the reviewer do the merge.
• Close the linked issue and delete your feature or bugfix branch from GitHub.