GEOS-Chem no-diff-to-benchmark: Difference between revisions
Jump to navigation
Jump to search
Line 13: | Line 13: | ||
|-valign="top" | |-valign="top" | ||
|Use hard-coded dates for meteorological fields and boundary conditions | |Use hard-coded dates for meteorological fields and boundary conditions | ||
*'''''This update fixes a bug that caused met fields and nested-grid boundary conditions to be read more frequently than necessary. This eliminates a computational bottleneck that was inadvertently introduced in 14.4.0.''''' | |||
|Nicholas Balasus (Harvard) | |Nicholas Balasus (Harvard) | ||
|Bug fix | |Bug fix | ||
| | | | ||
*[https://github.com/geoschem/geos-chem/pull/2347 geos-chem PR #2347] | *[https://github.com/geoschem/geos-chem/pull/2347 geos-chem PR #2347] | ||
|-valign="top" | |-valign="top" |
Revision as of 20:38, 25 June 2024
GEOS-Chem Versions Page | GEOS-Chem model development priorities
This page includes information about the GEOS-Chem "no-diff-to-benchmark" development stream, which contains updates and fixes that will not affect the fullchem benchmark simulations. These updates are mergeable at any time, either into the next Y version or into a standalone Z version.
Updates that will not affect fullchem benchmark simulations
Feature | Contributor(s) | Model scope | Notes and references |
---|---|---|---|
Use hard-coded dates for meteorological fields and boundary conditions
|
Nicholas Balasus (Harvard) | Bug fix |
|
Initialization fix to avoid run-time error in UCX in CESM | Lizzie Lundgren (Harvard) | CESM | |
Correct alphabetical order of complex SOA species in geoschem_config.yml | Haipeng Lin (Harvard) | CESM | |
Changes for GEOS-Chem v14.4 within CESM compatibility | Haipeng Lin (Harvard) | CESM | |
Remove BudgetWetDep* entries from HISTORY.rc files for simulations where wetdep is turned off | Bob Yantosca (Harvard) | Diagnostics | |
Fix filename for CMIP6 aircraft emissions in HEMCO_Config.rc.template #2317 | Bob Yantosca (Harvard) | Emissions | |
Fix formatting issue in `stale.yml` that was causing the "Mark Stale Issues" GitHub Action to fail | Bob Yantosca (Harvard) | GitHub |