-
Notifications
You must be signed in to change notification settings - Fork 49
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
Ccpp release 3 work #100
Ccpp release 3 work #100
Conversation
…n oz_phys or oz_phys_2015; add ozone and h2o data files to repo
… call now expects the name of a suite (rather than a path/filename), modified case_configurations namelists to contains names of suites in the physics_suite variable; modified the string passed into ccpp_init() in gmtb_scm.F90; added code to link SDFs from the directory where they are stored to the run directory
…uire that NETCDF environment variable is set (and not using custom CMake find); add SIONLIB to CMakeLists; change me and master to 0 (from 1) to work with SIONLIB stuff in Thompson init
…riables to GFS_typedefs for cellular automata, changes to Init_parm, and lheatstrg
…d SCM host metadata to work with latest ccpp-physics
… couple of compilation errors in GFS_typedefs.F90; fix type in gmtb_scm_physical_constants.f90
…ove 'hrrr' from GSD suite; uncomment Tiedtke scheme from prebuild
…s; rename/modify input namelists to reflect values in FV3 and use new suite names; rename and modify case configuration files to use new namelists and suite names; edit 'physics_test' plot configuration file; add MYNN section to GFS_typedefs.F90/control_initialize; add section to gmtb_scm_type_defs.f90/physics_associated for setting fractional landmask fractions
…named case configuration files for arm_sgp_summer_1997_A as a test of prescribed surface suites; added plot_config file to plot
… experiment_config since it contains both information for setting up a case and information for specifiying physics; associated minor code changes to handle path changes
…appen in a separate PR
Associated PR: |
Notes on ozone/h2o forcing work:
Note: Since the ozone/h2o production/loss data now works like FV3 (passed via internal module variables), this can only work with multiple independent SCM columns (potentially using different physics) if all independent columns are using the same ozone scheme (and the same ozone production/loss data) |
Notes on working with GSD suite:
|
The fractional landmask changes from FV3 were integrated into the SCM code. These changes will be reverted in an upcoming PR. This will affect many SDFs, scm/src/GFS_typedefs.F90, scm/src/gmtb_scm_type_defs.f90 (both CCPP metadata and a section in physics%associate that set the fractional landmask fractions). UPDATE on 5/29/19: these changes will not be reverted anymore. |
…tb-scm into grant_ccpp_release_3_work_dom_mods
…ts; edited ccpp_prebuild_config.py and CCPP metadata to correctly pass in needed variables to Thompson MP to turn ltaerosol on without crashing
Python model run script to simplify Fortran code
…iguration; the run script must be run with a case name; if a suite is specified, it is used, otherwise, a default SDF is chosen; suites run with a default namelist unless specified; the output_dir is constructed automatically unless specified in the case configuration file
…sed in GFS_typedefs.F90 and module_gfdl_cloud_microphys.F90); fixes writing of 'fort.2' to run dir
9018bde
to
8adb1a7
Compare
…f, det_mf since SCM is outputting thise
@@ -11,8 +11,8 @@ | |||
import sys |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this file will need to be updated to work with the new run script if we want to release this functionality.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will this be a follow-up PR?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, although timing (before/after release) is TBD. A followup PR that will be useful for restoring this functionality in a cleaner way (using your run script) is forthcoming.
@@ -1,15 +1,17 @@ | |||
&gfs_physics_nml | |||
fhzero = 6. | |||
h2o_phys = .true. | |||
ldiag3d = .false. | |||
fhcyc = 24. | |||
ldiag3d = .true. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not exactly sure why this is needed, but either way it's not a big deal (unallocated variables otherwise?)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ya, the SCM output expects that tendencies are allocated, and they are only allocated in GFS_typedefs if ldiag3d is true.
lradar = .false. | ||
ltaerosol = .true. | ||
lradar = .true. | ||
ttendlim = -999. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The best value we have at GSD at the moment is between 0.005 and 0.008. The FV3 regression tests are using 0.005 since the last PR was merged (https://github.com/NCAR/NEMSfv3gfs/pull/166). Not sure what we should do, keep it as is because it's apparently working without the limiter turned on (have you tried multiple test cases with the GSD suite)? Physically more correct is -999. because it doesn't modify the answer coming out of the microphysics.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that it should probably be consistent with whatever is used in FV3 going forward, although it might be worth a special note in the namelist saying that it can be turned off with -999. I did run all cases with it off, and it didn't crash, although I didn't look carefully at the output either. I'll change it in a followup PR to be consistent with FV3 and other namelist changes if they're coming down the pike.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work, only a few minor comments that shouldn't prevent this PR from going in. See also NCAR/ccpp-physics#247 (review).
Ccpp release 3 work
This PR constitutes initial preparation for the third CCPP release. The major work was to:
Other notes:
New method for running:
In the run directory, execute:
./run_gmtb_scm.py -c CASE_NAME [-s suite_name] [-n physics_namelist_path] [-g flag to invoke through gdb]