You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
cam_cesm2_1_rel_05-Nor_v1.0.6: oslo-aero bugfixes and new compsets and testing
Summary: main oslo-aero bugfixes and compset/testing updates for noresm2.1 release
Contributors: @mvertens, @gold2718, @DirkOlivie, @oyvindseland
Reviewers: @gold2718
Purpose of changes:
- #24; clcoagTend output looks bizarre
- #109; Bug in HetFrz code
- #114; New tests to add for noresm2.1. release
Github PR URL: #116
Changes made to build system: Put in new noresm flag that is triggered by compset
Changes made to the namelist: None
Changes to the defaults for the boundary datasets: None
Substantial timing or memory changes: None
The main features in this PR are:
- bug fixes in the following two routines that now permit bfb answers with different pes
- src/chemistry/oslo_aero/hetfrz_classnuc_oslo.F90
- src/chemistry/oslo_aero/koagsub.F90
- updates to config_component.xml and config_compsets.xml to simplify the definition of compsets and remove deprecated ones
- cleanup of config_compsets.xml so that domain files are now set in cime config_grids.xml rather than in cam's config_compsets.xml
NOTE: this PR will also require an accompanying PR in CIME.
Testing:
ERP_D_Ln9.f19_f19_mtn14.QPC6.betzy_intel.cam-outfrq9s
ERP_Ln9.f19_f19_mtn14.NF1850norbc.betzy_intel.cam-outfrq9s
What happened?
Changing the number of tasks changed answers in routine testing (e.g., ERP tests). This is usually an indication of a coding bug.
What are the steps to reproduce the bug?
Run any NorESM case which uses Oslo Aero.
What CAM-Nor tag were you using?
cam_cesm2_1_rel_05-Nor_v1.0.5
What machine were you running CAM (or NorESM) on?
Betzy
What compiler were you using?
Intel
Path to a case directory, if applicable
No response
Will you be addressing this bug yourself?
Yes
Extra info
There is an incorrect array reference in a call to
calculateNumberConcentration
should be
The text was updated successfully, but these errors were encountered: