ICALEPCS 2005 10/13/2005 M. Greenwald Visions for Data Management and Remote Collaboration on ITER M. Greenwald, D. Schissel, J. Burruss, T. Fredian, J.

Slides:



Advertisements
Similar presentations
2 Introduction A central issue in supporting interoperability is achieving type compatibility. Type compatibility allows (a) entities developed by various.
Advertisements

Ninth Lecture Hour 8:30 – 9:20 pm, Thursday, September 13
ASCR Data Science Centers Infrastructure Demonstration S. Canon, N. Desai, M. Ernst, K. Kleese-Van Dam, G. Shipman, B. Tierney.
Building an Operational Enterprise Architecture and Service Oriented Architecture Best Practices Presented by: Ajay Budhraja Copyright 2006 Ajay Budhraja,
MDSplus Tom Fredian MIT Plasma Science and Fusion Center.
SWIM WEB PORTAL by Dipti Aswath SWIM Meeting ORNL Oct 15-17, 2007.
1 Software & Grid Middleware for Tier 2 Centers Rob Gardner Indiana University DOE/NSF Review of U.S. ATLAS and CMS Computing Projects Brookhaven National.
Building Enterprise Applications Using Visual Studio ®.NET Enterprise Architect.
Network Management Overview IACT 918 July 2004 Gene Awyzio SITACS University of Wollongong.
Enterprise Search With SharePoint Portal Server V2 Steve Tullis, Program Manager, Business Portal Group 3/5/2003.
Software Engineering Module 1 -Components Teaching unit 3 – Advanced development Ernesto Damiani Free University of Bozen - Bolzano Lesson 2 – Components.
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
Knowledge Portals and Knowledge Management Tools
Course Instructor: Aisha Azeem
Optimizing Business Operations Business Priorities Presentation.
V. Chandrasekar (CSU), Mike Daniels (NCAR), Sara Graves (UAH), Branko Kerkez (Michigan), Frank Vernon (USCD) Integrating Real-time Data into the EarthCube.
The Design Discipline.
Database System Development Lifecycle © Pearson Education Limited 1995, 2005.
Ihr Logo Data Explorer - A data profiling tool. Your Logo Agenda  Introduction  Existing System  Limitations of Existing System  Proposed Solution.
Framework for Automated Builds Natalia Ratnikova CHEP’03.
Research & Development Roadmap 1. Outline A New Communication Framework Giving Bro Control over the Network Security Monitoring for Industrial Control.
Nurjana Technologies Company Presentation. Nurjana Technologies (NT) is a small business enterprise founded in 2012 and operating in Aerospace and Defence.
1 Dr. Markus Hillenbrand, ICSY Lab, University of Kaiserslautern, Germany A Generic Database Web Service for the Venice Service Grid Michael Koch, Markus.
Rational Unified Process Fundamentals Module 4: Disciplines II.
AL-MAAREFA COLLEGE FOR SCIENCE AND TECHNOLOGY INFO 232: DATABASE SYSTEMS CHAPTER 1 DATABASE SYSTEMS (Cont’d) Instructor Ms. Arwa Binsaleh.
Digital Object Architecture
Microsoft Active Directory(AD) A presentation by Robert, Jasmine, Val and Scott IMT546 December 11, 2004.
1 ISA&D7‏/8‏/ ISA&D7‏/8‏/2013 Systems Development Life Cycle Phases and Activities in the SDLC Variations of the SDLC models.
DISTRIBUTED COMPUTING
1st Workshop on Intelligent and Knowledge oriented Technologies Universal Semantic Knowledge Middleware Marek Paralič,
Database structure for the European Integrated Tokamak Modelling Task Force F. Imbeaux On behalf of the Data Coordination Project.
EGEE is a project funded by the European Union under contract IST Testing processes Leanne Guy Testing activity manager JRA1 All hands meeting,
A framework to support collaborative Velo: Knowledge Management for Collaborative (Science | Biology) Projects A framework to support collaborative 1.
What is Cyberinfrastructure? Russ Hobby, Internet2 Clemson University CI Days 20 May 2008.
CSE 219 Computer Science III Program Design Principles.
OOI CI LCA REVIEW August 2010 Ocean Observatories Initiative OOI Cyberinfrastructure Architecture Overview Michael Meisinger Life Cycle Architecture Review.
Project 2003 Presentation Ben Howard 15 th July 2003.
Chapter © 2012 Pearson Education, Inc. Publishing as Prentice Hall.
© 2012 xtUML.org Bill Chown – Mentor Graphics Model Driven Engineering.
August 2003 At A Glance VMOC-CE is an application framework that facilitates real- time, remote cooperative work among geographically dispersed mission.
The european ITM Task Force data structure F. Imbeaux.
1 Geospatial and Business Intelligence Jean-Sébastien Turcotte Executive VP San Francisco - April 2007 Streamlining web mapping applications.
Chapter 10 Analysis and Design Discipline. 2 Purpose The purpose is to translate the requirements into a specification that describes how to implement.
Systems Analysis and Design in a Changing World, Fourth Edition
1 Computing Challenges for the Square Kilometre Array Mathai Joseph & Harrick Vin Tata Research Development & Design Centre Pune, India CHEP Mumbai 16.
Framework for MDO Studies Amitay Isaacs Center for Aerospace System Design and Engineering IIT Bombay.
NA-MIC National Alliance for Medical Image Computing UCSD: Engineering Core 2 Portal and Grid Infrastructure.
Presented by Scientific Annotation Middleware Software infrastructure to support rich scientific records and the processes that produce them Jens Schwidder.
Group 3: Architectural Design for Enhancing Programmability Dean Tullsen, Josep Torrellas, Luis Ceze, Mark Hill, Onur Mutlu, Sampath Kannan, Sarita Adve,
ICALEPCS /13/2005 M. Greenwald Visions for Data Management and Remote Collaboration on ITER M. Greenwald, D. Schissel, J. Burruss, T. Fredian, J.
March 2004 At A Glance NASA’s GSFC GMSEC architecture provides a scalable, extensible ground and flight system approach for future missions. Benefits Simplifies.
INTRODUCTION TO DBS Database: a collection of data describing the activities of one or more related organizations DBMS: software designed to assist in.
GRID Overview Internet2 Member Meeting Spring 2003 Sandra Redman Information Technology and Systems Center and Information Technology Research Center National.
Presented by Jens Schwidder Tara D. Gibson James D. Myers Computing & Computational Sciences Directorate Oak Ridge National Laboratory Scientific Annotation.
August 2003 At A Glance The IRC is a platform independent, extensible, and adaptive framework that provides robust, interactive, and distributed control.
March 2004 At A Glance The AutoFDS provides a web- based interface to acquire, generate, and distribute products, using the GMSEC Reference Architecture.
MIT Lincoln Laboratory Dynamic Declarative Networking Exploiting Declarative Knowledge To Enable Energy Efficient Collaborative Sensing Daniel J. Van Hook.
Cyberinfrastructure Overview of Demos Townsville, AU 28 – 31 March 2006 CREON/GLEON.
The EPIKH Project (Exchange Programme to advance e-Infrastructure Know-How) gLite Grid Introduction Salma Saber Electronic.
Data Catalog Project A Browsable, Searchable, Metadata System
Chapter 6 Database Design
Distributed System Concepts and Architectures
Enabling Collaboration with IT
MANAGING DATA RESOURCES
FDA Objectives and Implementation Planning
Systems Engineering for Mission-Driven Modeling
DAT381 Team Development with SQL Server 2005
PLANNING A SECURE BASELINE INSTALLATION
敦群數位科技有限公司(vanGene Digital Inc.) 游家德(Jade Yu.)
ONAP Architecture Principle Review
Presentation transcript:

