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

check eta levels in ideal case #955

Merged
merged 3 commits into from
Jul 23, 2019
Merged

Conversation

dudhia
Copy link
Collaborator

@dudhia dudhia commented Jul 15, 2019

TYPE: enhancement

KEYWORDS: ideal, eta

SOURCE: internal

DESCRIPTION OF CHANGES:
CPreviously, no check existed to detect invalid eta levels that a user specified in the namelist.input
file for an idealized case. A couple loops of code were copied from the file
dyn_em/module_initialize-real.F, which is used in the real program.

  1. Check that first and last level are 1.0 and 0.0, respectively.
  2. Check that the eta levels are strictly monotonically decreasing (from surface to model lid).

LIST OF MODIFIED FILES:
M dyn_em/module_initialize_ideal.F

TESTS CONDUCTED:

  • Code stops with incorrect eta-level settings
  • Code still runs with correct eta-level settings

RELEASE NOTE:
If a user chooses to explicitly list the eta levels for an idealized case, a check has been added to verify that valid eta levels are supplied for idealized cases in the namelist.input file.

@@ -631,6 +631,19 @@ SUBROUTINE init_domain_rk ( grid &
DO k=1, kde
grid%znw(k) = model_config_rec%eta_levels(k)
ENDDO
!Check the value of the first and last eta level for our domain,
Copy link
Contributor

Choose a reason for hiding this comment

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

@dudhia
Jimy,
Would you indent this so that it lines up with the rest of the code.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

done

Copy link
Contributor

Choose a reason for hiding this comment

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

I am OK with this PR now.

dudhia and others added 2 commits July 23, 2019 14:19
Just for conventional look to comments in the module_initialize_ideal.F file.
Copy link
Contributor

@davegill davegill left a comment

Choose a reason for hiding this comment

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

Approved

@dudhia dudhia merged commit eeb10bb into wrf-model:release-v4.1.3 Jul 23, 2019
davegill pushed a commit that referenced this pull request Jan 25, 2022
Modify description for GWD input fields

TYPE: text only

KEYWORDS: field description, registry, gwdo

SOURCE: internal

DESCRIPTION OF CHANGES:
Problem:
Descriptions for GWDO input fields are not clear, and some is even wrong in the registry.

Solution:
This PR modifies the descriptions for all 10 GWDO input variables: VAR,CON,OA[1-4],OL[1-4], and made them consistent with MPAS PR[#955](MPAS-Dev/MPAS-Model#955).

LIST OF MODIFIED FILES: 
M   Registry/Registry.EM_COMMON

TESTS CONDUCTED: 
1. Descriptions changed.
2. Are the Jenkins tests all passing?

RELEASE NOTE: Description for the 10 orographic gravity wave drag variables (gwd_opt=1 only) are updated.
vlakshmanan-scala pushed a commit to scala-computing/WRF that referenced this pull request Apr 4, 2024
Modify description for GWD input fields

TYPE: text only

KEYWORDS: field description, registry, gwdo

SOURCE: internal

DESCRIPTION OF CHANGES:
Problem:
Descriptions for GWDO input fields are not clear, and some is even wrong in the registry.

Solution:
This PR modifies the descriptions for all 10 GWDO input variables: VAR,CON,OA[1-4],OL[1-4], and made them consistent with MPAS PR[wrf-model#955](MPAS-Dev/MPAS-Model#955).

LIST OF MODIFIED FILES: 
M   Registry/Registry.EM_COMMON

TESTS CONDUCTED: 
1. Descriptions changed.
2. Are the Jenkins tests all passing?

RELEASE NOTE: Description for the 10 orographic gravity wave drag variables (gwd_opt=1 only) are updated.
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.

2 participants