Software Engineering Working Group Meeting

1
Software Engineering Working Group Meeting

• Tony Craig, Cecelia Deluca, Patrick Worley
• (co-chairs)
• February 4 5, 2003
• NCAR
• Mesa Lab Access Grid

2
Agenda

• Tuesday AM, 4 February 2003
• 800 Continental Breakfast
• 830 - 845 Introduction (Pat Worley)
• 845 - 1000 Status Of CCSM SE (Tony Craig)
• 1000 - 1015 Break
• 1015 - 1100 Update on SciDAC (John Drake)
• 1100 - 1145 Update on ESMF (Cecelia DeLuca)
• 1145 - 130 Lunch

3
Agenda

• Tuesday PM, 4 February 2003
• 130 - 230 Incorporation of ESMF in CCSM
  (Erik Kluzek)
• 230 - 330 CAM Process, Redesign, and Plans
  (Tom Henderson)
• 330 - 400 Break
• 400 - 430 Incorporating CAM into a Data
  Assimilation Testbed (Jeff Anderson Kevin
  Raeder)

4
Agenda

• Wednesday AM, 5 February 2003
• 800am Coffee
• 830 - 900 CCSM Testing Status
• (Tony Craig/Lawrence
  Buja/Wei Yu)
• 900 - 1045 CCSM Testing Discussion
• (Pat Worley to lead)
• 1045 - 1100 Break
• 1100 - noon Open Discussion
• More details on
• http//www.ccsm.ucar.edu/working_groups/Software
  /agendas/030204.html

5
Addenda

• Dave Parks talk on the architecture of the SX-6
  (scheduled for Tuesday afternoon) has been
  cancelled.
• DOE-sponsored workshop on issues in porting the
  CCSM to the Cray X1 (and possibly other vector
  systems) to be held on Thursday, February 6. For
  more information, visit
• http//www.csm.ornl.gov/meetings/climate2.html
• This meeting is not on the access grid, but
  presentations and a summary will be posted after
  the meeting.

6
Role of CSEG

• The CCSM Software Engineering Group is
  responsible for
• Coordinating the computational development of
  model components,
• Overseeing the evolving design of the CCSM,
• Optimizing the model, and
• Preparing releases.

7
Role of SEWG

• The role of the CCSM Software Engineering Working
  Group is to
• Involve the broader CCSM community in
  computational discussions and decision-making,
• Inform the community of CSEG and SEWG activities,
  and
• 3. Serve as a liaison to external computer
  science and software engineering efforts,
  bringing relevant external activities to the
  attention of the CCSM community.

8
CSEG Successes

• External developers were able to contribute, and
  accelerate, development of CCSM component models.
  This was due to
• Good will on the part of people both inside and
  outside of NCAR
• Testing procedures
• Change Review Boards managing development and
  establishing priorities
• 3. Many, many others ? (see Tonys talk).

9
CSEG Issues

• Defining processes that can be maintained with
  available manpower and compatible with aggressive
  deadlines. Examples include
• Documents (design, requirements, )
• Testing and check-in procedures what
  experiments, what machines, who prioritizes, who
  validates, failure detection and rollback
  mechanisms,
• Many, many others. (See Tonys talk and rest of
  meeting agenda.)

10
On With The Show