SE/CPL Summary

Owned by Andy Salinger
Last updated: Nov 11, 2016
1 min read

Things SE/CPL wants you to know:

  1. Make sure all science capability you want to preserve is tested. 
    1. run_acme script, for example.
    2. You can't have the assumption that infrastructure doesn't change
  2. Slack messaging service is very valuable for informal communications: /wiki/spaces/ED/pages/36864779
  3. CMDV Software: Please consider investing time in
    1. SE Learning initiative of Mike Heroux
    2. Sub-component test of Anshu Dubey.
  4. Documentation on software and best coding practices is on our roadmap.

Highlights of meeting:

  1. Good revamp of SE roadmap
  2. CIME 5 complete rewrite is HUGE step forward for our infrastructure
    1. Python tools with XML configuration
    2. Deep expertise
  3. CIME Collaboration with CSEG going very well: win-win
  4. First JIRA Deep dive meeting made encouraging progress