Lero© 2012 Modeling the Image-Processing Behavior of the NASA Voyager Mission with ASSL Emil Vassev and Mike Hinchey.

Slides:



Advertisements
Similar presentations
Annual Conference of ITA ACITA 2009 Realising Management and Composition of Self-Managed Cells in Body Area Networks Alberto Schaeffer-Filho, Emil Lupu,
Advertisements

Chapter 19: Network Management Business Data Communications, 5e.
KAIS T The Vision of Autonomic Computing Jeffrey O. Kephart, David M Chess IBM Watson research Center IEEE Computer, Jan 발표자 : 이승학.
Towards Self-Testing in Autonomic Computing Systems Tariq M. King, Djuradj Babich, Jonatan Alava, and Peter J. Clarke Software Testing Research Group Florida.
Some questions o What are the appropriate control philosophies for Complex Manufacturing systems? Why????Holonic Manufacturing system o Is Object -Oriented.
4.1.5 System Management Background What is in System Management Resource control and scheduling Booting, reconfiguration, defining limits for resource.
Yingping Huang and Gregory Madey University of Notre Dame A W S utonomic eb-based imulation Presented by Tariq M. King Published by the IEEE Computer Society.
Object-Oriented Analysis and Design
Improving Software Quality with Generic Autonomics Support Richard Anthony The University of Greenwich.
Blue Bear Systems Research Hardware Architectures for Distributed Agents Dr Simon Willcox 24 th Soar Workshop 9 th – 11 th June 2004 Building 32, Twinwoods.
1 ITC242 – Introduction to Data Communications Week 12 Topic 18 Chapter 19 Network Management.
Improving Robustness in Distributed Systems Jeremy Russell Software Engineering Honours Project.
Ensuring Non-Functional Properties. What Is an NFP?  A software system’s non-functional property (NFP) is a constraint on the manner in which the system.
A Model-Driven Framework for Architectural Evaluation of Mobile Software Systems George Edwards Dr. Nenad Medvidovic Center.
Autonomic Computing Shafay Shamail Malik Jahan Khan.
Architectural Design Principles. Outline  Architectural level of design The design of the system in terms of components and connectors and their arrangements.
Computers: Tools for an Information Age
1 Autonomic Computing An Introduction Guenter Kickinger.
An Approach to Test Autonomic Containers Ronald Stevens (IEEE Computer Society & ACM Student Member) August 1, 2006 REU Sponsored by NSF.
WELCOME. AUTONOMIC COMPUTING PRESENTED BY: NIKHIL P S7 IT ROLL NO: 33.
Designing and implementing of the NQF Tempus Project N° TEMPUS-2008-SE-SMHES ( )
Software Architecture Framework for Ubiquitous Computing Divya ChanneGowda Athrey Joshi.
Automating service management Tiina Niklander Faculty of Science Department of Computer Science In AMICT 2008 Petrozavodsk, May 2008.
Lifecycle Verification of the NASA Ames K9 Rover Executive Dimitra Giannakopoulou Mike Lowry Corina Păsăreanu Rich Washington.
Architecting Web Services Unit – II – PART - III.
Event Management & ITIL V3
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
OPERAS CC : An instance of a Formal Framework for MAS Modelling based on Population P Systems P.Kefalas Dept. of Computer Science CITY COLLEGE Thessaloniki,
Space unit Life in Space.
A Self-Manageable Infrastructure for Supporting Web-based Simulations Yingping Huang Xiaorong Xiang Gregory Madey Computer Science & Engineering University.
Page 1 Reconfigurable Communications Processor Principal Investigator: Chris Papachristou Task Number: NAG Electrical Engineering & Computer Science.
The roots of innovation Future and Emerging Technologies (FET) Future and Emerging Technologies (FET) The roots of innovation Proactive initiative on:
Supporting Self-Adaptation in Multi- Agent Systems.
Issues Autonomic operation (fault tolerance) Minimize interference to applications Hardware support for new operating systems Resource management (global.
1 Qualitative Reasoning of Distributed Object Design Nima Kaveh & Wolfgang Emmerich Software Systems Engineering Dept. Computer Science University College.
1 Computing Challenges for the Square Kilometre Array Mathai Joseph & Harrick Vin Tata Research Development & Design Centre Pune, India CHEP Mumbai 16.
CIS 112 Exam Review. Exam Content 100 questions valued at 1 point each 100 questions valued at 1 point each 100 points total 100 points total 10 each.
MAPLD 2005/254C. Papachristou 1 Reconfigurable and Evolvable Hardware Fabric Chris Papachristou, Frank Wolff Robert Ewing Electrical Engineering & Computer.
Dissecting Self-* Properties Andrew Berns & Sukumar Ghosh University of Iowa.
THE VISION OF AUTONOMIC COMPUTING. WHAT IS AUTONOMIC COMPUTING ? “ Autonomic Computing refers to computing infrastructure that adapts (automatically)
1 Run-Time Software Engineering An approach for Embedded and Ubiquitous Computing Environments Sooyong Park Sogang University South.
Cognitive Radio: Next Generation Communication System
9-Dec Dec-15  INTRODUCTION.  FEATURES OF OOP.  ORGANIZATION OF DATA & FUNCTION IN OOP.  OOP’S DESIGN.
16/11/ Semantic Web Services Language Requirements Presenter: Emilia Cimpian
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
1 Earth Science Technology Office The Earth Science (ES) Vision: An intelligent Web of Sensors IGARSS 2002 Paper 02_06_08:20 Eduardo Torres-Martinez –
Internet of Things. IoT Novel paradigm – Rapidly gaining ground in the wireless scenario Basic idea – Pervasive presence around us a variety of things.
The Vision of Autonomic Computing Self-Management Unit 7-2 Managing the Digital Enterprise Kephart, and Chess.
ASSL1 Modeling the Image- Processing Behavior of the NASA Voyager Mission with ASSL September 12, 2013 by Emil Vassev and Mike Hinchey 2013 NASA Annual.
Model Integrated Computing and Autonomous Negotiating Teams for Autonomic Logistics G.Karsai (ISIS) J. Doyle (MIT) G. Bloor (Boeing)
Supporting Self-Adaptation in Multi- Agent Systems (In Action)
Java Programming: Advanced Topics 1 Enterprise JavaBeans Chapter 14.
UML - Development Process 1 Software Development Process Using UML.
March 2004 At A Glance The AutoFDS provides a web- based interface to acquire, generate, and distribute products, using the GMSEC Reference Architecture.
LECTURE 5 Nangwonvuma M/ Byansi D. Components, interfaces and integration Infrastructure, Middleware and Platforms Techniques – Data warehouses, extending.
SmartGRID Decentralized, dynamic grid scheduling framework on swarm agent-based intelligence Seminar in HUST, Wuhan, China. Oct. 22, 2008 Ye HUANG, Amos.
AUTONOMIC COMPUTING B.Akhila Priya 06211A0504. Present-day IT environments are complex, heterogeneous in terms of software and hardware from multiple.
Introduction to Machine Learning, its potential usage in network area,
Object-Oriented Analysis and Design
Architecting Web Services
NASA Ames Research Center
Architecting Web Services
Intelligent Systems Software Assurance Symposium 2004
AI, Grand Designs, and Safety. Prof. Mike Hinchey, IFIP President-Elect.
Model-Driven Engineering for Mission-Critical IoT Systems
Software Architecture Lecture 20
Systems Engineering for Mission-Driven Modeling
Software Engineering for Safety: a Roadmap
Self-Managed Systems: an Architectural Challenge
Infokall Enterprise Solutions
Presentation transcript:

Lero© 2012 Modeling the Image-Processing Behavior of the NASA Voyager Mission with ASSL Emil Vassev and Mike Hinchey

Lero© 2012 AC & Space Exploration Autonomic Computing (AC) – a solution to software complexity:Autonomic Computing (AC) – a solution to software complexity: Helps to implement self-adaptive and autonomic systems (ASs); Autonomic elements (AEs) – the architectural components of an autonomic system (AS) AC may handles complexity in spacecraft computer systems –The new age of space exploration: NASA embarks in AC AC software helps to build the next generation of unmanned spacecraft; Autonomous Nano-Technology Swarm (ANTS) concept mission; Deep Space One (DS1) mission;

Lero© 2012 Our Approach – Prototyping with ASSL –AC-based ANTS-like and Voyager-like missions: Investigate hypotheses about the design and implementation of future Voyager-like missions based on the AC principles. Build prototype software models: help in the comparison of features and issues of the actual Voyager mission with hypothesized possible autonomic approaches; bring significant benefits to the development of future space-exploration systems. We experiment with ASSL (Autonomic System Specification Language) to realize these goals.

Lero© 2012 Research Objectives –Long-term objectives: model and implement with ASSL AS prototypes of future Voyager- like and ANTS-like missions; benchmark experiments - compare prototyped autonomic features and issues with the actual Voyager Mission; validate features in question and perform further investigations based on practical results under simulated conditions; –First objective: specify with ASSL and generate a prototype model for the image- processing behavior observed in the Voyager mission. –Event-driven behavior –Event-driven behavior: Voyagers are able to detect space objects and take pictures of the same on-the-fly

Lero© 2012 scalable specification model; provides judicious selection and configuration of infrastructure elements and mechanisms for ASs; decomposes an AS in two directions – 1) into levels of functional abstraction; 2) into functionally related sub-tiers; presents the system from three different perspectives – 1) AS; 2) ASIP; 3) AE; meets the AS builders needs; flexible approach to specification. ASSL Specification Model

