180 likes | 197 Views
Strategic Plan Implementation. Cecelia DeLuca/NCAR (ESMF) December 17, 2008 ESMF Board/Interagency Meeting. Strategic objectives through 2010. Complete functionality and increase ease of use Integrate ESMF into science gateways Support integration into applications. Release Plan.
E N D
Strategic PlanImplementation Cecelia DeLuca/NCAR (ESMF) December 17, 2008 ESMF Board/Interagency Meeting
Strategic objectives through 2010 • Complete functionality and increase ease of use • Integrate ESMF into science gateways • Support integration into applications
Release Plan 2002 2003 2004 2005 2006 2007 2008 2009 2010 ESMF v1 Prototype ESMF v2 Components, VM and Utils ESMF_GridCompRun() ESMF v3 Index Space Operations ESMF_ArraySparseMatMul() Complete re-write ofdata and grid structuresfor generality and robustness ESMF v4 Grid Operations ESMF_GridCreate() ESMF_FieldRegrid() ESMFv5 Standardization Build, init, data types, error handling, … Public release May 2008 ESMF v3.1.0r
Outstanding functionality From ESMF Strategic Plan: 1. complete an ArrayBundle class that enables optimized data transfers of multiple Arrays 2. complete the Field and FieldBundle communications methods 3. integrate contributed Location Stream code for the representation of observational data 4. complete arbitrary distributions for structured Grids, introduce multi-tile Grid methods, and implement exchange Grids 5. complete the interface to a general regridding package (still need conservative regrid) 6. complete the interface to unstructured Meshes 7. complete a C interface 8. complete a hierarchical attribute package 9. complete a rudimentary IO package 10. complete a compliance tester for components
Data representation options ESMF data structures were reworked and released in ESMF v3, starting May 2006. Two options: 1. Representation in index space (Arrays) • One or more logically rectangular tilesstore indices and topology • Sparse matrix multiply for regridding withuser supplied interpolation weights • Highly scalable - no global information held locally 2. Representation in physical space (Fields) • Built on Arrays + some form of Grid • Grids may be logically rectangular, unstructured mesh, or based on location of observations • Regridding using parallel on-line interpolation weight generation, bilinear or higher order Supported Array distributions
Coupling options Multiple executable options • Single executable • Multiple executable • Couplingcommunicationscan be set up and calledin a coupler • Coupling communications can be setup in a coupler but calleddirectly from within components – useful when it is inconvenient to return from a component in order to perform a coupling operation • Recursive components for nesting higher resolution regions • Ensemble management, including sequential execution of ensemble members Contributed by U Maryland Coupler Comp B Comp A Comp A Comp B Array send/recv
Results for ESMF higher orderregrid in CCSM • dTAUx/dy - closely related to the curl of the wind stress, which drives the upper ocean circulation and is therefore important to represent accurately in climate simulations • Mapped from the T62 (2-degree) Community Atmospheric Model (CAM) grid to the gx1v5 (384x320 irregularly spaced) • Noise is calculated as deviation of a point from the sum of itself plus four neighbors • 33% reduction in noise globallycompared to current bilinear approach Interpolation noise in the derivative of the zonal wind stress Interp. noise grid index in latitudinal direction Black = bilinear Red = higher-orderESMF v3.1.1 Green = higher order ESMF v4.0.0
Usability Metrics: Bugs 40% reduction from peak (230 to 140)
Usability Metrics: Feature Requests 30% reduction from peak (110 to 76)
Usability Metrics: Support Requests Holding steady
Port and test status • 30+ platform/compiler combinations regression tested nightly, new ports include gfortran (4.3) and Solaris, Windows in progress http://www.esmf.ucar.edu/download/platforms • Received award to employ the TeraGrid Build & Test service to access additional platforms for testing • New test harness for automating the test coverage of a huge grid and distribution parameter space
Strategic objectives through 2010 • Complete functionality and increase ease of use • Integrate ESMF into science gateways • Support integration into applications
Metadata export from ESMF (v4.0) • ESMF holds information about grids, component inter-relationships • Users can associate additional metadata with ESMF classes (Grids, Arrays, Fields, States, Components) • Metadata is stored as name/value pairs in Attribute packages • Attribute packages can be standard (e.g CF conventions for Fields) or custom • Packages can be nested – for example, metadata for an import State contains metadata for all the Fields in the State. • Metadata can be exported in plain text or XML format … • then ingested into portal, where users can search and browse components, more (Curator talk) Preview of the portal for dynamical core comparison developed jointly with ESG Image courtesy of Rocky Dunlap, Georgia Institute of technology
More on science gateways … • Work in progress: translation of ESMF interfaces into web service interfaces to support loose coupling and integration of components into service oriented architectures • Will enable invocation of ESMF components and applications from a portal in a Grid-based (e.g. Teragrid) gateway • Data and metadata from the run stored back to the portal Image courtesy of Rocky Dunlap, Georgia Institute of technology
Strategic objectives through 2010 • Complete functionality and increase ease of use • Integrate ESMF into science gateways • Support integration into applications
HAF GAIM Support and broaden the customer base Jan 2008
ESMF adoption • 76 components in the community – most recent additions are CCSM4 dead and data components. (Live coming next…) • 4 large production or operational codes running ESMF: • NCEP GFS • GEOS-5 • HYCOM-CICE • COAMPS-NCOM • Goals from strategic plan for end 2010: • 100 components • 20 large production or operational codes running ESMF Image courtesy of Rocky Dunlap, Georgia Institute of technology
A peek at the future … 2009 2010 2011 2012 2013 2014 2015 Interoperability Compliance definitionsand verification tools Integration with workflows Generation of service interfaces for loose coupling Metadata links to data and other services Automated model assembly andrun environment Based on metadata files Tutorial development andclassroom deployment Numerical/computational maintenance and development