Skip to content

Tempo version 3#3078

Open
AndersJensen-NOAA wants to merge 38 commits into
ufs-community:developfrom
AndersJensen-NOAA:tempo_v3
Open

Tempo version 3#3078
AndersJensen-NOAA wants to merge 38 commits into
ufs-community:developfrom
AndersJensen-NOAA:tempo_v3

Conversation

@AndersJensen-NOAA

@AndersJensen-NOAA AndersJensen-NOAA commented Feb 4, 2026

Copy link
Copy Markdown
Contributor

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.
  • 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:

Updates to tempo microphysics version 3: Addresses issue: #3109

Commit Message:

* UFSWM - 
  * UFSATM - 
    * ccpp-physics - 

Priority:

  • Critical Bugfix: Reason
  • High: Reason
  • Normal

Git Tracking

UFSWM:

Closes #3109

Sub component Pull Requests:

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: tempo has its own documentation

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. New lookup tables are needed

Library Changes/Upgrades:

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

Testing Log:

  • RDHPCS
    • Orion
    • Hercules
    • GaeaC6
    • Derecho
    • Ursa: /scratch4/BMC/wrfruc/jensen/ufs_tempo_dev_test/tests/
  • WCOSS2
    • Dogwood/Cactus
    • Acorn
  • CI
  • opnReqTest (complete task if unnecessary)

@github-project-automation github-project-automation Bot moved this to Evaluating in PRs to Process Feb 4, 2026
@AndersJensen-NOAA AndersJensen-NOAA marked this pull request as draft February 4, 2026 18:44
@AndersJensen-NOAA AndersJensen-NOAA marked this pull request as ready for review February 19, 2026 22:13
@gspetro-NOAA

Copy link
Copy Markdown
Collaborator

@AndersJensen-NOAA Could you please fill out the PR template if this PR is ready? We can't move the PR forward until we have the info requested in the template. If the PR is not ready, it would be best to convert it to draft form until it is ready.

@gspetro-NOAA gspetro-NOAA moved this from Evaluating to Not Ready in PRs to Process Feb 25, 2026
@AndersJensen-NOAA

Copy link
Copy Markdown
Contributor Author

@grantfirl I'm happy to pull down code and fire off tests tonight.

@AndersJensen-NOAA

Copy link
Copy Markdown
Contributor Author

@grantfirl new tests are here: /scratch4/BMC/wrfruc/jensen/ufs_tempo310/tests

@AndersJensen-NOAA

Copy link
Copy Markdown
Contributor Author

@grantfirl I also made a new test regional_wofs_tempo as part of this PR (replacing the p8 hail test), but I don't think that it ran.

@grantfirl

Copy link
Copy Markdown
Collaborator

scratch4/BMC/wrfruc/jensen/ufs_tempo310/tests

@AndersJensen-NOAA Thanks for running those. I'll push the RT log. I think that regional_wofs_tempo test didn't run because it wasn't added to rt.conf. I'll add it and try to run just that test on Ursa and upload the log in the comments to prove that it runs.

@gspetro-NOAA gspetro-NOAA moved this from Pre-testing required to Waiting for Reviews (subcomponent) in PRs to Process Jun 16, 2026
@grantfirl

Copy link
Copy Markdown
Collaborator

@AndersJensen-NOAA The regional_wofs_intel test now runs with the changes in 82dcaec

RegressionTests_ursa.log

@grantfirl

Copy link
Copy Markdown
Collaborator

@gspetro-NOAA The control_p8_ugwpv1_tempo_aerosol_hail test was removed from Ursa due to memory issues a few PRs back. It might be able to be turned back on with the addition of memory for this test by @AndersJensen-NOAA in this PR. I'll leave that up to you all to decide.

@gspetro-NOAA

gspetro-NOAA commented Jun 16, 2026

Copy link
Copy Markdown
Collaborator