Lero© 2012 Specifying and Generating Prototypes with ASSL ASSL tiers - intended to specify different aspects of an AS, but only a few are needed to come up with a working model; an ASSL specification is built around self-management policies, which make that specification AC-driven; a complete specification: is validated with a built-in consistency checking tool; is used to automatically generate a functional prototype. generated prototypes: fully-operational multithreaded event- driven applications with embedded messaging; ASSL Policy Specification ASSELF_MANAGEMENT { SELF_HEALING { FLUENT inLosingSpacecraft { INITIATED_BY { EVENTS.spaceCraftLost } TERMINATED_BY { EVENTS.earthNotified } } MAPPING { CONDITIONS { inLosingSpacecraft } DO_ACTIONS { ACTIONS.notifyEarth } }

Lero© 2012 Autonomous Nano Technology Swarm (ANTS)  A novel approach to asteroid belt resource exploration;  Swarm of pico-class, low-power, and low-weight spacecraft:  High autonomy - autonomous and adaptable agents;  Exhibits self-organization emergent behavior;  Single spacecraft:  Equipped with a solar sail;  Onboard computation;  Artificial intelligence techniques.

Lero© 2012 ANTS Architecture Workers - up to 80 percent of the swarm, bear instruments and gather data. Rulers - coordinate data gathering through the use of rules. Messengers - coordinate communications among the workers, rulers, and mission elements on Earth.

Lero© 2012 ANTS Autonomic Properties 1.Self-configuration. ANTS must be fully reconfigurable to support concurrent exploration and examination of hundreds of asteroids. 2.Self-optimizing. ANTS must be able to improve its performance on the fly (group and individual).  rulers;  messengers;  workers. 3.Self-healing. Any ANTS unit, teams, sub-swarms, and the entire swarm must be able to recover from both mistakes and failures. 4.Self-protecting. ANTS must be to anticipate and cure intrusions (for example, solar storms).

Lero© 2012 Goal: “On the fly” configuration of different teams of ANTS units, to explore asteroids. SELF_CONFIGURING – a self- management policy; actions – a set of actions that could be undertaken by ANTS events – a set of events that trigger and are triggered by the actions. metrics – a metric that counts the number of detected asteroids. Self-configuring

Lero© 2012 Goal: Recover from failures, including those caused by damage due to a crash or any outside force. proactive - heartbeat messages; SELF_HEALING policy: inCollision - the worker crashes; inInstrumentBroken - the instrument is not operational anymore; inHeartbeatNotification - initiated on a regular basis by a timed event to send the heartbeat message to the ruler; checkANTInstrument (action) – instrument checking operation; distanceToNearestObject (metric) - distance to the nearest object in space. Self-Healing

Lero© 2012 Goal: ANTS safety objectives should present a level of safety that at least makes ANTS capable of operating under the following hazards: a collision with the other spacecraft units or asteroids; high-density magnetic fields; high radiation (due to a solar eruption); a high energy level (due to a solar eruption); a loss of communication among the ANTS AEs. Safety index 1 index 2 index 4 index 2 index 1 NASA Risk Index Determination

Lero© 2012 Self-scheduling Goal: self-scheduling mechanism in ANTS; some of the tasks could be time-constrained; Modeling self-scheduling for ANTS:  the most complex exercise;  fault tolerance measures to both value and timing violations;  capture the timing and schedulability requirements;  model scheduling at group and individual level; We specified self-scheduling as a distinct self-management policy

Lero© 2012 Prospective ASSL Models for ANTS Self-Optimizing:  self-optimization for rulers - a process of learning;  self-optimization for messengers - a process of positioning to balance the communications between the rulers;  self-optimization for workers - a process of learning about the asteroids. This will allow workers to gain experience. Self-Protecting:  the self-protecting policy – should backs up the safety SLO at both individual and swarm levels;  the self-protecting behavior of the team should be interrelated with the self-protecting behavior of the individual members.

Lero© 2012 an extremely successful example for subsequent space missions; designed for exploration of the Solar System; continue to explore space: now on the special Voyager Interstellar Mission; –Factors of success: rigorous spacecraft design and implementation; spacecraft hardware was designed to allow for enhanced remote control programming; autonomous behavior persists in the Voyager requirements; The Voyager Mission Voyager Spacecraft [The Planetary Society, “Space topics: Voyager – the story of the mission”]

Lero© 2012 Image Processing Behavior 1. The Voyager II spacecraft: –uses its cameras to monitor space objects; –takes a picture with its cameras; –notifies Earth that an image transmission is about to start; –applies color filters and sends the stream of pixels to Earth; –notifies antennas on Earth for the end of each session. 2. Antennas on Earth: –are prompted to receive the image by special messages (one per applied filter); –receive image pixels; –are prompted to terminate the image sessions by special messages; –send the collected images to the Voyager Mission base on Earth. 3. The Voyager Mission base on Earth receives images from antennas.

Lero© 2012 ASSL Model for Voyager we specified Voyager at the three main ASSL tiers – AS tier, ASIP tier, and AE tier; we specified the Voyager II spacecraft and the antennas on Earth as AEs that: follow their encoded autonomic behavior; exchange predefined ASSL messages over predefined ASSL communication channels. the Voyager mission autonomic behavior is specified at both AS and AE tiers as a self-management policy: the global autonomic behavior is determined by the specification of that policy at each AE and at the global AS tier.

Lero© 2012 a pure software solution – both spacecraft and antennas are implemented as interacting components in a Java application; has a multi-granular structure composed of instances (objects) of the specified tiers in the ASSL specification: a hierarchical composition where sub-tier instances are grouped around instances of major tiers. Structure of the Generated Prototype

Lero© 2012 Behavior of the Prototype log records show important state-transition operations ongoing in the system; these records help to trace and evaluate the behavior of the generated prototype model; –Test results: –The run-time behavior of the generated prototype model for the Voyager II mission strictly followed that specified with the ASSL IMAGE_PROCESSING self-management policy.

Lero© 2012 Discussion and Future Work image-processing - programmed as an autonomic policy, but does not extend the original event-driven behavior observed in the Voyager Mission; the Voyager’s prototype abstracts most of the spacecraft components; the next prototype model: will specify the spacecraft’s radio, antenna, and two cameras as distinct managed elements - this will allow the evaluation of component behavior (via ASSL metrics and events); will extend the IMAGE_PROCESSING policy with other self- management features – two scenarios are planned: remote- assistance self-healing and on-board self-healing.

Lero© 2012 Future Work further prototype development: detailed specification of the ANTS and Voyager spacecraft components; new autonomic features - self-healing, self-protecting, and self- adapting policies; construct an intelligent Voyager-like system able to react automatically to hazards in space by finding possible solutions and applying those on-board with no human interaction; a new ASSL model checking mechanism is currently under development – this will allow for automatic feature validation and discovery of design flaws;

Lero© 2012 Benefits both the ASSL specifications and the generated prototypes can be extremely useful for the design and implementation of future ANTS- like andVoyager-like missions; the ability to compare features and issues with the actual mission and with hypothesized possible autonomic approaches gives significant benefit; we develop Voyager prototypes incrementally where each new prototype includes new autonomic features - this helps to evaluate the performance of each feature and gradually construct a model of a future Voyager-like system; this approach helps to discover eventual design flaws in both the original system and the prototype models;

Lero© 2012 Thank you!