Fix Issue #2119 - shrink regional domain slightly

[gspetro-NOAA]

Commit Queue Requirements:

• This PR addresses a relevant WM issue (if not, create an issue).
• All subcomponent pull requests (if any) have been reviewed by their code managers. (N/A)
• Run the full Intel+GNU RT suite (compared to current baselines), preferably on Ursa (Derecho or Hercules are acceptable alternatives). Exceptions: documentation-only PRs, CI-only PRs, etc.
  • Commit log file w/full results from RT suite run (if applicable).
  • Verify that test_changes.list indicates which tests, if any, are changed by this PR. Commit test_changes.list, even if it is empty.
• Fill out all sections of this template.

---

Description:

This PR implements the fix proposed in Issue #2119 for missing values of dyn/phy output in regional regression tests on west and south boundaries.
It also modifies rt.conf to run gnv1_nested_intel on WCOSS2 and Hercules.

Commit Message:

* UFSWM - shrink domain slightly for regional tests; activate gnv1_nested_intel on wcoss2/hercules

Priority:

• Critical Bugfix: Reason
• High: Reason
• Normal

Git Tracking

UFSWM:

• Closes missing values of dyn/phy output in regional regression test on west and south boundaries #2119
• Closes gnv1_nested_intel intermittent inability to match against WM baselines on wcoss/hercules/orion #2127

Sub component Pull Requests:

• None

UFSWM Blocking Dependencies:

• Blocked by #
• None

Documentation:

• Documentation update required.
  • Relevant updates are included with this PR.
  • A WM issue has been opened to track the need for a documentation update; a person responsible for submitting the update has been assigned to the issue (link issue).
• Documentation update NOT required.
  • Explanation: Fix does not affect documented capabilities

---

Changes

Regression Test Changes (Please commit test_changes.list):

• PR Adds New Tests/Baselines.
• PR Updates/Changes Baselines.
• No Baseline Changes.

Input data Changes:

• None.
• PR adds input data.
• PR changes existing input data.

Library Changes/Upgrades:

• Required
  • Library names w/versions:
  • Git Stack Issue (JCSDA/spack-stack#)
• No Updates

---

Testing Log:

• RDHPCS
  • Hera
  • Orion
  • Hercules
  • GaeaC6
  • Derecho
  • Ursa
• WCOSS2
  • Dogwood/Cactus
  • Acorn
• CI
• opnReqTest (complete task if unnecessary)

[gspetro-NOAA]

gnv1_nested_intel failed this time on Hercules, so I'm wondering if the intermittent failures are still present... 🤔 I'll see what it does the second time. @BrianCurtis-NOAA if things fail on WCOSS2, we can just revert the changes to rt.conf and proceed with the rest of the PR.
UPDATE: I forgot to create a new baseline for it, so no wonder it failed. 🤦‍♀️

[BrianCurtis-NOAA]

gnv1_nested_intel failed this time on Hercules, so I'm wondering if the intermittent failures are still present... 🤔 I'll see what it does the second time. @BrianCurtis-NOAA if things fail on WCOSS2, we can just revert the changes to rt.conf and proceed with the rest of the PR. UPDATE: I forgot to create a new baseline for it, so no wonder it failed. 🤦‍♀️

Great, but we don't need to add it to test_changes.list because it will still work without bl change on the platforms that run it still, correct?

[gspetro-NOAA]

@BrianCurtis-NOAA Yes, it should work on platforms that run it already, but since Hercules & WCOSS2 will both require new baselines, it seems to me like it should still go in test_changes.list. If we run ./rt.sh -a <account> -c -b test_changes.list -e without it, it'll fail on WCOSS2 & Hercules and require the addition of that test manually to the file. Or is that preferred to know for certain that running that command didn't lead to unexpected baseline changes on platforms that were already running the test?