Revision 3657e4066889b03de1ae808db02c049a13ccca7d authored by Alan V Di Vittorio on 08 December 2023, 23:14:38 UTC, committed by Alan V Di Vittorio on 08 December 2023, 23:14:38 UTC
The model successfully runs to completion for ZLND with functional CO2 downscaling. The linearly downscaled CO2 data have been verified within the GCAM repo code, but not yet in the fortran ehc code (giac repo). Convergence downscaling has not been verified. Restarts work properly. The gcam namelist has been updated to add several options for convergence downscaling and the gcam co2 passing namelist item has been corrected in name. A shell script has been added to gcam/tools that generates the new input base co2 gridded files. The fortran floating point exception checks are still off because the model still fails due to untrapped GCAM nans if these are on (which usually is only when DEBUG=TRUE). This allows for DEBUG to be set to TRUE and for the model to run. The configuration for the boost library for the ehc/gcam now points to the files in the gcam repo for portability. The xerces library configuration has been removed as it is no longer needed by GCAM. The three repo branches (e3sm, giac, gcam) at this commit work together (at least for ZLND), and thse branches are set in the .gitmodules files.
1 parent 2cf7280
CONTRIBUTING.md
## How to contribute to E3SM
#### **Did you find a bug?**
* Is it a bug in E3SM code? E3SM includes several codes that are developed
externally.
See [LICENSE](LICENSE) for
locations and, if appropriate, report your bug in the original developers site.
* Ensure the bug was not already reported by searching on our GitHub instance
under [Issues](https://github.com/E3SM-Project/E3SM/issues).
* If you are unable to find an open issue addressing the problem, open a new
one. Be sure to include a title, clear description, and as much relevant
information as possible, including the case, machine, compiler and compiler
version.
#### **Do you want to fix an existing bug?**
* Thank you!
* Before you start writing code, please read [Developing
E3SM](http://e3sm.org/model/running-e3sm/developing-e3sm/) to know more about
our development workflow.
* Open a new GitHub pull request with the patch.
* Ensure the PR description clearly describes the problem and solution. Include
the relevant issue number if applicable.
#### **Did you fix whitespace, format code, or make a purely cosmetic patch?**
Changes that are cosmetic in nature and do not add anything substantial to the
stability, functionality, or testability of E3SM will generally not be accepted
from non-staff.
#### **Do you intend to add a new feature or change an existing one?**
* We may not have the resources to test/evaluate new or changed features from
non-staff. Your feature PR will get attention if its part of the E3SM science
plan and coordinated by its management.
* If you would like to collaborate on E3SM development, see [E3SM
Collaboration](http://e3sm.org/about/collaboration/)
#### **Do you have questions about the source code?**
See our documentation at [e3sm.org](https://e3sm.org).
Computing file changes ...
