Skip to content

dev/emc: Release FV3 solver updates#262

Closed
laurenchilutti wants to merge 3 commits into
NOAA-GFDL:dev/emcfrom
laurenchilutti:solveremc
Closed

dev/emc: Release FV3 solver updates#262
laurenchilutti wants to merge 3 commits into
NOAA-GFDL:dev/emcfrom
laurenchilutti:solveremc

Conversation

@laurenchilutti
Copy link
Copy Markdown
Member

Description

Cherry-picks changes form PR #261 to dev/emc
This includes updates on behalf of Lucas Harris including:
Revision to semi-implicit solver to linearize vertical sound wave propagation about the hydrostatic state. This has been extensively tested by GFDL and EMC in SHiELD, GFS, and RRFS.

Fixes # (issue)

How Has This Been Tested?

This has been tested with ShiELD in the main branch.

Checklist:

Please check all whether they apply or not

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • Any dependent changes have been merged and published in downstream modules

… a revision to the semi-implicit solver to linearize vertical sound wave propagation about the hydrostatic state.
@XiaqiongZhou-NOAA
Copy link
Copy Markdown
Contributor

"tau_w" is already used in explicit Rayleigh damping in dev/emc branch. Can the new-added "tau_w" change to another name? Otherwise, there are conflicts when compiling.

@lharris4
Copy link
Copy Markdown
Contributor

lharris4 commented Apr 19, 2023 via email

@XiaqiongZhou-NOAA
Copy link
Copy Markdown
Contributor

Lucas:
In the current dev/emc, if tau_w=0, w is damped as tau. The purpose of tau_w is to have different damping time scale for horizontal and vertical winds. I am not sure who is currently using this option. This option was added based on Henry's test for WAM at that time.
Kate

@lharris4
Copy link
Copy Markdown
Contributor

lharris4 commented Apr 19, 2023 via email

@XiaqiongZhou-NOAA
Copy link
Copy Markdown
Contributor

Lucas:
That sounds a good solution.

Lauren:
Could you revise the code as Lucas suggested?
Thanks.
Kate

@laurenchilutti
Copy link
Copy Markdown
Member Author

I have just pushed the changes, let me know if that is acceptable

@lharris4
Copy link
Copy Markdown
Contributor

Hi, Lauren. These changes look good to me. Thanks for taking care of this.

Lucas

Comment thread model/nh_core.F90 Outdated
pe2, dm, &
pm2, pem, w2, dz2, pt(is:ie,j,1:km), ws(is,j), &
a_imp, p_fac, scale_m)
a_imp, p_fac, scale_m, tau_w)
Copy link
Copy Markdown
Contributor

@XiaqiongZhou-NOAA XiaqiongZhou-NOAA Apr 19, 2023

Choose a reason for hiding this comment

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

tau_w added in nh_core.F90, nh_utils.F90 should be fast_tau_w_sec

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Hi, Kate. I believe that inside the nh_core/nh_utils modules the name is tau_w and the namelist flag fast_tau_w_sec is used in the call to the NH utils. So this implementation is correct, but potentially confusing. However for consistency's sake and to eliminate confusion we could replace this with fast_tau_w_sec.

Thanks,
Lucas

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

I will update this also to use fast_tau_w_sec as well. You are right that this could be confusing to follow.

…lculation to be fully double precsision. Address spacing change.
@laurenchilutti
Copy link
Copy Markdown
Member Author

Comments from PR #261 and this PR have all now been addressed. Changes are identical in both PRs.

@lharris4
Copy link
Copy Markdown
Contributor

lharris4 commented Apr 20, 2023 via email

@laurenchilutti
Copy link
Copy Markdown
Member Author

replacing this PR with #266

@laurenchilutti laurenchilutti deleted the solveremc branch December 23, 2024 14:32
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