ICALEPCS /13/2005 M. Greenwald Visions for Data Management and Remote Collaboration on ITER M. Greenwald, D. Schissel, J. Burruss, T. Fredian, J. Lister, J. Stillerman MIT, GA, CRPP Presented by Martin Greenwald MIT – Plasma Science & Fusion Center ICALEPCS 2005, Geneva

ICALEPCS /13/2005 M. Greenwald ITER is the Next Big Thing in Magnetic Fusion Research World’s first burning plasma experiment To be built and operated as an international collaboration Site: Cadarache, France Europe, USA, Japan, Russia, Korea, China Construction ~10 years, ~10B$

ICALEPCS /13/2005 M. Greenwald What Challenges Will ITER Present? Fusion experiments require extensive data visualization and analysis in support of between-shot decision making. –“Shots” are the basic unit of the experiments. For ITER, shots are: à~400 seconds each, perhaps 2,000 per year for 15 years –Average cost per shot is very high (order $1M) –Most data are long time series (or multi-dimensional arrays) Today, teams of ~ work together closely during operation. Real-time remote participation is standard operating procedure.

ICALEPCS /13/2005 M. Greenwald Challenges: Experimental Fusion Science is a Demanding Real-Time Activity Run-time goals: –Optimize fusion performance –Ensure plasmas are fully documented before changing conditions Drives need to assimilate and assess large quantity of data between shots.

