You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In a global simulation with a static nest, the nest thinks it is on tile 1. Some suites read per-tile static data. The nest data must come from tile 7, but the nest tries to read tile 1 instead. It happens because CCPP receives tile_in_mosaic instead of global_tile from the atmos_cubed_sphere.
To fix this, we'll need to get the global_tile from the dynamical core. This issue documents that:
Description
In a global simulation with a static nest, the nest thinks it is on tile 1. Some suites read per-tile static data. The nest data must come from tile 7, but the nest tries to read tile 1 instead. It happens because CCPP receives tile_in_mosaic instead of global_tile from the atmos_cubed_sphere.
To fix this, we'll need to get the global_tile from the dynamical core. This issue documents that:
To Reproduce:
What compilers/machines are you seeing this with?
N/A. Machine and compiler don't affect it.
Give explicit steps to reproduce the behavior.
Additional context
I have a fix for this already, which I'll PR soon. It includes a fix for another bug (or two) which I must fix to run the test case.
Testing:
Have you tested the code changes?
Yes. I have a test case of the GFS with a static nest using current GFS physics. It has per-tile static data for all seven tiles.
On what platforms?
Hera Intel Centos.
Have you run regression test in ufs-weather-model or ufs-s2s-model with code changes?
Not yet.
Will the baseline results change?
Will know that after I run the regression tests.
The text was updated successfully, but these errors were encountered: