Interim ReviewCupid: An IDE for Model

Development and Modeler Training

Cecelia DeLuca1, Rocky Dunlap2, Spencer Rugaber2

1NOAA ESRL/University of Colorado2Georgia Institute of Technology

April 15, 2014

https://earthsystemcog.org/projects/cupid/

Outline

• ESMF and the NUOPC Layer• The Earth System Prediction Suite (ESPS)• NASA Modeling and ESPS• NUOPC Layer in Model E• Cupid IDE• Cupid Demo

The Earth System Modeling Framework (ESMF) was developed as a multi-agency response to calls for common modeling infrastructure.

ESMF delivered:•Standard interfaces for model components•High performance libraries and tools for time management, data communications, metadata and I/O, and parallel grid remapping

The Earth System Modeling Framework

Metrics:~5500 downloads

~3000 individuals on info mailing list

~40 platform/compilers regression tested

~6400 regression tests

http://www.earthsystemmodeling.org

The initial ESMF software fell short of the vision for common infrastructure in several ways:

1. Implementations of ESMF could vary widely and did not guarantee a minimum level of technical interoperability among sites

2. It was difficult to track who was using ESMF and how they were using it

3. There was a significant learning curve for implementing ESMF in a modeling code

New development directions address these gaps.

New Directions

1. Implementations of ESMF could vary widely and did not guarantee a minimum level of technical interoperability among sites

• The National Unified Operational Prediction Capability (NUOPC) is a consortium of operational weather prediction centers and their research partners

• NUOPC developed the NUOPC Layer software to increase interoperability of ESMF components

• The NUOPC Layer adds to ESMF:• A formalism that describes and splits the phases of initialization• A formalism for checking and reporting whether component requirements

are satisfied during the run sequence• Code templates for drivers, models, mediators (couplers) and connectors,

and example application showing a variety of model interactions (e.g. explicit, semi-implicit, implicit coupling)

• Compliance checkers

The National Unified OperationalPrediction Capability

2. It was difficult to track who was using ESMF and how they were using it

• The Earth System Prediction Suite (ESPS) is a collection of weather and climate modeling codes that use ESMF with the NUOPC conventions.

• The ESPS makes clear which codes are available as ESMF components and modeling systems.

ESPS on CoG:

https://www.earthsystemcog.org/projects/esps

The Earth System Prediction Suite

Currently, components in the ESPS can be of the following types:coupled system, atmosphere, ocean, wave, sea ice

Target codes include:• The Community Earth System Model (CESM)• The NOAA Environmental Modeling System (NEMS) and Climate Forecast System

version 3 (CFSv3)• The MOM5 and HYCOM oceans• The Navy Global Environmental Model (NavGEM)-HYCOM-CICE coupled system• The Navy Coupled Ocean Atmosphere Mesoscale Prediction System (COAMPS) and

COAMPS Tropical Cyclone (COAMPS-TC)• NASA GEOS-5• NASA ModelE

Model Codes in the ESPS

The ESMF team has been working with GISS developers and GSFC staff to implement NUOPC interfaces in Model E

Current status:• Model E can be driven by a NUOPC driver.• Ocean, atmosphere and “other” components are wrapped in NUOPC interfaces• The system validates bfb for a simple active atmosphere configuration (EM20), test

report here:http://www.earthsystemcog.org/projects/cupid/testreport_0106

The overall status for this activity is tracked here:https://www.earthsystemcog.org/projects/cupid/modeleplans

ESMF/NUOPC Layer in Model E

ESPS Code Status

  LEGEND              Compliant (Completion date) In progress   Candidate             

Coupled Modeling Systems  NEMS CFSv3 COAMPS /

COAMPS-TCNavGEM-HYCOM-CICE

GEOS-5 ModelE CESM

  2014 2014     2015 2015 2014Atmospheres

GFS/GSM              NMMB              CAM             2014FIM 2014            GEOS-5 FV         2015    ModelE Atm           2014  COAMPS Atm              NavGEM              NEPTUNE              WRF             2014

OceansMOM5              HYCOM              NCOM              MPAS-O              POP             2014

IceCICE 2014 2014     2014 2014 2014

WaveWW3 2014   2014   2014   2014SWAN              

Spanning major climate, weather, and ocean codes, ESPS is the most directresponse to calls for common modeling infrastructure yet assembled

ESPS creates opportunities for the Cupid team:• There is an opportunity for the GEOS-5 and Model E codes to become more

interoperable with other codes in the community, and each other.o The NUOPC Layer and the Modeling Analysis and Prediction Layer (MAPL) that GEOS-5

uses are similarly structured and share use of ESMF as an underlayer. A report details the relationship between the two software packages, here: http://www.earthsystemcog.org/site_media/projects/nuopc/paper_1401_nuopc_mapl.docx

o The ESMF and GMAO teams plan to incorporate MAPL into the ESMF distribution, in much the same way that NUOPC is bundled with ESMF.

