Skip to content
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

New spatially-variable horizontal upwind capability #122

Draft
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

cbegeman
Copy link
Collaborator

@cbegeman cbegeman commented Feb 7, 2025

Here we add a new capability to transition between centered and upwinded horizontal thickness advection as a function of column thickness.

Formerly, either thickness advection was centered or upwinded everywhere. With this PR, when config_use_spatially_variable_upwinding is .true., advection is fully upwinded when the column thickness is less than config_spatially_variable_upwind_hmin and fully centered when column thickness is greater than config_spatially_variable_upwind_hmax. Between these values, there is a linear transition layerThickEdgeFlux

singhbalwinder and others added 5 commits January 24, 2025 11:26
…NBFB-bug' (PR E3SM-Project#6942)

The MAM4xx microphysics standalone test shows NBFB behavior for
two consecutive runs on GPUs. This PR fixes that, and all the fixes are
in the MAM4xx submodule.

This PR also fixes an issue related to the LINOZ file read in the microphysics
interface. The time dimension in the LINOZ file is not unlimited. Adding
a function call to pretend_dim_is_unlimited fixes this issue.

[non-BFB] only for EAMxx
@cbegeman
Copy link
Collaborator Author

cbegeman commented Feb 7, 2025

Testing

Parabolic bowl test has been run and found to have similar convergence and error.

Drying slope testing in progress; fixing bug in Compass.

Global ocean standalone testing planned.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants