CCSM Ocean Model Development:
Practical Issues
CSL Computer Allocations
- Two separate ocean CSL accounts: "development" and
"production"
- Total allocation: 290 GAUs/day
- gx1v3,T42, fully coupled CCSM (all active components) costs
~65 GAUS/day ("regular" cost factor). CSL allocation would allow
~4.5 model years/day
- gx3, "ocean only" coupled with CCSM data models
costs ~1.7 GAUS/model year ("regular"). CSL allocation would
allow ~170 model years per day.
- "economy" jobs cost one-half as much as "regular" jobs, but
when demand is high, economy-job turn-around is poor
CCSM Ocean-Model Code Access
There are two methods for accessing CCSM Ocean Model Code:
- Official CCSM2.0.1 Release from CCSM website
http://www.cesm.ucar.edu/models/ccsm2.0.1/
- CCSM CVS Repository
CCSM CVS Repository Access
- Everyone needs permission to access the CCSM CVS Repository
- With permission, users can check out component models and check in changes onto development branches in the repository
- CVS does not allow much privacy; all users have wide-ranging
access to repository. Must rely on user's
honorable behavior to avoid inappropriate check-ins
(on the main branch, e.g.) or access to other developers' private
branches.
- CCSM Ocean Model CVS Repository is not presently officially accessible by users outside CGD... which leads us to
OWG Code Development Issues
- Does the OWG want to allow wider access to the ocean-model repository?
- How should the ocean-model repository be managed?
- Atmospheric Working Group has established extensive rules
and guidelines for atmospheric-model (CAM) repository access:
- formal change review board, meets regularly,
with conference-call access for off-site review-board members
- formal approval and scheduling of all model changes,
with web-accessible documentation
- strict policies on repository access and
tagging requirements for testing prior to check-in
- coding standards, naming conventions
- "gate-keeper" for main development branch
- official policies on use of CAM developments in other applications
Discussion
Now or later...
Return to the top of this document