-
Notifications
You must be signed in to change notification settings - Fork 0
TrunkUpdates
Paul Leopardi edited this page Oct 8, 2024
·
3 revisions
Your changes will need to be approved by the CABLE committee (CableCommittee). Submissions to the committee needs to be via a Ticket. The following information should be included in the ticket.
- Who contributed to the code development, and their institution
- The branch location of the code changes, and the svn revision number(s).
- A statement that CABLE coding standards have been adhered to
- The purpose of the code development and the resulting model behaviour
- Benchmarking results should be described briefly. For ACCESS runs, include the UMUI job code (and do not reuse this for another simulation).
- Any appropriate technical documentation, user guide modifications or more detailed benchmarking results should be attached.
For more information, see section 4 of the Guidelines for CABLE users and developers.
As the CABLE code trunk is updated, tagged versions of the code will be created periodically. Having started at CABLE2.0, tags will be of the format 2.x.y where an increment to x will indicate a science change to CABLE while increments to y will indicate a technical change.
Back to CableHelp