-
Notifications
You must be signed in to change notification settings - Fork 337
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'init_atmosphere/optional_noahmp_static' into develop (PR …
…#1239) This merge introduces changes that make Noah-MP static fields optional in the init_atmosphere core. Previously, the soilcomp and soilcl{1,2,3,4} fields needed only by the Noah-MP scheme were required in all static files read by the init_atmosphere core. In cases where the Noah-MP scheme will not be used when running the atmosphere core, it would be desirable to not require these Noah-MP-only fields. Now, a new namelist option and package in the init_atmosphere core permit the generation and the use of static files that do not contain soilcomp and soilcl{1,2,3,4}. 1. The new config_noahmp_static namelist option in the &data_sources namelist group determines whether the Noah-MP-only static fields will be allocated, read, computed, and written in the init_atmosphere core. This namelist option defaults to true, yielding the default behavior of the init_atmosphere_model program prior to this commit. Also, this namelist option is not present in the default namelist.init_atmosphere file generated at compile time. 2. The new noahmp package, which is active if and only if config_noahmp_static is true, controls the allocation, reading, and writing of the Noah-MP-only static fields. 3. In the init_atm_static routine, which is called when config_static_interp is true, the soilcomp and soilcl{1,2,3,4} fields are computed only if config_noahmp_static is true. * init_atmosphere/optional_noahmp_static: Omit 'config_noahmp_static' from the default namelist.init_atmosphere file Make Noah-MP-only static fields optional in init_atmosphere core
- Loading branch information
Showing
3 changed files
with
89 additions
and
45 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters