NEESgrid A CyberInfrastructure for Earthquake Engineering Simulation

Transcription

1 NEESgrid A CyberInfrastructure for Earthquake Engineering Simulation (NEESgrid Data/MetaData Efforts and Issues) Professor of Civil and Environmental Engineering (Structural Engineering and Engineering Informatics) February 28,2005 NSF EXCITED Workshop (Exchanging CyberInfrastructure Themes in Engineering Design)

2 NEESgrid System Integration Development (NEESgrid - Bill Spencer, Jr. of UIUC PI) (Consortium effort NCSA, ANL, USC s ISI, U. Michigan, UC Berkeley, Stanford, and others ) NEESgrid s Data and Metadata Efforts (Data and MetaData Working Group) More on Data Issues Current Status Outline of Presentation

3 George E. Brown Jr. Network for Earthquake Engineering Simulation (NEES) Geotechnical Centrifuge University of California, Davis $4,614,294 Fast Hybrid Testing Laboratory University of Colorado, Boulder $1,983,553 Permanently Instrumented Field Sites Brigham Young University $1,944,423 Tsunami Wave Basin Oregon State University $4,775,832 Three (two relocatable) Shake Tables University of Nevada, Reno $4,398,450 Consortium Development Consortium of Universities for Research in Earthquake Engineering $1,999,907 Reconfigurable Reaction Wall University of California, Berkeley $4,268,323 Multi-Axial Subassemblage Testing System University of Minnesota, Twin Cities $6,472,049 System Integration University of Illinois at Urbana-Champaign $10,000,000 Large Uniaxial Shake Table University of California, San Diego $5,890,000 Modular Simulation Laboratory University of Illinois at Urbana-Champaign $2,958,011 Dual (relocatable) Shake Tables and High Performance Actuators State University of New York, University at Buffalo $6,160,785 $4,379,865 Geotechnical Centrifuge Rensselaer Polytechnic Institute $2,380,579 Lifeline Testing Facility Cornell University $2,072,716 Multi-directional Testing Facility Lehigh University $2,593,317 Field Testing Equipment University of Texas, Austin $2,937,036 Field Testing Equipment University of California, Los Angeles $2,652,761 NEESit Operations SDSC, University of California, - San Diego $40,000,000

4 Remote Users (Faculty, Students, Practitioners) Instrumented Structures and Sites NEES Resources Simulation Tools Repository Laboratory Equipment Curated Data Repository Global Connections (FY 2005 FY 2014) Enabling collaboration (laboratory experiments, field tests, simulations) Laboratory Equipment High- Performance Network(s) Enabling data sharing, archiving and access by researchers (and public) Remote Users: (K-12 Faculty and Students) Field Equipment Leading Edge Computation

5

