Skip to content

TEMPO code cleanup and refactor for v3.0.0 and MPAS release#192

Merged
clark-evans merged 26 commits intoufs-community:gsl/developfrom
AndersJensen-NOAA:tempo_v3.0.0_formatting
Feb 26, 2026
Merged

TEMPO code cleanup and refactor for v3.0.0 and MPAS release#192
clark-evans merged 26 commits intoufs-community:gsl/developfrom
AndersJensen-NOAA:tempo_v3.0.0_formatting

Conversation

@AndersJensen-NOAA
Copy link
Copy Markdown
Collaborator

@AndersJensen-NOAA AndersJensen-NOAA commented Dec 1, 2025

The title above should be a 1 line short summary of the pull request (i.e. what the project the PR represents is intended to do).

Enter a description of this PR. This should include why this PR was created, and what it does.

Testing and relations to other Pull Requests should be added as subsequent comments.

See the below examples for more information.
MPAS-Dev/MPAS#930
MPAS-Dev/MPAS#931

Priority Reviewers

  • Please list the developers/collaborators you'd like to prioritize for review
  • Example:

- added graupel volume to init_atmosphere registry
- formatted code
@guoqing-noaa
Copy link
Copy Markdown
Collaborator

Any updates on the timeline of this PR? Thanks!

@clark-evans
Copy link
Copy Markdown
Collaborator

Any updates on the timeline of this PR? Thanks!

It's currently being tested in dev1. The output so far looks fairly reasonable. If that holds with formal verification, I expect we'll be ready to merge next week or shortly thereafter.

@guoqing-noaa
Copy link
Copy Markdown
Collaborator

Any updates on the timeline of this PR? Thanks!

It's currently being tested in dev1. The output so far looks fairly reasonable. If that holds with formal verification, I expect we'll be ready to merge next week or shortly thereafter.

That's great! Thanks for the good news!

@AndersJensen-NOAA AndersJensen-NOAA marked this pull request as ready for review February 5, 2026 19:08
Copy link
Copy Markdown
Collaborator

@joeolson42 joeolson42 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suppose... ;-)

@AndersJensen-NOAA
Copy link
Copy Markdown
Collaborator Author

@dustinswales @clark-evans Three tests are failing. I though it was an issue with the lookup tables, so I made a few commits to try and modify, but it could be a namelist issue also with the update to tempo v3. Suggestions for easy ways to debug would be helpful.

@clark-evans
Copy link
Copy Markdown
Collaborator

@dustinswales @clark-evans Three tests are failing. I though it was an issue with the lookup tables, so I made a few commits to try and modify, but it could be a namelist issue also with the update to tempo v3. Suggestions for easy ways to debug would be helpful.

@dustinswales are we still pulling the namelists from barlage/mpas_testcase? That's what it looks like to me in the workflow. I'm guessing the feature tests are failing because Anders moved the TEMPO namelist parameters to a new namelist block that isn't represented in the testcase namelists.

If this is the case, then the tests would fail until that repo is updated - but we don't necessarily want to update that repo until after this PR is merged. Is there a hacky way of getting around this to test the updated code?

@dustinswales
Copy link
Copy Markdown
Collaborator

@clark-evans You are correct about the nml.
@AndersJensen-NOAA just stopped by and we chatted. The plan is for Anders to update his fork of the MPAS case configuration repo, and make any necessary changes for the TEMPO namelist updates.
Also, we should update the CI scripts to use Anders repo rather than updating the one owned by @barlage (We should've handed this off to someone at GSL when Mike left, so it's a good time for Anders to adopt it :))

@AndersJensen-NOAA
Copy link
Copy Markdown
Collaborator Author

@clark-evans You are correct about the nml. @AndersJensen-NOAA just stopped by and we chatted. The plan is for Anders to update his fork of the MPAS case configuration repo, and make any necessary changes for the TEMPO namelist updates. Also, we should update the CI scripts to use Anders repo rather than updating the one owned by @barlage (We should've handed this off to someone at GSL when Mike left, so it's a good time for Anders to adopt it :))

Thanks -- I may have to iterate a bit but I think I can get this working with running the base with old tables and old namelists and the feature with new tables and new namelists. It may take a few tries. If I get stuck I'll reach out again.

@AndersJensen-NOAA
Copy link
Copy Markdown
Collaborator Author

AndersJensen-NOAA commented Feb 13, 2026

@dustinswales -- I have things working. Can you take a quick peek at my changes to run_mpas.yaml and run_mpas_hrrr.yaml to make sure that things look good?

