Transcription
Overarching System TeamCecelia DeLuca/NESII (lead), Mark Iredell/EMC (presenter), Ligia Bernardet/DTC-GMTB,Jim Doyle/NRL, Mariana Vertenstein/NCAR, Jim Kinter/COLA, Larry Marx/COLA, FeiLiu/NRL-SAIC, Gerhard Theurich/NRL-SAIC, Patrick Tripp/EMC, Vijay Tallapragada/EMC,plus many involved with coupled system developmentNGGPS Annual MeetingAugust 5-6, 2016
Objectives Provide a portable, high performance, unified softwareinfrastructure for use in operational prediction models at NCEP. Coordinate and provide to NCEP a document on code, [data, anddocumentation] management for NEMS-based modelingapplications and suites. Promote communication and coordinated software developmentacross the NGGPS teams and related efforts in the community.
Unified Software InfrastructureCHARGE: Deliver multiple coupled system configurations following theNGGPS Implementation Plan and CPO MAPP awards, all running undera unified software framework, with EMC, broader NOAA, andcommunity engagement.ACHIEVEMENTS:1. Delivered initial global, regional, space weather, and land/hydrologycoupled system milestones running under the NEMS framework: Delivered development version (0.2) of the Unified Global CoupledSystem – Seasonal (UGCS-Seasonal) running under NUOPC/NEMS,with fully coupled GSM, MOM5, and CICE components, initializedfor a cold start and optimized for comparable performance withCFSv2.
Unified Software InfrastructureACHIEVEMENTS (cont): Delivered development version (0.1) of a single domain regionalconfiguration running under NUOPC/NEMS, with two-way coupledNMMB and HYCOM components. Delivered development version (0.4) of WAM and the IonospherePlasmasphere Electrodynamics (IPE) models validated underNUOPC/NEMS, with a one-way (WAM IPE) 3D coupling exchange. Delivered development version (0.2) of WRF-Hydro and LIS/Noahland validated running with GSM, MOM5, and CICE underNUOPC/NEMS, showing correct technical exchanges implementedamong components, not yet scientifically viable. Implemented WAVEWATCHIII coupled one-way to GSM(GSM WWIII), including nesting, running under NUOPC/NEMS.
Unified Software InfrastructureACHIEVEMENTS (cont):2. Delivered high performance modeling coupling tools capable ofsupporting a variety of coupled applications in a flexible andsystematic manner, based on community standards ESMF/NUOPC,with options for 2D and 3D grid remapping. Coordinated a merge of the NEMS development branch back to theNEMS trunk, which resulted in all development codes at EMC nowrunning through a NUOPC/NEMS driver. Established a way to systematically describe and test many newcoupled configurations using “compsets”, a concise nomenclature,e.g.:cfsr%20150401 1day leapfrog gsm%eul%T126 ww3%T188cfsr%20150401 30day nems gsm%eul%T126 cice%0.5 mom5%0.5 Provided ESMF/NUOPC/NEMS training for about 60 EMC staff,during multiple sessions.
Unified Software InfrastructureACHIEVEMENTS (cont):3. Initiated a NGGPS-funded pilot project with the Community EarthSystem Model (CESM) in which the main NEMS coupler/mediator willbecome a community component. The proposal is to distribute aversion of it through a shared repository created by NCAR calledCommon Infrastructure for Modeling Earth (CIME).NCAR has started building its next CESM implementation on couplercode shared with NEMS.
Unified Software InfrastructureDOCUMENTATION:All coupled model deliveries are documented BYnfSIWrJYfalD2lAIbUOGM0frNPEMIO ND28/edit#gid 0New NEMS User’s BTUd5SaB5D 3OUGX 93pWKP21QgTh4y6ok/edit#TEAM:Weekly communication with distribution of about 80, including:ESRL/CU NESII team (Fei Liu, Gerhard Theurich, Anthony Craig, CeceliaDeLuca, others), EMC (Xingren Wu, Jiande Wang, Bin Li, Mark Iredell,Suru Saha, Patrick Tripp, Jun Wang, Jack Woollen, Jiarui Dong, others),NCAR (David Bailey), COLA (Larry Marx, Jim Kinter), GFDL (Niki Zadeh),AOML (Steve Diaz, Gopal), others
Unified Software InfrastructureGAPS: EMC has not yet addressed several key system architecture questions.1Developers would benefit from the input of researchers with deepknowledge of and proven skill in the science of building coupledsystems with many model components on questions including how bestto seamlessly address a broad range of time and space scales. EMC would benefit from the formalization of a science team that spansits applications, and is authorized to make decisions about topics likethe system architecture (similar to the CESM Scientific SteeringCommittee). EMC would benefit from research community experimentation andcontribution to coupled model configurations. Currently GMTB’sexpertise and focus is the atmosphere, so that could be augmented andbenefit from partnerships (like the CIME pilot) that bring ent/d/1ySqAUtJiw2PrsfW 8cC4pypwiNv1wQ4EFolv2jeBL3w/edit#heading h.gor6vgpzooko
NEMS Component SchematicImage courtesy of DTC.
Model Components in NEMS(at least in progress as of Aug 5, 2016)Atmosphere NMM-B GSM FIM FV3 (soon)Chemistry GOCART CMAQOcean MOM HYCOM POMSea Ice CICE KISSWave WaveWatch3Land/Hydro LIS WRF-HydroIonosphere IPECoupling mediators Ensemble mediator Atmosphere-Ocean-Icemediator Physics-Chemistry mediator Space Weather mediator10
Coupled Compsets in NEMS(at least in progress as of Aug 5, 2016) noyear spaceweather datawam dataipe 20150401short nemscold gsm cice mom5 noyear spaceweather datawam ipe 20150401short%prof nemscold gsm cice mom5 noyear sbys hycom 2009 sbys gsm ww3 noyear sbys hycom%core2 2009 sbys ww3 noyear sbys hycom%core2%1.6 20150401long nems gsm cice mom5 2009 blocked gsm ww3 20150401long nems gsm cice mom5 slg 2009 leapfrog gsm ww3 20150401 nems gsm cice mom5 20150401short nems gsm cice hycom 20150401 nems gsm cice mom5 slg 20150401short nems gsm cice mom5 2009 nems gsm cice mom5 sbys lis wrfhydro 20150401short nems gsm cice mom5 ww3 2009 nems gsm cice mom5 wrfhydro sbys lis 20150401short nems gsm cice mom5 slg 2009 nems gsm lis cice mom5 sbys wrfhydro 20150401short nems gsm eulerian 2009 nems gsm lis cice mom5 wrfhydro 20150401short nems gsm slg 2013 sbys nmmb%glob20150401short nems nmm cice mom5 20150401short%prof nems gsm cice mom511
Code, Data, and DocumentationManagementCHARGE: Deliver a document that outlines issues, requirements, and plansrelated to code, data and documentation management, with EMC, broaderNOAA, and community engagement.ACHIEVEMENTS:1. Delivered updated Code, Data, and Documentation t/d/1bjnyJpJ7T3XeW3zCnhRLTL5a3m4 3XIAUeThUPWD9Tg/edit#heading h.ku78qulk21xhOrganized a meeting for September 1-2, 2016 at NCWCP, focused on EMCreview and evolution of the document. Workshop nems-workshop/2. The draft code/data/documentation management document includesproposed operating principles, a proposed standard requirements format,and initial requirements for software, documentation, and input and outputdata.Technical requirements were also initiated for land surface and ensembles.
Code, Data, and DocumentationManagementACHIEVEMENTS (cont)3. Initiated a Change Review Board (CRB) process for prioritizingNEMS-related work and allocating shared technical resources. Firstmeeting was March 8, 2016.TEAM:Contributors/reviewers include DTC (Bernardet, Carson), ESRL(DeLuca, Theurich, Liu), EMC (Iredell, Tolman, Saha, Trahan), NCARCESM (Large, Vertenstein), VLab (Sperow), COLA (Kinter, Marx), others.GAPS: Broader community review of the code/data/doc managementdocument will be needed after the September 1-2 meeting at EMC. EMC needs to establish a regular schedule for NEMS CRB meetings(at least twice a year).
Communication and CoordinationCHARGE: Communication and coordination across NGGPS teams and related effortsin the community.ACHIEVEMENTS:1. Initiated documentation survey and gap analysis across NEMS components,model applications, and end-to-end suites. Contacted participants NGGPS-widefor input. Included general, scientific, technical, and user documentationcategories per 6uzJrjrsY-um0jB5hU-Gfeh3 VCIJDA4Ibmu5s/edit#gid 0Recently addedrequirements andtutorial categories.2. Began migratingall developerdocumentation toan EMC CommunityWorkspace on modeling-center/home
Communication and CoordinationACHIEVEMENTS (cont):3. Agreed to a preferred technical documentation format (in a repository withcode, set up so that it is automatically updated with code updates), andimplemented physical parameterization, physics driver documentation, andother documentation in this format.TEAM:Organized by DTC (Bernardet), NESII (DeLuca, Liu), and EMC (Howard, Kunkel,Iredell); others have been contributing ideas and information.GAPS:Several components do not appear to have documentation, or are missingspecific kinds of documentation. Much of the technical documentation is notin the preferred format, and it needs to be reviewed for clarity andcorrectness.EMC would benefit from redesign of their primary website(http://www.emc.ncep.noaa.gov/) and dedicated resources to maintain it.This process will be easier if developer documentation is moved off theprimary website to a VLab community workspace.
OAS Role and LeadershipOVERALL GAPS:Topics the OAS has tried to address (including system-widearchitecture, organizational coordination, and communication) wouldnormally be aspects of organizational management. The leadershipand membership of OAS is primarily technical. It would benefit fromworking more closely with EMC management and science leadership.
AcknowledgementsThe work presented is supported by the NGGPS program, the CPOMAPP program, and the NSF EarthCube program.
(DeLuca, Theurich, Liu), EMC (Iredell, Tolman, Saha, Trahan), NCAR CESM (Large, Vertenstein), VLab (Sperow), COLA (Kinter, Marx), others. GAPS: Broader community review of the code/data/doc management document will be needed after the September 1-2 meeting at EMC. EMC needs to establish a regular schedule for NEMS CRB meetings
