-
Notifications
You must be signed in to change notification settings - Fork 0
RoleOrig
This text is taken from Section 6 of the Roadmap, p41-43.
The roles and responsibilities of the management committee would be:
a) To provide broad science directions for CABLE subject to the needs of stakeholders.
b) Maintain a record of who is working on different areas of the CABLE code, aid communication between parties interested in similar types of research and facilitate the creation of working groups as required.
c) Devise and review benchmarking tests for any proposed changes to the CABLE repository trunk and initiate extra tests where required.
d) Review documentation of any proposed changes to the CABLE repository trunk and integrate these into existing documentation if proposed changes are approved.
e) Identify potential conflicts (either structural or scientific) in multiple CABLE development proposals.
f) Request or perform (where resourced) ACCESS-CM tests of proposed changes if required.
g) Approve changes to CABLE trunk and determine trunk versions to be released as official updates of CABLE.
h) Recognise and document successful developments/approved changes, possibly through a CABLE annual report.
The CABLE management committee would need to meet at least every second month. It would be chaired by the CABLE coordinator and include representatives of each major group involved in CABLE development and one member of the technical support group. Members of the group need to have a good knowledge of the CABLE code.
The roles and responsibilities of the technical support group would be:
a) Management of the CABLE code repository including tagging repository trunk versions when official releases are approved.
b) Updating CABLE libraries for different coupled models for official CABLE releases, and mirroring these releases on the existing CABLE Sharepoint site.
c) Providing user support and training in technical aspects of using CABLE.
d) Providing a CABLE email help facility and responding to enquiries (initially as part of the ACCESS help facility).
e) Setting up code verification test runs for CABLE (offline and for key atmospheric models).
f) Assisting with aspects of the CABLE benchmarking process, including:
a. Checking coding standards are met in any new code.
b. Aid in the development of standardised offline and coupled (atmosphere-land model) evaluation tests for benchmarking, including the collation and formatting of input/forcing datasets.
c. Help deliver atmosphere-ocean coupled model runs (ACCESS) for benchmarking purposes
The technical support group should include all staff who are regularly involved in providing technical support to CABLE but may also involve those with a wider (ACCESS) role.
The roles and responsibilities of the CABLE coordinator would be:
a) Ensuring reporting needs on CABLE are met
b) Organise and chair meetings of the management committee, distribute agenda and action items.
c) Liaise with technical support group to ensure CABLE user needs are being met
d) Facilitate communication between CABLE users through a CABLE email list or other media, and annual (or 6 monthly) meetings
e) Facilitate community-wide science development through working groups
f) Provide mechanisms for CABLE achievements to be promoted e.g. web-site, possible annual report