@AndersJensen-NOAA @grantfirl I have copied the input-data-20251015 directory contents to input-data-20260617. From input-data-20260617, I plan to remove:

  • FV3_input_data_TEMPO/MP_TEMPO_freezeH2O.dat
  • FV3_input_data_TEMPO/MP_TEMPO_QRacrQG.dat
  • FV3_input_data_TEMPO/MP_TEMPO_HAILAWARE_QRacrQG.dat
  • FV3_input_data_TEMPO/MP_TEMPO_QRacrQS.dat
  • FV3_fix/CCN_ACTIVATE.BIN

I need to add:

  • /scratch4/BMC/wrfruc/jensen/for_ftp/qr_acr_qs_data_tempo_v3
  • /scratch4/BMC/wrfruc/jensen/for_ftp/qr_acr_qg_data_tempo_v3
  • /scratch4/BMC/wrfruc/jensen/for_ftp/freeze_water_data_tempo_v3
    to input-data-20260617/FV3_input_data_TEMPO/.

I'll also need to add /scratch4/BMC/wrfruc/jensen/for_ftp/ccn_activate.bin to input-data-20260617/FV3_fix.

Is that correct?

@grantfirl

Copy link
Copy Markdown
Collaborator

@gspetro-NOAA I added the testing logs from the runs that completed last Friday, although there were some more minor changes in the TEMPO submodule since then. I don't anticipate any of these changes causing any trouble, but I can't prove that without rerunning the pre-tests. Please let me know if you'd like them to be re-run before testing on other platforms.

Also, it looks like that there are more compiler warnings. I'll see if I can track those down.

The additional compiler warnings disappeared after updating the code to the latest develop branches. I'm not sure what the extra remarks are about.

@grantfirl

Copy link
Copy Markdown
Collaborator

@AndersJensen-NOAA @grantfirl I have copied the input-data-20251015 directory contents to input-data-20260617. From input-data-20260617, I plan to remove:

  • FV3_input_data_TEMPO/MP_TEMPO_freezeH2O.dat
  • FV3_input_data_TEMPO/MP_TEMPO_QRacrQG.dat
  • FV3_input_data_TEMPO/MP_TEMPO_HAILAWARE_QRacrQG.dat
  • FV3_input_data_TEMPO/MP_TEMPO_QRacrQS.dat
  • FV3_fix/CCN_ACTIVATE.BIN

I need to add:

  • /scratch4/BMC/wrfruc/jensen/for_ftp/qr_acr_qs_data_tempo_v3
  • /scratch4/BMC/wrfruc/jensen/for_ftp/qr_acr_qg_data_tempo_v3
  • /scratch4/BMC/wrfruc/jensen/for_ftp/freeze_water_data_tempo_v3
    to input-data-20260617/FV3_input_data_TEMPO/.

I'll also need to add /scratch4/BMC/wrfruc/jensen/for_ftp/ccn_activate.bin to input-data-20260617/FV3_fix.

Is that correct?

In addition to updating the *_run.IN files afterward to reflect the newly-staged files, I think that this is correct, although I'll let @AndersJensen-NOAA confirm.

@gspetro-NOAA

Copy link
Copy Markdown
Collaborator

@gspetro-NOAA The control_p8_ugwpv1_tempo_aerosol_hail test was removed from Ursa due to memory issues a few PRs back. It might be able to be turned back on with the addition of memory for this test by @AndersJensen-NOAA in this PR. I'll leave that up to you all to decide.

I think it would be good to turn it back on and test whether it works.

Comment thread tests/default_vars.sh Outdated

export TPN=192

export MEM_PER_NODE="368640M"

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

