Hydrologic Models and Simulations within the HydroShare Online Community

Anthony M. CastronovaMohamed M. Morsy

Brian MilesJonathan L. Goodall

Brief Introduction to HydroShare

8/6/2015 2015 CUAHSI Conference on HydroInformatics 2

Collaborative environment for sharing data, models, and code.

Data are represented as web resources that contain metadata (e.g. Dublin Core)

Relationships can exist between resources (one-to-many, many-to-many)

Resources can be accessed via RESTful API and therefore they can be used with applications outside of HydroShare

Brief Introduction to HydroShare Public and Private resources Filtering by keyword Different types of resources that provide varying functionality aimed at

specific types of data. Supported data types are constantly growing.

8/6/2015 2015 CUAHSI Conference on HydroInformatics 3

Framework Architecture

Django Front-end website Resource creation, exploration Data sharing

iRODS Resource storage Distributed file system

HydroShare Apps Actions that operate on resources Community driven app

development Powered by the Tethys framework

8/6/2015 2015 CUAHSI Conference on HydroInformatics 4

Vision for Modeling

Engage the community to assemble a collection of model representations.

Provide the ability to discover models that are being used by colleagues and other research teams

Enable scientists and students to engage other researchers

Provide public/private space for archiving models and simulations

Central location for data management

Model execution and integration with 3rdparty software

8/6/2015 2015 CUAHSI Conference on HydroInformatics 5

8/6/2015 2015 CUAHSI Conference on HydroInformatics 6

This image cannot currently be displayed.

Model Package

8/6/2015 2015 CUAHSI Conference on HydroInformatics 7

Model Package

Execute SimulationCreate New Resources with Output Results

8/6/2015 2015 CUAHSI Conference on HydroInformatics 8

Apps.HydroShare.org

import numpy

array = numpy.zeros((100,.

.

.

.

REST API+

Python Library

Model Packages

Composite resource

Model Program Defines the computational engine and

software metadata

Model Instance Defines the simulation including input

and output data

A one-to-many relationship exists between Model Programs and Model Instance resources

8/6/2015 2015 CUAHSI Conference on HydroInformatics 9

Model Program

Model Instance

Inputs

Outputs

Derived From

Part

Of

Executed By

Generated By

Model Program Resource

Uses HS science metadatacreator, contributor, date, org...

Model program specific terms expands Morsy et al. (2014) software and requirements

Expand HS science metadata definition when necessary

does not describe every possible hydro-related entity

8/6/2015 2015 CUAHSI Conference on HydroInformatics 11

Dublin Core Metadata Abstract Authors Contributors Keywords

Resource Specific metadata Version Language OS Source code Documentation

Creates landing page Summarizes metadata Builds HydroShare Citation Downloadable Content Can be linked with other

resources

8/6/2015 2015 CUAHSI Conference on HydroInformatics 12

Model Program Creation

8/6/2015 2015 CUAHSI Conference on HydroInformatics 13

Model Instance

SWAT ModelRHESSys ModelUEB Snow

Model

UNC Purdue USU

Extending Model Instance Types

Specific instance types inherit properties from the generic model instance Extend the core metadata to enhance functionality. (e.g. Execution) This list is growing. However, all models can still be represented using the generic

model instance

Specific Model Instances Specific Model Instances

asynchronous task message queue isolated containers,lightweight virtual machines

Model results / error messages written to HydroShare resources

distributed task queue

8/6/2015 2015 CUAHSI Conference on HydroInformatics 15

Utilizes community built libraries Server-side model execution Input from users via the HydroShare website Model computation occurs on HydroShare hardware and reports results and/or

errors back Upon task completion, new model instance resources are created

Model Execution Architecture

RHESSys Model Execution Provide basic metadata for simulation Model input parameters Interactive status

Viewing RHESSys results

Track simulation runs View simulation results Currently investigating a robust way to

provide this functionality to other models

Summary

A comprehensive metadata definition is used as the foundation onto which models are represented within the HydroShare infrastructure.

Lots of work on representing Model Programs and Model Instances, as well as 3rdparty software integration and model execution

Exploring various methods of model execution and generating a list of use-cases to demonstrate our modeling functionality

Ultimately our goal is to make useful research tools that others can use, implement, and maintain.

8/6/2015 2015 CUAHSI Conference on HydroInformatics 18

Moving Forward Closer look at resource/content ownership

What if you aren't the author of a model, but you are the resource creator?

Resource metadata and content accuracy Engage model developers directly. We need a formal method for users request or initiate contact with model developers.

Ensure accurate citations Automatic citation generation may need to be overridden.

Incentivize modelers Feedback about who is using there models Credit for their hard work via accurate citations, analytics, etc.

Engage the modeling community Encourage use of the HydroShare modeling tools Build use-cases for future development efforts.

8/6/2015 2015 CUAHSI Conference on HydroInformatics 19

Hydrologic Models and Simulations within the HydroShare Online CommunityBrief Introduction to HydroShareBrief Introduction to HydroShareFramework ArchitectureVision for ModelingSlide Number 6Slide Number 7Slide Number 8Model PackagesSlide Number 10Slide Number 11Slide Number 12Slide Number 13Slide Number 14Slide Number 15Slide Number 16Slide Number 17Summary Moving Forward