-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FV3 nesting incompatible with stochastic physics due to tile size equality assumption #77
Comments
It seems to be that the CA should only run on the global domain, and the nest should get the same values as the global domain. Lisa is on vacation right now, but I will talk to her to get her thoughts. |
What do you mean by this?
|
I had a typo. I am saying that I don't think a separate CA should not be running inside the nest. But @lisa-bengtsson would know better. |
@SamuelTrahanNOAA it would require some development. 7 tiles is currently not supported, neither is running tiles with different size, with the CA. Could you turn it off at a high level if do_ca = .true. and a nested configuration is running? I would need some time to develop this capability. |
At present, in the nested global workflows I'm using (global-workflow and HAFS), turning on nesting automatically turns off CA. |
When using FV3 nesting, the tiles can be different sizes. It appears the cellular automata code makes the assumption that all tiles have the same size. That is rarely true for nested configurations. The configuration I'm testing is a global model with a static nest. That's seven tiles: six global tiles of equal size, and a seventh tile that has far more gridpoints.
Presently, I don't have a test case you can easily run to reproduce this problem because the model will fail for a great many other reasons first (such as NOAA-EMC/fv3atm#797 and NOAA-GFDL/GFDL_atmos_cubed_sphere#328). I'm hoping to have a test case soon for debugging with a branch that has fixes and workarounds for all other problems.
This is the failure. It happens only on the nest:
Line 232 of cellular_automata_sgs.F90 is here:
The stochastic_physics_wrapper.F90 line 400 is calling stochastic_physics_wrapper.F90 and sending the information for the current tile
Atm(mygrid)
The text was updated successfully, but these errors were encountered: