GEOSS Future Products Workshop: Session 4: Model Web NOAA, Silver Spring, MD 27 March 2013 Moderator: Stefano Nativi Rapporteur: David Arctur

Session 4. Model Web – 1

Session 4. Model Web – 2

Session 4. Model Web – Some Conclusions Include modeling/process capabilities as discoverable and usable GEOSS resources –Being user-driven –Lowering entry barriers Recognize that GEOSS has different User types, and Model Web addresses some of them Start a forum to discuss model integration challenges (OGC) Work out a short term roadmap for the Model Web, including effective show cases –Considering low hanging fruits –Integrating existing components

Stefano Nativi, Model Web Initiative Vision: dynamic web of models, integrated with databases and websites  consultative infrastructure for asking “what if” questions, e.g.: –How will climate change affect infection rate of dengue fever in Vietnam? Huge amounts of data available Numerous models & modeling frameworks Links/interfaces needed for connecting vocabularies, brokers, knowledge bases, business processes  how to combine what is needed??

Models, Tools Tightly coupled, loosely coupled, Model as a Service –Simulations (OpenModeller, nanoForge, nanoHub) –Frameworks Object Modelling System ModCom, Invisible Modelling Environ, … Etc –Controlled vocab’s, thesauri GEMET, INSPIRE, GCMD, GEOSS, etc Brokering semantic assets GEOSS Ontology WG –Knowledge bases GEOSS User Requirements Registry (URR) Gazetteers, including event gazetteers

Brokers GEOSS Brokering Framework (DAB) –Discovery intermediation –Access intermediation Spatial-temporal CRS Formats Data subsetting Data aggregation –Resources: data, services, documents, models

Model Web Not a dedicated tool, model framework, or workflow framework It is a facilitation framework, supporting: –Open access –Minimal barriers to entry –Interface-driven approach, service/resource based –Scalable, distributed Challenges –Manage heterogeneity of resources –Agreed definition of “model” representation –High-performance computing –Long-term access; standardization vs virtualization

Gary Geller, Model Web for Biodiversity & Ecosystem SBAs Scientists generally not considering how to work together but how to solve their problems of interest Resources not easily found or managed Ecology is hard; “not physics” Some models are better and more used than others Websites connect models and audiences, critical Getting started to develop Model Web: –Keystone models, small planned focused webs –Balance between cowboy – fascist approaches –Growth phase  Mature phase: become useful  become good  achieve global infrastructure

Hans-Peter Plag: Model Web Business Process, with GEOSS URR Model Web Examples: Geo-Design, integrating across architecture and construction Internet of Things, intercommunicating Internet of Models? or Internet from Models? Model intercommunication Business process focus Crowd-sourcing to analyze, design and validate

User-Requirement Registry (URR) Part of GCI –Collect, store, publish user needs Use URR to identify value-adding business processes; with crowd- sourced input and validation Requirements: what to do, who to do it Lexicons, controlled vocabularies; essential variables –Integrated into the GEOSS Semantics Registry Connect Earth observations to societal benefits using value chains Analysis goals: gaps; prioritization of users, data & processes; relevance of data Business processes in URR: –Browse URR –Explore risk reduction –Publish business processes and expose to science community for validation

Fei Liu: ESMF and Beyond Library to expose fortran, c, python models –85 components, 12 major modeling systems, 700k SLOC Started in 2002 Superstructure for assembling geophysical components and app’s National Unified Operational Prediction Capability (NUOPC) layer between superstructure & infrastructure –Aggregate ESMF functions Standard methods: initialize, run, finalize Data as Fields (grids), rectangular & unstructured Parallel regridding, many options, offline or during model run

ESMF Metadata Common Information Model (CIM) –XML for exchange of model descriptions, used in CMIP5 Common Modeling Architecture (CMA) –NUOPC Layer encodes elements of CMA for ESMF NUOPC for creating managed multi-model ensemble systems –Models connected via connectors to a central mediator that performs merges and more complex operations –Supports many kinds of model-to-model associations

ESMF Python Speeds up regridding Enables CSDMS integration CUPID: IDE for model devel & modeler trainer Enables users to change model parameters with less effort than initial development

Web Services Pilot: Climate-Hydro Coupling Support distributed, heterogeneous service networks for prediction –SWAT –OpenMI –CAM, Community Atmosphere Model

Roger Moore: Vision for Integrated Modeling Time is as important as space Natural events & “black swans” difficult to model –Deep Water Horizon –Volcanic ash –Climate, energy, water, health issues OpenMI –Descriptive, configurative model framework –Space/time resolution adaptation –OpenMI 2.0 written to OGC format; OAB approved for member comment (2013)

Integrated Environmental Modeling More emphasis on ‘integrated modeling’ than ‘environmental’ domain Facilitate & deliver research results Assist decision makers Engine for innovation Depends on small set of standards –Model component descriptions –Interface definitions –Semantics, especially variables Depends on trust in framework by users and public Barriers to progress: awareness, confidence, availability, skill base, little R&D program, little uptake among target groups Need a committed group to drive IM and build bridges –Business plan, research, dissemination, promotion, education

Mattia Santoro: Business Process Broker User designs abstract BP  compiled  execute  output returned to user Several BP process editors available Several frameworks for BP workflow execution Gap between Abstract BP design and Exec BP process BP Representation: need standards for ABP, EBP Web distributable Intermediation services: Brokers for discovery, access, semantics Provides interop arrangements for ABP  EBP Phases: –Read & pre-process ABP –Publish and submit EBP Support for more WF engines Support for more BP methods

Model Web - Discussion Q: Not much emphasis on products, mostly processes. What are the products? A: We’re talking about enabling platforms for products here; ways of connecting to users, understanding their needs. A: We need to make easier to exchange information between models. But need to understand how the models work. Q: Don’t want to know how they work; just want an answer. A: There are some products available for download; need to try them out. How can we change our perspective from looking for data to looking for ways to combine? A: CSDMS workshop: more about framework for users to ask questions. Impact assessment is difficult.

Model Web Discussion - 2 Q: How can you convey to a user what you are generating? What the semantics are for, eg, a flood map. People don’t care about processes, but about products. A: Need to consider: who is the user? It’s not the funding agency. Initial user is the model creation community; their users are the analysts. We’re not at stage of delivering final tools. A: The pieces developed so far are products, that can be assembled to address problem solving. Q: Technology is not “Product” A: Need a social function, for identifying the tools to combine A: You can only develop products for specific users as you understand what they need A: Liping Di describes “Virtual Product” concept; expert develops geoprocessing model, registers as a virtual product

Model Web Discussion - 3 Q: Still making a mistake confusing geoprocessing with “product” Q: Reflecting on sensor web, I still can’t discover all sensors. There are so many aspects of models, can’t just generate a model without effort. Do you intend to address specific aspects of models and push them forward, or try to make small progress on everything? A: Need to get a committed community to work on this. Need to get people to understand time scale needed to work on this. A: Need to think outside the box, not continue incrementally with what we know. Develop concepts and see how to implement them. Q: What are the steps needed? A: Have seen today most of the components needed. ESMF, OpenMI can be put to use. GCI, DAB, URR are coming along. Start with a few steps. Is a product a dataset? Is it a method? Let’s extend the concept of products. Are they useful for someone, even if not everyone? How can we engage users better?

Model Web Discussion – other comments No discussion of specific products, e.g, flood map. Workshop has been about the tools to create future products Missing the information viewpoint. Emphasis on services. Is it possible to discuss specific products in a common architecture forum?