@clark-evans ready to merge once Dustin and you okays this.

@clark-evans
Copy link
Copy Markdown
Collaborator

The comparison script output from the GSL hrrrv5 tests includes the following line for all three tests:

"DIFFER : Failed to find variable ng in file "/home/runner/work/run_bl/history.2024-02-02_18.00.00.nc"."

This also appears for all subsequent forecast hours. Since it's in the run_bl directory, I'm guessing Ng is not in the baseline output but is in the feature output. Is that to be expected, @AndersJensen-NOAA?

@dustinswales
Copy link
Copy Markdown
Collaborator

@AndersJensen-NOAA Looks good to me.

I will say that sleuthing through the CI logs to see that this is answer changing is a big pain.
We could add a plotting step to the CI script that plots any differences and stores them as an artifacts.
(This we the diffs would be right in your face in the PR, and we could double-check the developers "blessing of the changes")

@dustinswales dustinswales requested review from dustinswales and removed request for dustinswales February 13, 2026 17:16
@AndersJensen-NOAA
Copy link
Copy Markdown
Collaborator Author

AndersJensen-NOAA commented Feb 13, 2026

The comparison script output from the GSL hrrrv5 tests includes the following line for all three tests:

"DIFFER : Failed to find variable ng in file "/home/runner/work/run_bl/history.2024-02-02_18.00.00.nc"."

This also appears for all subsequent forecast hours. Since it's in the run_bl directory, I'm guessing Ng is not in the baseline output but is in the feature output. Is that to be expected, @AndersJensen-NOAA?

great catch @clark-evans -- I reverted the changes to the namelist for the baseline run only, in an attempt to not change the baselines as I had inadvertently turned off the hail aware option when updating namelists.

New tests are running now

@clark-evans
Copy link
Copy Markdown
Collaborator

Final commit looks good to me; I can merge once @dustinswales gives the OK.

@clark-evans clark-evans linked an issue Feb 24, 2026 that may be closed by this pull request
@clark-evans clark-evans merged commit f506b43 into ufs-community:gsl/develop Feb 26, 2026
18 checks passed
@guoqing-noaa
Copy link
Copy Markdown
Collaborator

Hooray, thanks for the merge of this PR!

With this PR, rrfs-workflow can now use the official gsl/develop branch!

@AndersJensen-NOAA, to confirm, we will need the name list change and the three new fix files you shared with me when establishing the AR3.5km PEAR runs, right? Thanks!

@AndersJensen-NOAA
Copy link
Copy Markdown
Collaborator Author

Hooray, thanks for the merge of this PR!

With this PR, rrfs-workflow can now use the official gsl/develop branch!

@AndersJensen-NOAA, to confirm, we will need the name list change and the three new fix files you shared with me when establishing the AR3.5km PEAR runs, right? Thanks!

Yes, the changes that I shared with you are applicable here too!