ICALEPCS /13/2005 M. Greenwald Challenge: Long Pulse Length Concurrent reading, writing; larger data sets Greater challenge – integration across time scales Data will span range > 10 9 in significant time scales Will require efficient tools –To browse very long records –To locate and describe specific events or intervals Challenge: Long Life of Project 10 years construction; 15+ years operation Systems must adapt to decades of information technology evolution & revolution Backward compatibility must be maintained

ICALEPCS /13/2005 M. Greenwald Challenge: Long Pulse Length Concurrent reading, writing; larger data sets Greater challenge – integration across time scales Data will span range > 10 9 in significant time scales Will require efficient tools –To browse very long records –To locate and describe specific events or intervals Challenge: Long Life of Project 10 years construction; 15+ years operation Systems must adapt to decades of information technology evolution & revolution Backward compatibility must be maintained

ICALEPCS /13/2005 M. Greenwald Challenges: International, Remote Participation Scientists will want to participate in “live” experiments from their home institutions dispersed around the world. –View and analyze data –Manage ITER diagnostics –Lead experimental sessions Collaborations span many administrative domains –Resource management –Trouble shooting/end-to-end problem resolution Cyber-security must be maintained, plant security must be inviolable.

ICALEPCS /13/2005 M. Greenwald We Are Beginning the Dialogue About How to Proceed This is not yet an “official” ITER activity What follows is our vision for data management and remote participation systems Opinions expressed here are the authors alone (but based on decades of experience).

ICALEPCS /13/2005 M. Greenwald Strategy: Design, Prototype and Demo With 10 years before first operation, it is too early to choose specific implementations – software or hardware Begin now on enduring features Define requirements, scope of effort, approach Decide on general principles and features of architecture Within 2 years: start on prototypes:  Part of conceptual design Within 4 years: demonstrate: Test, especially on current facilities Simulation codes could provide testbed for long-pulse features In 6 years: proven implementations expanded and elaborated to meet requirements

ICALEPCS /13/2005 M. Greenwald Strategy: Design, Prototype and Demo With 10 years before first operation, it is too early to choose specific implementations – software or hardware Begin now on enduring features –Define requirements, scope of effort, approach –Decide on general principles and features of architecture Within 2 years: start on prototypes:  Part of conceptual design Within 4 years: demonstrate: Test, especially on current facilities Simulation codes could provide testbed for long-pulse features In 6 years: proven implementations expanded and elaborated to meet requirements

ICALEPCS /13/2005 M. Greenwald Strategy: Design, Prototype and Demo With 10 years before first operation, it is too early to choose specific implementations – software or hardware Begin now on enduring features –Define requirements, scope of effort, approach –Decide on general principles and features of architecture Within 2 years: start on prototypes:  Part of conceptual design Within 4 years: demonstrate: Test, especially on current facilities Simulation codes could provide testbed for long-pulse features In 6 years: proven implementations expanded and elaborated to meet requirements

ICALEPCS /13/2005 M. Greenwald Strategy: Design, Prototype and Demo With 10 years before first operation, it is too early to choose specific implementations – software or hardware Begin now on enduring features –Define requirements, scope of effort, approach –Decide on general principles and features of architecture Within 2 years: start on prototypes:  Part of conceptual design Within 4 years: demonstrate: –Test, especially on current facilities –Simulation codes could provide testbed for long-pulse features In 6 years: proven implementations expanded and elaborated to meet requirements

