Skip to content

October2016

rml599gh edited this page Oct 18, 2016 · 12 revisions

CABLE committee meeting, 19th October 2016, 2.00pm (AEST)

  1. Trunk updates:

a) Updates this month

  1. See #128

  2. logs of updates @ https://trac.nci.org.au/trac/cable/log/trunk?action=stop_on_copy&rev=3825&stop_rev=3824&mode=stop_on_copy&verbose=on

  3. A part III of this series of updates will be made this afternoon once corresponding ".trunk_sumbal" files have been generated. However, these are largely obsolete as Jenkins testing is online.

  4. ACCESS is at present unusable with the head of the trunk. Ad hoc modifications to the trunk to run in ACCESS can be made. Updating the trunk so that these are not necessary is in progress.

  5. As this is such a large update, as well as removing immediate ACCESS capability, I suggest we spam cable_users?

  6. I suggest we spam cable_users re: Jenkins usage once this is finalised.

*Changes include bug fixes and addition of VH modules. Extra changes in progress to ensure backwards-compatibility of I/O. This version should be tagged but would be good to have a solution on ACCESS compiling and running first. Issue is associated with use of netcdf. Need to assess need for any further documentation. *

b) Updates in progress

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

Yes

ii) #62 (radiation/albedo bug fix, ASAP), #92 (if BP confirms), #66 (initialisation bug), #89 - Jenkins tests? - are any of these included in the trunk update?

#66 done in this months update. #89 can be closed.

iii) SLI and POP and other VH/LN enhancements, #18, #61, #73, #93, #90, #94. - presumably these all now in, but work still required for ACCESS applications??

Incorporated under #128 and have gone into trunk.

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

#95 will overlap with Haverd2013 option. Needs to be switchable.

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

JS to work through remaining tickets on this list and resolve where appropriate with input from BP.

  1. CABLE community activities

a) Trunk consolidation/priorities. See notes: CodeConsolidation. Next steps (including action items from last meeting)?

MD hydrology to be next merge, then need to assess BP/YPW branch against trunk and consolidate.

b) CABLE video conference, October 26th. Program?

VH talk, then mostly discussion around bench-marking (YPW and GA to lead), I/O (CC and BP), role of CABLE committee and coordinator (RL).

  1. Land-surface modelling issues paper (2 pages) for ACCESS roadmap planning meeting

Brief discussion as input to writing team for issues paper due Nov 14 (RL, HZ or ID and GA). Issue of CABLE pathway for NWP, DA. Draft document to be circulated when written (also to be circulated to ACCESS RLG group around Nov 7).

  1. CABLE-JULES coupling not discussed

a) Progress with coupling into UM8.5 for ACCESS-CM2.

b) CABLE in JULES4.2+/UM10.+ - Video con with Met Office

  1. Benchmarking/test suite

a) CABLE technical test suite – Jenkins work (NH), ACCESS tests

*Jenkins - helpful to differentiate between technical tests (compile/run/bitwise reproducible) with benchmarking tests. Is it feasible for Jenkins to be running simple quick tests as one process and longer set of tests as a batch job? Need to consider storage requirements and how many sets of test output are kept/archived. *

b) PALS

Not discussed.

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

Need for a test with full C cycle. VH offering to set up and make available her 1000 pts test but needs to have Trendy data in common data area. VH to follow-up with BP about organising this and what documentation/permissions might be required. Not sure about feasibility of running this under Jenkins as takes a few hours. May be worth setting up a single-site test as well as an initial test.

  1. Meetings

a) AMOS conference 2017, abstract deadline passed

Proposal is to combine atmosphere-land sessions due to limited abstract submissions. Number of oral spots still to be confirmed.

  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 )

Need to consider if we want to update the CABLE committee and coordinators role. Also note that CABLE roadmap proposed a technical support group. Currently just JS and BP fulfilling most of the function of that group. Suggest make this a discussion item at video conference.

  1. Next meeting date: Wednesday November 30th, 2pm?

*To be confirmed. *

  1. Any other business

Action items - September 2016

  • Documentation of namelist file (README?) (Who?)
  • Update of user guide on wiki (Who?)

Action items - October 2016

  • Finalise documentation for trunk update (VH)
  • Determine method for getting trunk to compile/run for ACCESS (JS)
  • Merge #86 GSWP3 to current trunk (JS)
  • Work through remaining tickets at agenda 1b to assess status (JS)
  • Advertise video conference and confirm program/speakers/discussion leads (RL)
  • Initiate meeting of writing group for issues paper and circulate draft when available (RL)
  • Set-up of 1000 points C-cycle test for general use (VH)
Clone this wiki locally