Tempo version 3#3078
Conversation
|
@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. |
|
@grantfirl I'm happy to pull down code and fire off tests tonight. |
|
@grantfirl new tests are here: /scratch4/BMC/wrfruc/jensen/ufs_tempo310/tests |
|
@grantfirl I also made a new test |
@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. |
|
@AndersJensen-NOAA The regional_wofs_intel test now runs with the changes in 82dcaec |
|
@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. |
|
@AndersJensen-NOAA @grantfirl I have copied the input-data-20251015 directory contents to input-data-20260617. From
I need to add:
I'll also need to add Is that correct? |
The additional compiler warnings disappeared after updating the code to the latest develop branches. I'm not sure what the extra remarks are about. |
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. |
I think it would be good to turn it back on and test whether it works. |
|
|
||
| export TPN=192 | ||
|
|
||
| export MEM_PER_NODE="368640M" |
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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
There was a problem hiding this comment.
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.
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. |
|
@AndersJensen-NOAA Could you accept (or reject, if problematic) my proposed changes so that I can test the data staging for the PR? |
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>
@gspetro-NOAA You should be good to test now. |
Replace MEM_PER_NODE with MEM_PER_NODE_OPT
Commit Queue Requirements:
test_changes.listindicates which tests, if any, are changed by this PR. Committest_changes.list, even if it is empty.Description:
Updates to tempo microphysics version 3: Addresses issue: #3109
Commit Message:
Priority:
Git Tracking
UFSWM:
Closes #3109
Sub component Pull Requests:
UFSWM Blocking Dependencies:
Documentation:
Changes
Regression Test Changes (Please commit test_changes.list):
Input data Changes:
Library Changes/Upgrades:
Testing Log: