-
Notifications
You must be signed in to change notification settings - Fork 317
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge tag 'clm5.0.dev013' into release-clm5.0
Update cime and cism to newer versions used in release. These bring in some answer changes. The cime version updates the orbit for 2000 compsets. The cism version changes answers for two fields with NO_EVOLVE and more fields for EVOLVE. Fixes an important bug needed for use with Data Assimulation. Several changes to testing. Adding wallclock as needed, changing a few compsets so science supported compsets are used, added tput_tolerance to some tests known to be variable. Many changes to the clm tools for creating input files. Added the version by querying "git describe" and adding it as an attribute to NetCDF files. Changes to get tools working, and tested. Also changed so that tools can be run in either a CTSM checkout or a CESM checkout. Updated README files so they are accurate.
- Loading branch information
Showing
135 changed files
with
1,406 additions
and
9,762 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,21 @@ | ||
### General Type of Issue: | ||
Some example types are: | ||
- bug | ||
- enhancement | ||
- question | ||
|
||
### Details of Issue: | ||
(Be sure to give enough details that the issue can be understood sufficiently | ||
to replicate or to make the required changes) | ||
|
||
### For bugs fill out the following: (Otherwise remove, and remove any prompts that aren't useful) | ||
----------------------------------------------------------------- | ||
#### Important Details of your setup/configuration (compset, settings, etc.): | ||
|
||
#### Important output or errors that show the problem: | ||
|
||
#### What is the CTSM version you are using (output of git describe)?: | ||
|
||
#### What is the machine you are running on:? | ||
|
||
----------------------------------------------------------------- |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,16 @@ | ||
### Description of changes | ||
|
||
### Specific notes | ||
|
||
CTSM Issues Fixed (include github issue #): | ||
|
||
Are answers expected to change (and if so in what way)? | ||
|
||
Any User Interface Changes (namelist or namelist defaults changes)? | ||
|
||
Testing performed: | ||
(List what testing you did to show your changes worked as expected) | ||
(This can be manual testing or running of the different test suites) | ||
|
||
**NOTE: Be sure to check your Coding style against the standard:** | ||
https://github.com/ESCOMP/ctsm/wiki/CTSM-coding-guidelines |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,44 @@ | ||
## How to contribute: | ||
|
||
It's recommended that you first contact [email protected] to discuss the changes or additions that you propose. | ||
Work with them to think about the design and implemention of the changes as well as the planning | ||
and scheduling for the change to come into CTSM. | ||
|
||
It's also recommened that you join the [email protected] google groups in order | ||
to be informed about the science that is happening in CTSM as well as the latest develepments and tags. | ||
The ctsm-dev group is here: | ||
|
||
https://groups.google.com/a/ucar.edu/forum/#!forum/ctsm-dev | ||
|
||
Use the help from the wiki below to setup a fork and personal branch in GitHub to put your developments | ||
on and keep up to date with the master branch of CTSM. Once the changes are sufficiently advanced you | ||
can form a Pull Request on GitHub. Either from your fork on GitHub, or from the main ESCOMP GitHub page | ||
for CTSM (be sure to hit the "compare across forks" link at the top of the page when you first create | ||
the pull request). | ||
|
||
https://github.com/ESCOMP/ctsm/pulls | ||
|
||
This allows you to show your proposed changes and start getting feedback on them (even if they aren't finished). | ||
This also allows your changes to be planned for and slated for a time to come into CTSM master. In most | ||
cases you won't merge the Pull Request yourself, but a software engineer responsible for CTSM will do | ||
additional testing and bring the changes to CTSM master. | ||
|
||
### CTSM Developers Guide: | ||
|
||
https://wiki.ucar.edu/display/ccsm/Community+Land+Model+Developers+Guide | ||
|
||
## Getting Started: | ||
|
||
The following resources give you information on the project and how to get started. | ||
|
||
#### CTSM Wiki: | ||
|
||
https://github.com/ESCOMP/ctsm/wiki | ||
|
||
#### Coding Practices and Style: | ||
|
||
Code conventions: https://github.com/ESCOMP/ctsm/wiki/CTSM-coding-guidelines | ||
|
||
#### Code of Conduct: | ||
|
||
See the "CODE_OF_CONDUCT.md" file for expectations of how to work in the community. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.