Enhancement: Update several METplus Use Cases to restore output for the `FULL` domain

[JohnHalleyGotway]

Describe the Enhancement

Issue dtcenter/MET#3298 and linked pull request dtcenter/MET#3321 modified the default behavior of MET Point-Stat, Grid-Stat, Pair-Stat, and Ensemble-Stat tools. Rather than setting mask.grid to include the FULL domain in their default configuration files, the default behavior has moved moved to the application code itself.

• The default config files of these tools NO LONGER define any masking regions.
• Users are encouraged to define whatever masking regions they'd like in their own config file.
• If no masking regions are defined at runtime, the tools add mask.grid equal to FULL by default.

In METplus, any Use Case that does not override the default mask.grid setting was generating output for the FULL domain by default. After this change, the output for that FULL domain is gone.

As discussed during the METplus project meeting on Feb 3, 2026, the scientists recommend that we modify the configurations of the affected use cases by adding mask.grid equal to FULL to restore the METplus Use Case output back to what it was before this change in MET.

1. For this issue, inspect the 14 of 69 affected use cases in this recent METplus Testing Workflow run. Update their configurations to also request output for the FULL domain.

2. Update the METplus Upgrade Instructions to note this change.

Time Estimate

2 hours.

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) or no engineer required
• Select scientist(s) or no scientist required

Labels

• Review default alert labels
• Select component(s)
• Select priority
• Select requestor(s)

Milestone and Projects

• Select Milestone as a METplus-Wrappers-X.Y.Z version, Consider for Next Release, or Backlog of Development Ideas
• For a METplus-Wrappers-X.Y.Z version, select the METplus-Wrappers-X.Y.Z Development project

Define Related Issue(s)

Consider the impact to the other METplus components.

• METplus, MET, METdataio, 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.
• Add any new Python packages to the METplus Components Python Requirements table.
• For any new datasets, an entry to the METplus Verification Datasets Guide.
• 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 Development issue
  Select: Milestone as the next official version
  Select: METplus-Wrappers-X.Y.Z Development project for development toward the next official release
• Iterate until the reviewer(s) accept and merge your changes.
• Delete your fork or branch.
• Close this issue.