6 Vision of NEES (Collaboratory( Collaboratory)

7 NEESgrid!- CyberInfrastructure To connect and facilitate experimentation/simulation (virtual collaboratory) in earthquake engineering for US and the world Tele-Control Services and APIs Tele-Observation and Data Visualization E-Notebook Streaming data services DAQ and related services Data and Metadata Services Remote Collaboration and Visualization tools and services Core Grid Services, deployment efforts, packaging Simulation Component

8 Data/Metadata Working Group Member Objective: To define a common approach and tools to enhance the sharing, access and utilization of the NEESgrid data repository Jean-Pierre Bardet University of Southern California Jennifer Swift University of Southern California Andrei Reinhorn State University of New York, Buffalo (Data Sharing and Archiving Committee, DSAC) Ken Ferschweiler Northwest Alliance for Computational Science and Engineering, Oregon State Univ. Lelli Van Den Einde University of California at San Diego Gokhan Pekcan University of Nevada, Reno (Coordinator of the Task Group) Hank Ratzesberger University of California, Santa Barbara Chuck Severance University of Michigan Bill Spencer University of Illinois, Urbana-Champaign (PI of NEES s System Integration Project) Jim Eng University of Michigan Jun Peng

9 NEESgrid Data Core Elements Data Acquisition NEESpop Data/MD Ingest Tools API Grid and Web Services Data Teamlets API Local Repository Workstation NEESdata Data tools Data viewers Data Teamlets API Central Repository

10 Overall Data Modeling Efforts NEES Site Specifications Database Site A Site B Site C Equipment People Equipment People Project Description Experiments Trials Experiments Trials Domain Specific models Tsnumai Specimen Shake Table Specimen Geotech Specimen Centrifuge Specimen Common Elements Units Sensors Descriptions Data / Observations Data Data Data

11 NEESgrid Experiment Data Flow SiteSpecific ProjectRelated Data Model ExperimentalSetup Project Browser Data Ingestion Experiment Control ExperimentalElement DataElement NEESGrid Data Repository Data Turbine C D DAQ Stored Viewer Streaming Viewer DAQ Disk

12 Data Model Development Effort by Stanford Team (Shake Table/Large Scale Structural Tests December 1, 2003) A knowledge engineering approach: Evaluate existing data model representations and tools Representation: E-R diagram, UML, NEESML, RDF, OWL Tools: Protégé 2000, Rational Rose, Dezign Evaluate existing data models for usability Project Description: OrSt Model, Science Ontology Sensors/Common Elements: Berkeley CUREE/Kajima, SensorML Specimen/Structure Models: CIS/2, IFCs, SAC Data Others: COSMOS Visit, interview and discuss with experimental site personnel Conference calls, UN Reno, UC Berkeley, UIUC, U Minnesota Develop prototype models for feedback Validate and test data models with saved experimental data

13 Observations Pre-experiment and post-experiment data could be as valuable as the actual experiment itself Computer simulations play a significant role towards the design of an experiment as well as for post-event investigations Simulations Simulations Simulations Pre-Experiment Stage Experiment Stage Post-Experiment Stage Process: Activities Specimen Units of Measure Data Model Instrumentation

14 Overview of Reference Data Model Shake table and large scale structural tests Simple and extensible, minimum burden to researchers But sufficiently representative for earthquake engineering experimentations Data model representations: Object Model Has only 20+ main classes Modeling tool: Protégé 2000 Backend storage: OWL (Web Ontology Language) Relational Model Has only 20+ tables Modeling tool: Dezign Backend storage: Relational database such as MySQL

15 Prototype Class Relationship SiteInformation RolePerson Organization Site Person Project ApparatusSetup Apparatus Publication Task InfrastructureSetup PrimaryEquipment Activity SepcimenSetup Specimen EventGroup 1 SensorSetup Sensor DAQSystem WaveFormSetup DAQSetup DAQChannel DAQCable WaveForm Event SoftwareSetup Software File OutputData SetupFile DataElement

16 Protégé Interface: Object Model Only 20+ main classes

17 OWL Representation

18 Relational Data Representation

19 Modeling of Specimen and Setups Universal modeling of specimen for all experiments is very difficult if not impossible Goal is to provide ways to archive the data and information on the project and the experiment Desirable formats and features: CAD drawings; sketched drawings and notes; photos; narrative description; electronic notebook; linkage of drawings, sensor locations to data, etc..

20 Modeling DAQ (data and setup) Sensor DAQCable DAQSystem owner manufacturer serialnumber otherinfo PC and/or External A/D owner manufacturer serialnumber otherinfo sensorid type calibrationinfo lastcalibrationdate outputquantity minrange maxrange owner manufacturer serialnumber otherinfo cableid length connectortype DAQChannel owner manufacturer serialnumber otherinfo channelid filter samplingrate gain offset excitationvoltage unit Sampling

21 Project Data Browsing

22 Project Data Browsing

23 Project Data Browsing

24 Project Data Browsing

25 Data Services : Report Generator Assistance ReportGen.java Engineering Report Generator Java Servlet Applications DisplayNEES.java OWLDataRetrieval.java DBDataRetrieval.java Retrieve Related Data: e.g. Data Related to Instrumentation OWLMapping.java DBMapping.java OWLAccess.java DBAccess.java Present Common Interface for Data Access: e.g. Access an Object by its ID Jena JDBC Standard Library for Data Access XML-Based Documents OWL (Web Ontology Language) Relational Database: MySQL Structured Data Stroage Based on Data Model

26 Report Structure & Corresponding Functions getsummary() getscope() getsetupoverview() getinfrastructure() getspecimen() getloading() getinstrumentation() getprocedure() getschedule() getimplementation() getresults() getdataprocessing() getpredictions() getdiscussions() Re: Prof. Andrei SUNY-Buffalo

27 Data Model & Corresponding Functions SiteInformation getsummary() RolePerson Person Organization Project Site getinfrastructure() getsetupoverview() getspecimen() Publication getloading() ApparatusSetup Task InfrastructureSetup Activity SepcimenSetup EventGroup 1 SensorSetup Apparatus PrimaryEquipment Specimen DAQSystem Sensor WaveFormSetup DAQSetup DAQChannel DAQCable WaveForm Event SoftwareSetup Software getinstrumentation() File OutputData SetupFile DataElement

28 Front Page to Access MiniMOST Project

29 Retrieve Summary

30 Scope and General Presentation

31 Infrastructure Setup

32 Instrumentation

33 More on Data Issues.. Current Developments and Tools Facilitate experimenters and researchers generating and ingesting data into repository Allow browsing (and limited searching) and retrieving data/information about a project or experiment Support No data generated by NEES would be lost policy But.. A data repository is only as good as what can be done with the data.

34 Data Production Data Life Cycle Data Management Data Consumption For how long? What format? (standardization, usability) Heterogeneous data types (text, CAD, video, streams) Raw, processed, derived, curated data Non-proprietary data format and software (what to archive?) What to preserve? Everything? Selectively? Need: data policies and short/long term plans for the cyberinfrastructure community (not just the cyberinfrastructure but the community it serves!)

35 Consumers for the NEESgrid Data Repository: Experimenters about generating reports, analysis of results Practitioners about specific results for specific experiment on specific component (beam column joint) Researchers about prior works for developing new ideas (new, novel active damping/sensing devices) Colleagues in other fields data interoperability and sharing (IRIS s seismological data sets) Faculty developing teaching materials Students discovering new knowledge, mining archived data K-12 audience about earthquakes and our civil infrastructure systems

36 OAIS (Open Archive Information System) Functional Model Preservation Planning Data Management? Producer Ingest Access Consumer Archival Storage? Administration Current Focus and Deliverables Management NEES Consortium

37 Data Models Experiment Prep Experiment Management Capture Data/Metadata Throughout Data Lifecycle Data Monitoring Data Analysis Data Publishing Data Curation Data Discovery and Reuse

38 What have I learnt about NEESgrid (CI) data issues? The amount of data (in a wide variety of formats) to be generated will be overwhelming standardization is hard but some standardization is necessary Expectations of what data models and repository can support are very high (and may not be easy to deal with in short term) Putting data in a computer (meaningfully) IS NOT an easy problem A lot to be learnt among different disciplines engineering, digital library, digital archive and preservation, library information science, information and communication technologies,. Many related ongoing works: Skyserver, DSPACE, IRIS, GEON, BRIN,..

39 What have I learnt about NEESgrid (CI) issues? Strong leadership and management team (not only technology developers) coordinate activities True collaborative efforts among developers, researchers, disciplines involved Dedication of community participants from the domain of concern Policies and guidelines need to be well defined by the community, implemented and enforced Need to have buy-in by the researchers (or users of the CI) CI is not a pure academic research activity with much at stakes by the community at large

40 Current Status NEES: Officially opened Oct. 1, 2004 and Opening Ceremony at NSF Nov. 15, 2004 NEES Organization: NEESr (Researchers), NEESInc (Management), NEESit (IT operations SDSC) NEESgrid transition from NCSA to SDSC on Oct. 1, 2004 NEESit to release interim version by end of March, 2005 International collaborations/activities related to NEES: KOCEF ($90 million effort in Korea) E-Defense (Japan) NCREE (Taiwan) European groups and others.

41 Rapidly Deployable CI and Data Problem Source: A Proposal on Innovative Use of IT in Post-Disaster Investigation, EERI, Feb 2004

42 Acknowledgments NEES s Data and Metadata Task Group NEES s Data Sharing and Archiving Committee Joy Pauschke of NSF, Bill Spencer of UIUC, Chuck Severance of U. Michigan and Joe Futrelle of UIUC, Gokhan Pekcan of U. Nevada, Reno, Anke Kamrath, Lelli Van Den Einde of SDSC and many others.. Jun Peng, Any opinions expressed in this presentation are those of the presenter and do not necessarily reflect the views of the NEESgrid, NEESit, NEESInc, NSF and his collaborators.

43