WPI CS534 Showcase Jeff Martin. * Computer Software on Deep Space 1 * Used to execute plans/mission objectives * Model based * Constraint based * Fault.

Slides:



Advertisements
Similar presentations
Extending the Information Power Grid Throughout the Solar System Al Globus, CSC.
Advertisements

Making the System Operational
JSIMS 28-Jan-99 1 JOINT SIMULATION SYSTEM Modeling Command and Control (C2) with Collaborative Planning Agents Randall Hill and Jonathan Gratch University.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 20 Slide 1 Critical systems development 2.
© 2003 Carnegie Mellon University slide 1 Building CSIRT Capabilities and the State of the Practice Georgia Killcrece CSIRT Development Team CERT ® Training.
Oracle Database Architectures Are Extremely Complex, And Very Expensive. All of Their Complexity Goes Away ! The Snippet Engine Network Architectures Are.
AI Planner Applications Practical Applications of AI Planners.
Experiences with an Architecture for Intelligent Reactive Agents By R. Peter Bonasso, R. James Firby, Erann Gat, David Kortenkamp, David P Miller, Marc.
8. Fault Tolerance in Software
Dynamically Reconfiguring Hierarchies Walter Hsueh CS446 Software Engineering with.
Safeguarding the Three Corner Sat Constellation By Stephen Levin-Stankevich Stephen Nauman.
Simulating A Satellite CSGC Mission Operations Team Cameron HatcherJames Burkert Brandon BobianAleks Jarosz.
JPL Autonomous Space Mission Simulation Flight Team Bob Hoffman Josh Ruggiero Adam Nikolic Dusty Terrill.
Mission Operations in Small Satellite Projects Making Mission Operations Effective J. Burkert Colorado Space Grant Consortium.
CS 603 Communication and Distributed Systems April 15, 2002.
System Integration Management (SIM)
DEVELOPING A COMMUNICATIONS STRATEGY Kelly R Hall, CCE IOM President/CEO Longview Chamber of Commerce
What is it? A mobile robotics system controls a manned or partially manned vehicle-car, submarine, space vehicle | Website for Students.
NASA PKI for PKI FORUM Presenters: Paul Ma, NASA-Ames Research Center
ATIF MEHMOOD MALIK KASHIF SIDDIQUE Improving dependability of Cloud Computing with Fault Tolerance and High Availability.
Team Members Lora zalmover Roni Brodsky Academic Advisor Professional Advisors Dr. Natalya Vanetik Prof. Shlomi Dolev Dr. Guy Tel-Zur.
High Altitude Scientific Ballooning (Near Space Engineering)
1. 2 Purpose of This Presentation ◆ To explain how spacecraft can be virtualized by using a standard modeling method; ◆ To introduce the basic concept.
The Role of Optimization and Deduction in Reactive Systems P. Pandurang Nayak NASA Ames Research Center Brian.
Robot Autonomous Perception Model For Internet-Based Intelligent Robotic System By Sriram Sunnam.
Chapter 16 Designing Effective Output. E – 2 Before H000 Produce Hardware Investment Report HI000 Produce Hardware Investment Lines H100 Read Hardware.
 DATABASE DATABASE  DATABASE ENVIRONMENT DATABASE ENVIRONMENT  WHY STUDY DATABASE WHY STUDY DATABASE  DBMS & ITS FUNCTIONS DBMS & ITS FUNCTIONS 
