ESMF Change Review Board

1
ESMF Change Review Board
Climate
Data Assimilation
Weather
Robert Ferraro ESMF Board Meeting Dec 17,
2008 Robert.Ferraro_at_JPL.NASA.GOV
2
Organization Governance
Executive Management
Executive Board Strategic Direction Board
Membership Appointments
Reporting
Interagency Working Group Stakeholder
Liaison Programmatic Evaluation
Advisory Board External Projects
Coordination Community Adoption Evaluation
Reporting
Project Execution
Joint Specification Team (open membership) Require
ments Definition API Specification Design
Reviews External Code Contributions
Change Review Board Development
Priorities Release Review Approval
Functionality Change Requests
Development Constraints
Implementation Schedule
Core Development Team Project Management Software
Development Testing Maintenance Distribution
User Support
Requirements Collaborative Design Beta Testing
3
The Change Review Board Process

• Gather community and stakeholder input
• Special joint CRB/JST telecon prior to each CRB
  meeting
• Ad-hoc consultation by CRB members with their
  respective communities and stakeholders
• Meet quarterly to review and update the
  development schedule
• Review and approve (sometimes with adjustments)
  the next internal release
• Review community inputs, and add development
  tasks to the schedule based on this input
• Adjust the future release schedule based on
  current realities and changing priorities
• Publish the updated schedule on the ESMF CRB web
  page
• http//www.esmf.ucar.edu/plans/releases/sched_curr
  ent.shtml
• Or Navigate from the ESMF main page via the
  Release Schedule Quick Link

4
The CRB Membership

• Robert Ferraro, ChairNASA Jet Propulsion
  Laboratoryrobert.ferraro_at_jpl.nasa.govTom
  BlackNOAA National Centers for Environmental
  Predictiontom.black_at_noaa.govAlan
  WallcraftNaval Research Laboratorybei_chief_scie
  ntist_at_nrlssc.navy.milThomas Clune Resigned
  9/12/08NASA Goddard Space Flight
  Centerthomas.l.clune_at_nasa.govChris
  HillMassachusetts Institute of
  Technologycnh_at_plume.mit.eduMariana
  VertensteinNational Center for Atmospheric
  Researchmvertens_at_ucar.eduAtanas TrayanovNASA
  Goddard Space Flight Centertrayanov_at_janus.gsfc.na
  sa.govCecelia DeLuca, ex officioNational
  Center for Atmospheric Researchcdeluca_at_ucar.edu

• Members are appointed by the ESMF Execute Board
  to 1 year renewable terms
• Members represent the user community, not just
  their own institutions or agencies

5
Hows It Working?

• CRB continues to meet quarterly (mostly via
  telecon)
• Approved 2 Internal Releases (v3.1.0, v3.1.1) and
  1 Public Release (v3.1.0r)
• Development focus this past year has been on
  moving ESMF to the new Array and Grid structures,
  array and grid redistribution capabilities,
  implementing and testing the new sparse matrix
  multiply functionality, and performance
  optimization. These are all now in the Public
  Release v3.1.0r.
• The new internal structures, along with the
  sparse matrix multiply, are key to ESMF support
  for Regridding.

6
Planning For 2010

• ESMF has committed to a stable API (with backward
  compatibility) in 2010
• This past August, the CRB held an extended
  meeting to look at development priorities and a
  schedule for meeting this commitment
• Focus is on completing remaining high priority
  functionality development that would have an
  impact on the ESMF API
• High priority items identified are
• User-method Callbacks for data assimilation
• Conservative regridding
• Multi-tile grid representations
• Land-sea masks for regridding
• An I/O implementation

7
Planning For 2010 (cont)

• The CRBs highest priority is to assure that
  development which has an impact on the ESMF API
  is completed and delivered in Public Release
  v5.0.0r. This release has been tentatively
  scheduled for April 2010.
• The development schedule has been fleshed out to
  the Apr 2010 Public Release. The schedule was
  developed with larger than normal margin so that
  the stable API commitment in 2010 can be
  achieved.
• After May 2009, the backlog in the feature
  request log will be cleared out in the context of
  the v4.0 functionality
• Some feature requests may be closed out as
  obsolete or as subsumed under existing
  functionality
• Six Months is reserved before the end of FY10 to
  clean up documentation and update tutorial
  materials

8
The Release Schedule

• ESMF Release Schedule