o This will create opportunities for reducing redundancy and further merging the NUOPC Layer and MAPL packages.

o A translator will be written to convert between the interfaces.

• There is an opportunity for training users across ESPS modeling systems.

ESPS and Cupid

Cupid Development andTraining Environment

3. There was a significant learning curve for implementing ESMF in a modeling code

CUPID GOAL: Make ESMF training and development simpler and more appealing•NOAA CIRES, GA Tech, and NASA GISS/GSFC collaboration•Eclipse-based “Integrated Development Environment” or IDE•Customized for ESMF applications with NUOPC conventions

Cupid is a working prototype expected to be ready for first public release in FY14.

Cupid project: https://earthsystemcog.org/projects/cupid/

Cupid tutorial:https://github.com/cupid-ide/cupid/blob/master/org.earthsystemcurator.cupid.nuopc.fsml/doc/latex/cupid.pdf?raw=true

Cupid Development andTraining Environment

Select sample code or model • Pick a training problem (or coupled model)

• Generate a framework-aware outline of the source code

• Navigate around the source code using the outline

• Use an editor to modify the source code

• Automatically generate code needed for NUOPC compliance

• Compile and run locally or on a cloud (currently Amazon Web Services)

Run locally or on a cloud

Source code editor

Console for viewing output

Projectexplorer

NUOPC outline

Selecting the TrainingScenario or Model

Four options are available,

each with a different architecture and coupling behavior:•Single Model with Driver•Coupled Atmosphere-Ocean Driver•Coupled Atmosphere-Ocean with Mediator and Driver•Model E EM20 (atmosphere only) configuration (untested)

Scenario selection:•Populates the Project Explorer•Determines software prerequisites

Smart, Framework-aware Code Editing Environment

Central idea: A framework-aware editor provides contextual guidance as code is being written by checking for compliance to framework rules and automatically generating and inserting code fragments into existing code

Reverse engineer

Generate code

Smart, Framework-aware Code Editing Environment

NUOPC View•compact outline of NUOPC component source code•linked with source code editor•contextual reference documentation•compliance issues shown in red•new elements can be added to outline, simultaneously generating code in the editor

Behind the Scenes:Smart, Framework-awareCode Editing Environment

Running Code in Cupid: Local orCloud-based Job Submission

Eclipse projects can be configured to run on a personal or cloud-based computing system.

What advantages does cloud-based computing offer for an IDE?

•Configuration of a computational environment for compiling and running models requires expert knowledge, and•Configuration of an IDE for a particular computing system (e.g., NASA/Discover) introduces complexity

Cloud-based Training Environment

Central idea: Integrate cloud computing with the IDE so trainees get quickly to important learning objectives

Advantages:•trainee not required to configure computational environment•on-demand training in low-risk sandboxes•pre-configured scenarios highlight important ESMF/NUOPC concepts

New Cupid Training Project Wizard spins up Amazon EC2 instances

Behind the Scenes:Cloud-based Training Environment

NESII Amazon Elastic Compute Cloud (EC2) account:•preconfigured machine images – NUOPC and ModelE (EM20 rundeck)•can request access to NESII cloud account, or•can provide your own EC2 account credentials

XML-based training scenario configuration:

Thanks!

https://earthsystemcog.org/projects/cupid/

Extra slides

Behind the Scenes:Smart, Framework-awareCode Editing Environment

Structural Pattern Expression Structural Elements Matched

module Matches a Fortran module

m moduleName Matches the name of the module m

m subroutine Matches a subroutine defined inside module m

m subroutine(name(type1, type2, ...))orm subroutine(*(*))

Matches a subroutine defined inside module m with the given signature. The wildcard * can be used in place of the name and/or types.

s subroutineName Matches the name of subroutine s

s formalParam(i) Matches the ith formal parameter of subroutine s

Mapping Types

Behind the Scenes:Smart, Framework-awareCode Editing Environment

Structural Pattern Expression Structural Elements Matched

s call Matches a subroutine call within the implementation of subroutine s

s call(name(arg1, arg2, ...)) Matches a subroutine call within the implementation of subroutine s to a subroutine with the given name and given set of argument.

c argByIndex(i) Matches the ith argument value for the call c

c argByKeyword(keyword) Matches the value of the argument with the given keyword for the call c

Mapping Types (cont.)

Behind the Scenes:Smart, Framework-awareCode Editing Environment

NUOPC Driver

driverName

standardNUOPCImport

callsGenericSetServices

module(#driverName)

usesModule(NUOPC)

standardESMFImport usesModule(ESMF)

implementsSetServices subroutine(*(inout type(ESMF_GridComp) #p_gcomp, out integer #p_rc) )

... call(#^genericImports/importsGenericSS

(#^p_gcomp, #^p_rc))

genericImports usesModule(NUOPC_Driver)

importsGenericSS usesEntity(routine_SetServices)