ICALEPCS /13/2005 M. Greenwald Strategy: Design, Prototype and Demo With 10 years before first operation, it is too early to choose specific implementations – software or hardware Begin now on enduring features –Define requirements, scope of effort, approach –Decide on general principles and features of architecture Within 2 years: start on prototypes:  Part of conceptual design Within 4 years: demonstrate: –Test, especially on current facilities –Simulation codes could provide testbed for long-pulse features In 6 years: proven implementations expanded and elaborated to meet requirements

ICALEPCS /13/2005 M. Greenwald General Features Extensible, flexible, scalable –We won’t be able to predict all future needs –Capable of continuous and incremental improvement –Requires robust underlying abstraction Data Accessible from wide range of languages, software frameworks and hardware platforms Built-in security –Must protect plant without endangering science mission –Employ best features of identity-based, application and perimeter security models –Strong authentication mechanisms, single sign-on –Distributed authorization and resource management

ICALEPCS /13/2005 M. Greenwald Proposed Top Level Data Architecture Data Acquisition Control Service Oriented API Analysis Applications Visualization Applications Relational Database Main Repository Data Acquisition Systems Contains data searchable by their contents Contains large multi- dimensional data arrays.

ICALEPCS /13/2005 M. Greenwald Data System – Contents & Structure Coherent, complete, integrated, self-descriptive view of all data visible through simple interfaces. –All  Raw, processed, analyzed data, configuration, geometry calibrations, data acquisition setup, code parameters, labels, comments… –No data in applications or private files Metadata stored for each data element Logical relationships and associations among data elements are made explicit by structure (probably multiple hierarchies). Data structures can be traversed independent of reading data. Capable data directories (10 5 – 10 6 named items)

ICALEPCS /13/2005 M. Greenwald Data System - Abstractions Service oriented –Loosely coupled applications, running on distributed servers –Interfaces simple and generic, implementation details hidden àTransparency and ease-of-use are crucial àApplications specify what is to be done, not how –Data structures shared –Service discovery supported Data driven –All parameters in database not imbedded in applications –Data structure, relations, associations are data themselves àProcessing can be sensitive to data relationships and to position of data within structure –Data acquisition and processing “tree” maintained as data

ICALEPCS /13/2005 M. Greenwald Data System - Abstractions Service oriented –Loosely coupled applications, running on distributed servers –Interfaces simple and generic, implementation details hidden àTransparency and ease-of-use are crucial àApplications specify what is to be done, not how –Data structures shared –Service discovery supported Data driven –All parameters in database, not imbedded in applications –Data structure, relations, associations are data themselves àProcessing can be sensitive to data relationships and to position of data within structure –Data acquisition and processing “tree” maintained as data

ICALEPCS /13/2005 M. Greenwald Data System - Higher Level Organization All part of database All indexed into main data repository High level physics analysis –Scalar and profile databases Event identification, logging & tracking Integrated and shared workspaces –Electronic logbook –Summaries and status àRuns àTask groups àCampaigns –Presentations & publications

ICALEPCS /13/2005 M. Greenwald Remote Participation Creating an Environment That Is Equally Productive for Local and Remote Researchers Transparent remote access to data –Secure and timely Real-time info –Machine status –Shot cycle –Data acquisition and analysis monitoring –Announcements Shared applications Provision for ad hoc interpersonal communications Provision for structured communications

ICALEPCS /13/2005 M. Greenwald Remote is Easy, Distributed is Hard Informal interactions in the control room are a crucial part of the research We must extend this into remote and distributed operations Fully engaging remote participants is challenging (Fortunately we have already substantial experience)

ICALEPCS /13/2005 M. Greenwald Remote Participation Ad Hoc Communications Exploit convergence of telecom and internet technologies (eg. SIP) Deploy integrated communications –Voice –Video –Messaging – –Data streaming Advanced directory services –Identification, location, scheduling –“Presence” –Support for “roles”

ICALEPCS /13/2005 M. Greenwald Summary While ITER operation is many years in the future, work on the systems for data management and remote participation should begin now We Propose: All data into a single, coherent, self-descriptive structure Service-oriented access Data driven applications Remote participation fully supported –Transparent, secure, timely remote data access –Shared applications –Capable tools for ad hoc interpersonal communications