where does this default MEM_PER_NODE
(used in Ursa #SBATCH --mem=@[MEM_PER_NODE])
come from?

Isn't this more than the 300G set in regional_wofs_tempo‎?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

By default, Ursa gives 1.92G per core, and there are 192 cores/node. For a default TPN=192, the default memory should be 368640M. This memory amount is a system-level setting on Ursa. Note that Ursa has 2G per core available.

The reason why the tempo_p8 tests need 300G of memory is because they use 150 tasks, and by default, this does not provide enough memory for tempo.
see this comment: ufs-community/ccpp-physics#353 (comment)

If the regional_wofs_tempo test uses TPN=192, then it doesn't need the export MEM_PER_NODE="300G" statement.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

I was kinda confused by the memory changes for Ursa too. With the addition of export MEM_PER_NODE="368640M" in default_vars.sh, this is setting the memory for every Ursa test, right? Why is this needed if this is the same as the system-level setting on Ursa? Then, the individual TEMPO tests are asking for export MEM_PER_NODE="300G", which is now less than the default. This is what is desired? Or do I have this wrong?

I added the export MEM_PER_NODE="300G" statement to regional_wofs_tempo. I thought it was necessary. Where are the number of tasks being set for the tempo_p8 tests that is different than the default?

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Thanks for the details, explanation, and sorting through the intermittent test failures

Does this fix for memory in one scheme practically change quite a few unrelated tests that also have TPN/=192?

If so, one option would be to comment this MEM_PER_NODE setting by default, similar to EXCLUSIVE_NODES_OPT or HIDE_UGWPV1 ideas

It would be more work to compute these based on system settings near compute_petbounds_and_tasks

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Yes other tests with TPN/=192 would be changed. I don't know how to comment, or hide, a variable in the default settings though. But that would be the best solution.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

One way is like AndersJensen-NOAA#3

Comment thread tests/fv3_conf/control_run.IN Outdated
Comment thread tests/fv3_conf/control_run.IN Outdated
Comment thread tests/fv3_conf/regional_run.IN Outdated
Comment thread tests/fv3_conf/regional_run.IN Outdated
@AndersJensen-NOAA

Copy link
Copy Markdown
Contributor Author

@AndersJensen-NOAA @grantfirl I have copied the input-data-20251015 directory contents to input-data-20260617. From input-data-20260617, I plan to remove:

  • FV3_input_data_TEMPO/MP_TEMPO_freezeH2O.dat
  • FV3_input_data_TEMPO/MP_TEMPO_QRacrQG.dat
  • FV3_input_data_TEMPO/MP_TEMPO_HAILAWARE_QRacrQG.dat
  • FV3_input_data_TEMPO/MP_TEMPO_QRacrQS.dat
  • FV3_fix/CCN_ACTIVATE.BIN

I need to add:

  • /scratch4/BMC/wrfruc/jensen/for_ftp/qr_acr_qs_data_tempo_v3
  • /scratch4/BMC/wrfruc/jensen/for_ftp/qr_acr_qg_data_tempo_v3
  • /scratch4/BMC/wrfruc/jensen/for_ftp/freeze_water_data_tempo_v3
    to input-data-20260617/FV3_input_data_TEMPO/.

I'll also need to add /scratch4/BMC/wrfruc/jensen/for_ftp/ccn_activate.bin to input-data-20260617/FV3_fix.

Is that correct?

Yes, this is correct. Delete the old tables, and add the new ones. The ccn_activate.bin table should be the same one that Thompson uses. The other tables are different.

@gspetro-NOAA

Copy link
Copy Markdown
Collaborator

@AndersJensen-NOAA Could you accept (or reject, if problematic) my proposed changes so that I can test the data staging for the PR?

AndersJensen-NOAA and others added 4 commits June 17, 2026 12:27
Co-authored-by: Gillian Petro <96886803+gspetro-NOAA@users.noreply.github.com>
Co-authored-by: Gillian Petro <96886803+gspetro-NOAA@users.noreply.github.com>
Co-authored-by: Gillian Petro <96886803+gspetro-NOAA@users.noreply.github.com>
Co-authored-by: Gillian Petro <96886803+gspetro-NOAA@users.noreply.github.com>
@AndersJensen-NOAA

Copy link
Copy Markdown
Contributor Author

@AndersJensen-NOAA Could you accept (or reject, if problematic) my proposed changes so that I can test the data staging for the PR?

@gspetro-NOAA You should be good to test now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Baseline Updates Current baselines will be updated. CCPP There are changes to a CCPP repository. Changes Existing Input Data Existing input data will be changed. A new input-data-YYYYMMDD directory must be created. UFSATM There are changes to the UFSATM repository.

Projects

Status: Waiting for Reviews (subcomponent)

Development

Successfully merging this pull request may close these issues.

Tempo Microphysics version 3

4 participants