Bugfix #3410 ugrid lead time develop

[hsoh-u]

Expected Differences

The init_hour (or lead_time) is computed.

1. If the time variable has the units minutes/hours since YYYY-MM-DD, sets init_time from the units attribute.
2. If init_time variable is configured at the UGrid configurations, read the init_time variable and sets oroverride init_time
3. Compute init_hour/lead_time from the time variable and init_time variable

As a result, the 7 output file names were changed from *_000000_* to _120000_ because init_hour 00 was changed to 12. The FCST_LEAD column at the output files were changed too.

The unit.py was updated to handle missing output files and initialized the result object to None

Refactored UGridFile::open_metadata() at ugrid_file.cc and separated two APIs: metadata_coord_variables() and metadata_time().

• Do these changes introduce new tools, command line arguments, or configuration file options? [No]
  
  If yes, please describe:
  

• Do these changes modify the structure of existing or add new output data types (e.g. statistic line types or NetCDF variables)? [No]
  
  If yes, please describe:
  

Pull Request Testing

• Describe testing already performed for these changes:
  

by unit test
The binary files are available at seneca:/d1/personal/hsoh/git/pull_request/MET_bugfix_3410_ugrid_lead_time_develop/share/met
Note:
/d1/personal/hsoh/git/pull_request/MET_bugfix_3410_ugrid_lead_time_develop/share/met/config/UGridConfig_mpas should be applied to compute lead_hour (to read the initial_time variable).

• Recommend testing for the reviewer(s) to perform, including the location of input datasets, and any additional instructions:
  

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

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

The tests themselves were not updated, but the existing tests are now producing different outputs — specifically, the file name and init_hour columns differ across the 7 files.

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

The output file names are different (from 000000 to 120000). The values in the init_hour columns have also changed.

• Will this PR result in changes to existing METplus Use Cases? [Yes]
  
  If yes, create a new Update Truth METplus issue to describe them.

The output file names changed from 000000 to 120000. If these are used as input for the test cases, the expected input files may no longer exist. The values in the init_hour columns have also changed.

• Do these changes introduce new SonarQube findings? [No]
  
  If yes, please describe:

• Please complete this pull request review by [Fill in date].
  

Pull Request Checklist

See the METplus Workflow for details.

• Review the source issue metadata (required labels, projects, and milestone).
• 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) and Development issue
  Select: Milestone as the version that will include these changes
  Select: METplus-X.Y Support project for bugfix releases or MET-X.Y Development project for the next coordinated release
• After submitting the PR, select the ⚙️ icon in the Development section of the right hand sidebar. Search for the issue that this PR will close and select it, if it is not already selected.
• 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.

[DanielAdriaansen]

Same changes as in #3424

[DanielAdriaansen]

@hsoh-u I also suggest we update the MPAS test data for the UGRID capability as part of this PR. Could you try running the unit tests with this file on Seneca?

/home/dadriaan/projects/mpas/tutorial/data/fcst/mpas/ugrid/OK_12km_ugrid/2025051800/ens_1/diag.2025-05-18_12.00.00.nc

Here is the static file:
/home/dadriaan/projects/mpas/tutorial/data/fcst/mpas/ugrid/OK_12km_ugrid/init.nc

[sonarqubecloud]

Quality Gate passed

Issues
2 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
1.1% Duplication on New Code

See analysis details on SonarQube Cloud