Cyberinfrastructure Overview of Demos

1. Cyberinfrastructure Overview of Demos Townsville, AU 28 – 31 March 2006 CREON/GLEON

2. CI Overview of Demos • Goals: • Provide an integrative overview of GLEON cyberinfrastructure • Provide a context for the demos and discussions • Questions: • What is the vision? • What activities are underway? • What components exist? • What are next steps?

3. Vision • International collaborative network for sensor-based research into lake ecology • End-to-end integrated CI solution for data collection, analysis, and collaboration • Site level • Data acquisition, instrument deployment and management • Data management, curation, and publication • Site-level analysis and visualization • Network level • Resource discovery, access and utilization • Cross-site analysis and visualization • Collaboration, sharing of techniques, experiences, and best practices • Priority #1: timely (near-real-time) data sharing

4. High-level Architectural Design Requirements • Accommodate autonomous administrative domains • Heterogeneous technology bases • Local control of resources • Support near-real-time data publication from sensors • Extensible to new lakes and new partners • Support integration of new tools and applications • Adapt community standards where possible • Usable and efficient • System must provide an intuitive user interface into network resources (data and tools) • System must be provide scalable compute/data resources • Secure

5. Levels and Responsibilities in a Global Network • Site: site-specific science • Manage, maintain, and control site resources; curate and publish data • Provide services to acquire, manage, query, and analyze site data; create interfaces for network • Develop policies of data and resource sharing • Network: cross-site science • Establish standards and interfaces between sites • Agree on data types, semantics, units, metadata • Provide services to discover, query, and analyze data from multiple sites • Provide collaboration tools • Develop policies of cross-site data and resource sharing

6. Common Interface Layer Data Management Data Analysis and Modeling Data Acquisition Comm. & Ctl. Web Services Analytical Web Services Data-related Web Services Sensor Net Middleware Database Models Models Models Data Logger QA/QC Agent Sensor Sensor Sensor . . . . . . GLEON Site Architecture The components and the relationships are only tentative to start the discussion.

7. Common Interface Layer Common Interface Layer Common Interface Layer Data Management Data Management Data Management Data Analysis and Modeling Data Analysis and Modeling Data Analysis and Modeling Data Acquisition Data Acquisition Data Acquisition Comm. & Ctl. Web Services Comm. & Ctl. Web Services Comm. & Ctl. Web Services Analytical Web Services Analytical Web Services Analytical Web Services Data-related Web Services Data-related Web Services Data-related Web Services Sensor Net Middleware Sensor Net Middleware Sensor Net Middleware Database Database Database Models Models Models Models Models Models Models Models Models Data Logger Data Logger Data Logger QA/QC Agent QA/QC Agent QA/QC Agent Sensor Sensor Sensor Sensor Sensor Sensor Sensor Sensor Sensor . . . . . . . . . . . . . . . . . . GLEON Network Architecture Cyberdashboard Resource discovery and utilization Collaboration Desktop & Mobile Users Lake Site 2 Lake Site 1 Lake Site 3 Note that each site implements the Interface Layer, but the actual site architectures are independent and site-specific.

8. Standardization Issues • Agreeing on common CI standards will facilitate network integration and operations: • Database schemas • Metadata specifications • Model interfaces • Query interfaces • Security protocols • Cyberdashboard/portal framework • Policies for resource sharing and utilization

9. Balance Implementation and Standards Efforts • Grass-roots efforts • Reflect funding realities (no one site or funding agency is going to fund an international network) • Distributes Labor • Brings in more expertise, resources • Nimble (we can respond more quickly than larger top down organizations, e.g. PRAGMA) • Challenges of the balance • Standardizing will allow for easier extensibility of network to new sites • Standardizing creates delay based on discussion but will save development time • Standardizing requires coordination and policy considerations

10. Design Issues • Science • Is there one (or a few) question(s) we will all agree to support? • Priority on Features (from demos) • What would be the most useful to you? • What would be most useful for network science? • Degree of standardization possible (how far can we reduce the degrees of freedom?) • Who has an existing system? • What is minimal agreed upon “configuration”? • What variables will we all agree to capture? • If you don’t have a system, would you be willing to adopt one if provided (open source db, schema installed)? • Would you be willing to purchase common equipment (to some level)? • Distribution of workload • Are there volunteers to work on some of the outcomes? • Common Framework • Is there a subset of people to work in this?

11. Demonstrations • Cyberdashboard for Instrument Management • Data Integration and Transport for Distributed Sensor Networks • dbBADGER: A data access, post processing, and forwarding tool designed for sensor networks • Data Registration, Query and Analysis in GLEON • Sensor Calibration Automation Demonstration • Efficient 3-Dimensional Incompressible Fluid Flow Solvers for Grid Testbed • A System for On-Demand Historical and Predictive Lake Circulation Modeling • Sensor Network Systems with AmbientRT • AquaNode: A Solution for Underwater Wireless Communication • Prototype GBR Sensing Environment

12. Components of end-to-end SystemDemonstrations for Site and Network Level Science Site Network Acquisition Management Analysis Collaboration -------------------------------------------------------------------------------------------------------------- 1. X X X X 2. X X X X X 3. X X 4. X X X X X 5. X X 6. X X 7. X X 8. X X 9. X X 10. X X

13. Network Services • Resource Registration • Data (products and streams) • Analysis tools • Sensors and instruments • Storage • Computational Resources • Resource Discovery • Locating relevant resources within the distributed community • Resource Utilization • Analysis • Modeling • Instrument control • Decision support • Collaboration Tools • Site information (characteristics, science, infrastructure) • Knowledge base of best practices and expertise • Real-time interactions (chat, vtc, message boards, skype…)

14. Site: Administrative Domain Example: Lake, Coral Reef Equipment: Data capture: Sensor, Data logger Data communication: Wireless or wired network (sensor to lab) Data storage and management system Data analysis equipment Interface to the outside (network connection) Responsibilities Data capture, QA/QC, curation Equipment management and maintenance Policies Data access and sharing Equipment access and control Network: Federation of Sites Example: GLEON,CREON Equipment Data integration and query machines connected to internet Data analysis computers and internet connection Responsibilities Create a framework to share data Provide equipment for network level data integration, query, and some analysis Seek connections to other infrastructure for larger calculations Establish standards Build collaborations, share expertise, assist sites Policies Data sharing Tool/application sharing Standards Conceptual Framework