NATIONAL INSTITUTE OF SCIENCE & TECHNOLOGY Presented by: Santosh kumar Swain Technical Seminar Presentation by SANTOSH KUMAR SWAIN Roll # CS
Protecting the Public, Astronauts and Pilots, the NASA Workforce, and High-Value Equipment and Property Mission Success Starts With Safety Believe it or.
1 Description and Benefits of JWST Commanding Operations Concept TIPS/JIM Meeting 17 July 2003 Vicki Balzano.
.1 RESEARCH & TECHNOLOGY DEVELOPMENT CENTER SYSTEM AND INFORMATION SCIENCES JHU/MIT Proprietary Titan MESSENGER Autonomy Experiment.
Final Version Micro-Arcsecond Imaging Mission, Pathfinder (MAXIM-PF) Mission Operations Tim Rykowski Jeffrey Hosler May 13-17, 2002.
Automated Assistant for Crisis Management Reflective Agent with Distributed Adaptive Reasoning RADAR.
Slide 1 Teams l Most products are too large to be completed by a single software professional with the given time constraints l You will work within a.
Advanced Computer Networks Topic 2: Characterization of Distributed Systems.
Verifying AI Plan Models Even the best laid plans need to be verified Margaret Smith – PI Gordon Cucullu Gerard Holzmann Benjamin Smith Prepared for the.
16.412J/6.835 Intelligent Embedded Systems Prof. Brian Williams Rm Rm NE Prof. Brian Williams Rm Rm NE43-838
California Institute of Technology Formalized Pilot Study of Safety- Critical Software Anomalies Dr. Robyn Lutz and Carmen Mikulski Software Assurance.
Stellar Stars: Reflections of a Center CIO James F. Williams Ames Research Center August 15, 2011.
DSL Distributed Systems Laboratory ATC 23 August Model Mission: Magnetospheric Multiscale (MMS) Mission Goal “To study the microphysics of three.
Intelligent Systems Software Assurance Symposium 2004 Bojan Cukic & Yan Liu, Robyn Lutz & Stacy Nelson, Chris Rouff, Johann Schumann, Margaret Smith July.
EU 2nd Year Review – Feb – WP4 demo – n° 1 WP4 demonstration Fabric Monitoring and Fault Tolerance Sylvain Chapeland Lord Hess.
Institute for Space Systems Analysis and Design College of Engineering Virginia Tech College of Engineering Virginia Tech Chris Hall Aerospace and Ocean.
Mike Graves Summer 2005 University of Texas at Dallas Implicit Invocation: The Task Control Architecture Mike Graves CS6362 Term Paper Dr. Lawrence Chung.
Robotic Space Explorers: To Boldly Go Where No AI System Has Gone Before A Story of Survival J/6.834J September 19, 2001.
1 Standard Onboard Data Handling Architecture Based On SpaceWire Takahiro Yamada and Tadayuki Takahashi (JAXA/ISAS) November 2008 International SpaceWire.
1. 2 Purpose of This Presentation ◆ To explain how spacecraft can be virtualized by using a standard modeling method; ◆ To introduce the basic concept.
Space Systems Laboratory Massachusetts Institute of Technology AUTONOMY MIT Graduate Student Open House March 24, 2000.
SAS_05_Contingency_Lutz_Tal1 Contingency Software in Autonomous Systems Robyn Lutz, JPL/Caltech & ISU Doron Tal, USRA at NASA Ames Ann Patterson-Hine,
Copyright B. Williams J/6.834J, Fall 02 Lecture 3: Immobile Robots and Space Explorers Prof. Brian Williams Rm Wednesday, September 11 th,
SwCDR (Peer) Review 1 UCB MAVEN Particles and Fields Flight Software Critical Design Review Peter R. Harvey.
Control-Theoretic Approaches for Dynamic Information Assurance George Vachtsevanos Georgia Tech Working Meeting U. C. Berkeley February 5, 2003.
Ground Control AERSP 401A. Ground System’s Basic Elements Mission Elements –Control the space segment or handle mission data, and includes: Ground Stations.
XFEL The European X-Ray Laser Project X-Ray Free-Electron Laser Wojciech Jalmuzna, Technical University of Lodz, Department of Microelectronics and Computer.
Autonomy: Executive and Instruments Life in the Atacama 2004 Science & Technology Workshop Nicola Muscettola NASA Ames Reid Simmons Carnegie Mellon.
Information Security Crisis Management Daryl Goodwin.
Engineering and Science Directorate Organization Structure June 2016.
Artificial Intelligence In Power System Author Doshi Pratik H.Darakh Bharat P.
Reading B. Williams and P. Nayak, “A Reactive Planner for a Model-based Executive,” International Joint Conference on Artificial Intelligence, 1997.
Fault Protection Techniques in JPL Spacecraft
Detlef Koschny Research and Scientific Support Department ESA/ESTEC
Temporal Planning: Part 2
NASA Ames Research Center
Distributed Databases
Intelligent Systems Software Assurance Symposium 2004
JPL Autonomous Space Mission Simulation
AI in Space – Lessons From NASA’s Deep Space 1 Mission
Stratford University Restaurant Reservations System
Contract & Client Management
Presented by Derek Bistline
Presentation transcript:

WPI CS534 Showcase Jeff Martin

* Computer Software on Deep Space 1 * Used to execute plans/mission objectives * Model based * Constraint based * Fault tolerant

* Remote agent was a result of the New Millennium Program * This program was established to test technologies that would be used in Space [1] * Remote Agent was created from the join effort from [2]: * NASA's Ames Research Center * JPL (Cal Tech's Jet Propulsion Labratory * Was First tested on NewMaap [2] * New Millennium Autonomous Architecture Rapid Prototype * First Version was developed in 5 months. * Its goals where to plan and execute entry through Saturn's Rings and define an orbit * Was field tested on DS1 [3]

* To perform decisions on a space craft without interaction from ground controllers * Will allow faster response time to environment conditions * To be used when communication to ground control is not possible

* "Planner/Scheduler” * Execution component: called "Smart Executive” * "Mode Identification and Recovery (MIR)"

* Database of mission objectives(goals) * Creates Plans for mission objectives for next timeline * Define the operations (activities) that are needed to meet the objectives * Ex: while one operation is performed another cannot be * New Plan requests * Normal conditions * Requests new plan based on horizon * Fault conditions * Requests new plan if detected issue will effect future execution * Decisions made based on potential outcomes * Running more equipment then available power

* Makes initial request for a plan * executes operations that meet the objectives from the plan devised by the planner * Space craft component operations * Makes decisions on what to do in the event the outcome is not successful * taking a picture of an object * Attempts to recover (Retry, recovery from MIR, await replanning)

* Mode Identification and recovery * Monitors state of the systems on the Spacecraft * receives sensor data * compares to expected model * Recognizes problems * Requests actions to correct to Smart Executive * Reports Failures to Smart Executive

* The FAQ Site says no [1] * MEDIA Relations press release say "the first artificial Intelligence software in history to command a spacecraft" [2] * It is expected to handle situations that are unexpected, given current circumstances

* Provided in the notes section of each slide * Main References: * agent/ agent/ * * Peter Norvig was an Affiliate member of the team.