Cam sima dycore update #344
Conversation
…usion, add se_molecular_diff namelist
Merge in check_energy & cam_thermo_water_update changes
There was a problem hiding this comment.
Thanks @PeterHjortLauritzen! Some early comments.
I think there are a handful of instances in the dycore that have code walled off using #ifdef 0 and a comment, for much of the code that depends on tracers/chemistry/constituents and history, which were previously unsupported. Not sure if we should begin to implement these now or continue to wall these off (perhaps in a constituent manner to what is there now, i.e., change all to #ifdef 0) so they can be dealt with together at a later time.
| dry surface pressure scaling. If less than or equal to 0.0, | ||
| do not perform scaling. If greater than 0.0, perform scaling to scale_dry_air_mass | ||
| value (in Pa) as the average dry surface pressure target. | ||
| Default: set by build-namelist. |
There was a problem hiding this comment.
Build-namelist is no longer present after migrating to CAM-SIMA so this could be removed.
| <!-- Scale Dry Air Mass: for cases with topography --> | ||
| <value phys="cam4" > 98288.0D0 </value> | ||
| <value phys="cam5" > 98288.0D0 </value> | ||
| <value phys="cam6" > 98288.0D0 </value> |
There was a problem hiding this comment.
I believe CAM6 won't be supported in SIMA - @nusbaume could you please confirm? I remember I was asked in previous reviews to remove the cam6 options
There was a problem hiding this comment.
It will. The CSSI proposal will support CAM6.
| <value phys="cam4" > 98288.0D0 </value> | ||
| <value phys="cam5" > 98288.0D0 </value> | ||
| <value phys="cam6" > 98288.0D0 </value> | ||
| <value phys="cam7" > 98288.0D0 </value> |
There was a problem hiding this comment.
I believe those entries should now be phys_suite="cam7" instead of phys="cam7"
| ! Ensure N2 = 1 - (O2 + O + H) mmr is greater than 0 | ||
| ! Check for unusually large H2 values and set to lower value. | ||
| !------------------------------------------------------------ | ||
| !xxx this code is NOT in cam_development? |
There was a problem hiding this comment.
I think this was migrated to physics_cnst_limit in cam_development. I remember taking a look at this when porting the check_energy infrastructure and the code seemed the same, just that it is wrapped in a subroutine in CAM (physics_cnst_limit in physics_types).
| real (kind=r8), public :: nu = 7.0D5 ! viscosity (momentum equ) | ||
| real (kind=r8), public :: nu_div = -1 ! viscsoity (momentum equ, div component) | ||
| real (kind=r8), public :: nu_s = -1 ! default = nu T equ. viscosity | ||
| real (kind=r8), public :: nu_t = -1 ! default = nu T equ. viscosity xxx rename nu_t |
There was a problem hiding this comment.
Please confirm this comment to rename nu_t is still needed
| deallocate(ftmp) | ||
| #endif | ||
| end subroutine compute_adv_tends_xyz | ||
| #ifdef scm_code |
There was a problem hiding this comment.
Not sure if this code is still intended to be kept in SIMA, there seem to be other instances of SCAM code walled off using #ifdef SCAM in other files as well. I think at least they could use the same preprocessor variable scam instead of scm_code which seems to be unique for this file
| #ifdef constituents | ||
| use constituents, only: pcnst, cnst_name, cnst_longname | ||
| use dimensions_mod, only: fv_nphys, cnst_name_gll, cnst_longname_gll, qsize | ||
| #endif |
There was a problem hiding this comment.
Now that the CAM-SIMA history is implemented I think this subroutine could be modified to use the constituent properties pointer, not sure if it will fully work but please let me know if you like me to give it a try!
|
Note -- maybe it could be addressed in this PR: To support CAM7 moving mountain gravity waves the |
3 participants
Tag name (required for release branches):
Originator(s):
Description (include the issue title, and the keyword ['closes', 'fixes', 'resolves'] followed by the issue number):
Describe any changes made to build system:
Describe any changes made to the namelist:
List any changes to the defaults for the input datasets (e.g. boundary datasets):
List all files eliminated and why:
List all files added and what they do:
List all existing files that have been modified, and describe the changes:
(Helpful git command:
git diff --name-status development...<your_branch_name>)If there are new failures (compared to the
test/existing-test-failures.txtfile),have them OK'd by the gatekeeper, note them here, and add them to the file.
If there are baseline differences, include the test and the reason for the
diff. What is the nature of the change? Roundoff?
derecho/intel/aux_sima:
derecho/gnu/aux_sima:
If this changes climate describe any run(s) done to evaluate the new
climate in enough detail that it(they) could be reproduced:
CAM-SIMA date used for the baseline comparison tests if different than latest: