Skip to content

November2016

Jump to bottom
rml599gh edited this page Jan 24, 2017 · 7 revisions

CABLE committee meeting, 30th November 2016, 2.00pm (AEST)

  1. Action items
  • Documentation of namelist file (README?) (Who?) VH has/will put additional comments in namelist file. JS considering namelist file split e.g. met forcing separate from switches. LN/VH already doing this e.g. luc.nml and cru.nml. CC possible concerns with this approach.
  • Update of user guide on wiki (Who?) Assess need.
  • Finalise documentation for trunk update (VH) RL to review #128
  • Determine method for getting trunk to compile/run for ACCESS (JS) Trunk for ACCESS done, #130
  • Merge #86 GSWP3 to current trunk (JS) Started. Check against Mark's branch
  • Work through remaining tickets at agenda 1b to assess status (JS) Still to do
  • Initiate meeting of writing group for issues paper and circulate draft when available (RL) Paper written
  • Set-up of 1000 points C-cycle test for general use (VH) Some progress. Trendy forcing data made available.
  1. Ticket report

Generally thought to be a good idea. Noted that this is just one step for code management. 3 parts - characterising tickets, approving trunk updates, defining best/default versions (for which bench-marking process becomes critical). Perhaps need to provide more information to users on how to best use the svn repository to isolate changes and keep up to date with the trunk.

  1. Trunk updates:

a) Updates this month

  1. See #128, #130

VH to close sub-tickets of #128. Cable canopy bug found by TZ/VH. Confirm fixed in trunk and add to ticket.

b) Updates in progress

i) GSWP3 #86 - had approved but does this need new merge with trunk?

Covered under action items

ii) #62 (radiation/albedo bug fix, ASAP), #92 (if BP confirms)

iii) #95 (and #44) - ??

iv) #70 - ready to go in - ??

Remaining tickets still to be reviewed/assessed in light of recent trunk updates.

  1. CABLE community activities

a) I/O working group

BP joined the meeting to report on the I/O working group. Two detailed submissions (from Saudi Arabia and South Africa) were received following an email request for comments on CABLE I/O. Also comments from JK. AP also offered summer student project support. Working group met 30 Nov (MdK, BP, CC, JS). Discussed/defined potential issues/projects. Initialisation sequence - is better documentation sufficient? GA suggested flowchart. Potential project on met forcing interpolation of GSWP3, 3 hourly to 1 hourly. VH suggested use of weather generator. Sensitivity to temporal down-scaling method generally. Potential project on multiple tiles per grid-cell even for higher resolutions. S Africans want 30 pft. Initialisation would need a generalised format. VH noted that output currently limited to patch or grid-cell but not both. CC to share code/capability for pfts from hi-res MODIS. Could make a collection of different resolution pft maps. VH noted that potential veg also now available in code.

b) Trunk consolidation/priorities. See notes: CodeConsolidation. MD is consolidating his changes on top of VH's recent changes to trunk (with and without SLI). Need to ensure ticket is adequately documented. Process from here: Jenkins tests with MH code. MH also running tests. Report back and then consider for trunk.

CASA-CNP changes from YPW. Issues with identifying changes because of format differences (another reason for enforcing coding standards in future). Need to check for duplication of functionality and put on switches if necessary. Check C conservation. RML/JS to follow-up.

  1. CABLE-JULES coupling

a) CABLE in JULES4.2+/UM10.+ Current work on UM10.5 - close to running?

b) Land-surface issues paper / ACCESS roadmap workshop No further action required at this time.

  1. Benchmarking/test suite

a) CABLE technical test suite – Jenkins work (NH) - documentation and roll-out

b) PALS

c) C-cycle addition to test suite: 1000 pts TRENDY experiment?

  1. Meetings

a) AMOS conference 2017, registrations open

b) Ozewex workshop, December 2016

  1. CABLE committee role, priorities, scope of coordinator's role (see https://jules.jchmr.org/community/management for JULES management, code management for CLM: https://trello.com/b/yzLcXkAx/cesm-clm-and-rtm-development ) Should other people be involved in the committee e.g. MD, MdK. People with more time. Consider size of committee.

  2. Next meeting date: 1st February

  3. Any other business

Action items

  • Documentation of namelist file (VH/JS)
  • Assess need for update of user guide on wiki
  • Review #128 documentation for trunk update (RL)
  • Merge #86 GSWP3 to current trunk (JS)
  • Work through remaining tickets at agenda 1b to assess status (JS)
  • Set-up of 1000 points C-cycle test for general use (VH)
  • Start producing Ticket Reports for review at committee meetings (JS)
  • Close sub-tickets of #128 (VH)
  • Check documentation for fix of canopy bug (VH/JS)
  • Follow-up of CASA-CNP merge (JS/RL)
Clone this wiki locally