jordanschnell pushed a commit to cheMPAS-Fire/MPAS-Model that referenced this pull request Apr 2, 2026
…ase (ufs-community#192)

* removed unused configuration variable
- added graupel volume to init_atmosphere registry
- formatted code
* cleaned up core_atmosphere registry for tempo
* cleaned up mpas tempo driver call and removed tempo table build from mpas
* v3.0.0 updates consistent with tempo refactor
* v3.0.0 tempo refactor with ml prediction for bl clouds
* update point to tempo v3 and clean up code to better match NCAR implementation
* Update CMakeList for tempo v3
* add compile option for tempo
* More updates to github runners for tempo v3
* change workflow to pull tempo v2 and v3 tables
* adds flag to turn on/off ability to calculate reflectivity from melting snow/graupel
* update pointer to tempo v3.0.2
* update to version 3.0.3 with more ccpp changes
* Update version number in README

---------

Co-authored-by: Clark Evans <clark.evans@noaa.gov>
jordanschnell added a commit to cheMPAS-Fire/MPAS-Model that referenced this pull request Apr 2, 2026
* v8.3.1-2.13: Update MPAS HRRR CI test for tempo v3 lookup tables (ufs-community#213)

* Update MPAS HRRR CI test for tempo v3 lookup tables
* Update version in README

* v8.3.1-2.14: TEMPO code cleanup and refactor for v3.0.0 and MPAS release (ufs-community#192)

* removed unused configuration variable
- added graupel volume to init_atmosphere registry
- formatted code
* cleaned up core_atmosphere registry for tempo
* cleaned up mpas tempo driver call and removed tempo table build from mpas
* v3.0.0 updates consistent with tempo refactor
* v3.0.0 tempo refactor with ml prediction for bl clouds
* update point to tempo v3 and clean up code to better match NCAR implementation
* Update CMakeList for tempo v3
* add compile option for tempo
* More updates to github runners for tempo v3
* change workflow to pull tempo v2 and v3 tables
* adds flag to turn on/off ability to calculate reflectivity from melting snow/graupel
* update pointer to tempo v3.0.2
* update to version 3.0.3 with more ccpp changes
* Update version number in README

---------

Co-authored-by: Clark Evans <clark.evans@noaa.gov>

* update to joes mynn

* Updating version number

* v8.3.1-2.16: Adding MYNN-SFC submodule to MPAS (ufs-community#210)

* submodularizing the MYNN surface layer scheme
* bug fix in physics/Makefile
* modified sfclayer and seaice driver for mynnsfc submodule
* removing compilation of (my) old MYNN sfclayer scheme
* added note in mpas_atmphys_vars.F that qcg is no longer needed in mynnsfc submodule
* added config options for MYNN sfc layer submodule
* bug fix for bringing in new flags for MYNN sfclayer submodule
* Final bug fixes for MPAS compilation
* Updating pointer to MYNN-SFC with a new debug Makefile for MPAS
* bug fix for adding necessary input into the MYNN-SFC submodule
* addressing cmake errors
* Final update to MYNN-SFC pointer, which includes RUC-tuned option config_mynn_sfcflux_land =1
* changing default config_mynn_sfcflux_land from 0 to 1
* a few bug fixes in MYNN-SFC and corresponding driver changes
* update pointer to MYNN-SFC, only formatting/cleanup
* Update version number
* fix typo
---------

Co-authored-by: Clark Evans <clark.evans@noaa.gov>

* v8.3.1-2.17: Restructure GFL submodule for MPAS, WRF, and CCPP (ufs-community#211)

* "Resture GFL submodule for MPAS, WRF, and CCPP"
* "update GFL for CMake"
* "turn off shallow convection for both bl_mynn and bl_mynnedmf"
* Update version number

* v8.3.1-2.18: hotfix to the build failure using `make -j8` with spack-stack  (ufs-community#221)

* core_mynnsfc and core_physics_noahmp need to depend on core_physics_init
* bump version to 8.3.1-2.18

* Update PR template

Added mandatory questions section to PR template.

* Containerized CI + Cleanup testing  (ufs-community#218)

* Update CI
* Update README.md

---------

Co-authored-by: dustinswales <dswales@ucar.edu>

* v8.3.1-2.20: Add mmm physics as submobule. (ufs-community#233)

* Initial commit
* CI trigger test
* Address reviewer comment
* Update README.md

* v8.3.1-2.21: Add two new namelist options to control the hydrometeors to be included in the LBC files. (ufs-community#234)

* Add two new namelist options and packages to control the hydrometeors to be included in the LBC files. This is because the resource model has different hydrometeors in their products. The two options added are for the LBC from GFS or GEFS.
* Updating tabs to spaces for selected registry elements
* In core_init_atmosphere/Registry.xml, change bdy option name from 'tempoall' to 'rrfs' for consistency with 'gfs'
* Update version number

---------

Co-authored-by: Clark Evans <clark.evans@noaa.gov>

* v8.3.1-2.22: restore extra spaces in mpas_stream_manager.F to match NCAR's version (ufs-community#238)

* restore extra spaces in mpas_stream_manager.F to match NCAR's version
* Update version number

---------

Co-authored-by: Clark Evans <clark.evans@noaa.gov>

* final updates to match

---------

Co-authored-by: AndersJensen-NOAA <132939212+AndersJensen-NOAA@users.noreply.github.com>
Co-authored-by: Clark Evans <clark.evans@noaa.gov>
Co-authored-by: Joseph Olson <joeolson42@users.noreply.github.com>
Co-authored-by: haiqinli <38666296+haiqinli@users.noreply.github.com>
Co-authored-by: Guoqing Ge <guoqing.ge@noaa.gov>
Co-authored-by: Dustin Swales <dustin.swales@noaa.gov>
Co-authored-by: dustinswales <dswales@ucar.edu>
Co-authored-by: Ming Hu <Ming.Hu@noaa.gov>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Correct range of volg vules? scalars are inconsistent between init_atmosphere and atmosphere

5 participants