Engineering Measurement System (EMS) Project Charter Thursday, January 23, 2003 Kim Constantikes Ramon Creager

Slides:



Advertisements
Similar presentations
DIGIDOC A web based tool to Manage Documents. System Overview DigiDoc is a web-based customizable, integrated solution for Business Process Management.
Advertisements

1 1 Mechanical Design and Production Dept, Faculty of Engineering, Zagazig University, Egypt. Mechanical Design and Production Dept, Faculty of Engineering,
System Development Life Cycle (SDLC)
Ch:8 Design Concepts S.W Design should have following quality attribute: Functionality Usability Reliability Performance Supportability (extensibility,
Modeling Electrical Systems With EMTP-RV
Objectives Explain the purpose and various phases of the traditional systems development life cycle (SDLC) Explain when to use an adaptive approach to.
Software Modeling SWE5441 Lecture 3 Eng. Mohammed Timraz
Alternate Software Development Methodologies
Case Tools Trisha Cummings. Our Definition of CASE  CASE is the use of computer-based support in the software development process.  A CASE tool is a.
® IBM Software Group © 2006 IBM Corporation Rational Software France Object-Oriented Analysis and Design with UML2 and Rational Software Modeler 04. Other.
MotoHawk Training Model-Based Design of Embedded Systems.
Network Management Overview IACT 918 July 2004 Gene Awyzio SITACS University of Wollongong.
Quicktime Howell Istance School of Computing De Montfort University.
DCS Architecture Bob Krzaczek. Key Design Requirement Distilled from the DCS Mission statement and the results of the Conceptual Design Review (June 1999):
Microsoft Visio is diagramming software for Microsoft Windows. It uses vector graphics to create diagrams. The 2007 Standard and Professional editions.
Interpret Application Specifications
Objectives Explain the purpose and various phases of the traditional systems development life cycle (SDLC) Explain when to use an adaptive approach to.
What is adaptive web technology?  There is an increasingly large demand for software systems which are able to operate effectively in dynamic environments.
Software Issues Derived from Dr. Fawcett’s Slides Phil Pratt-Szeliga Fall 2009.
Cambodia-India Entrepreneurship Development Centre - : :.... :-:-
Introduction to Systems Analysis and Design
Architectural Design Establishing the overall structure of a software system Objectives To introduce architectural design and to discuss its importance.
Enterprise Architecture
System Design/Implementation and Support for Build 2 PDS Management Council Face-to-Face Mountain View, CA Nov 30 - Dec 1, 2011 Sean Hardman.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 18 Slide 1 Software Reuse 2.
Microsoft Visual Basic 2012 CHAPTER ONE Introduction to Visual Basic 2012 Programming.
Microsoft Visual Basic 2005 CHAPTER 1 Introduction to Visual Basic 2005 Programming.
Create with SharePoint 2010 Jen Dodd Sr. Solutions Consultant
Software Engineering Muhammad Fahad Khan
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 18 Slide 1 Software Reuse.
SSIS Over DTS Sagayaraj Putti (139460). 5 September What is DTS?  Data Transformation Services (DTS)  DTS is a set of objects and utilities that.
April 8/9, 2003 Green Bank GBT PTCS Conceptual Design Review GBT Precision Telescope Control System Kim Constantikes 4/8-9/03.
FP OntoGrid: Paving the way for Knowledgeable Grid Services and Systems WP8: Use case 1: Quality Analysis for Satellite Missions.
Framework for Automated Builds Natalia Ratnikova CHEP’03.
2Object-Oriented Analysis and Design with the Unified Process Objectives  Explain the purpose and various phases of the traditional systems development.
` Tangible Interaction with the R Software Environment Using the Meuse Dataset Rachel Bradford, Landon Rogge, Dr. Brygg Ullmer, Dr. Christopher White `
An Introduction to Software Architecture
Upgrade to Real Time Linux Target: A MATLAB-Based Graphical Control Environment Thesis Defense by Hai Xu CLEMSON U N I V E R S I T Y Department of Electrical.
OBJECT ORIENTED SYSTEM ANALYSIS AND DESIGN. COURSE OUTLINE The world of the Information Systems Analyst Approaches to System Development The Analyst as.
CHAPTER TEN AUTHORING.
OOI CI LCA REVIEW August 2010 Ocean Observatories Initiative OOI Cyberinfrastructure Architecture Overview Michael Meisinger Life Cycle Architecture Review.
Doug Tody E2E Perspective EVLA Advisory Committee Meeting December 14-15, 2004 EVLA Software E2E Perspective.
Component Technology. Challenges Facing the Software Industry Today’s applications are large & complex – time consuming to develop, difficult and costly.
© 2012 xtUML.org Bill Chown – Mentor Graphics Model Driven Engineering.
Middleware for FIs Apeego House 4B, Tardeo Rd. Mumbai Tel: Fax:
Information Systems Engineering. Lecture Outline Information Systems Architecture Information System Architecture components Information Engineering Phases.
Chapter 10 Analysis and Design Discipline. 2 Purpose The purpose is to translate the requirements into a specification that describes how to implement.
MURI: Integrated Fusion, Performance Prediction, and Sensor Management for Automatic Target Exploitation 1 Dynamic Sensor Resource Management for ATE MURI.
Lesson Overview 3.1 Components of the DBMS 3.1 Components of the DBMS 3.2 Components of The Database Application 3.2 Components of The Database Application.
L6-S1 UML Overview 2003 SJSU -- CmpE Advanced Object-Oriented Analysis & Design Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I College.
NA-MIC National Alliance for Medical Image Computing UCSD: Engineering Core 2 Portal and Grid Infrastructure.
C OMPUTING E SSENTIALS Timothy J. O’Leary Linda I. O’Leary Presentations by: Fred Bounds.
March 2004 At A Glance autoProducts is an automated flight dynamics product generation system. It provides a mission flight operations team with the capability.
Chapter 6 CASE Tools Software Engineering Chapter 6-- CASE TOOLS
MODEL-BASED SOFTWARE ARCHITECTURES.  Models of software are used in an increasing number of projects to handle the complexity of application domains.
CASE (Computer-Aided Software Engineering) Tools Software that is used to support software process activities. Provides software process support by:- –
April 8/9, 2003 Green Bank GBT PTCS Conceptual Design Review Overview of the High Frequency Observing System Richard Prestage.
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
Mantid Stakeholder Review Nick Draper 01/11/2007.
August 2003 At A Glance The IRC is a platform independent, extensible, and adaptive framework that provides robust, interactive, and distributed control.
8-1 © Prentice Hall, 2007 Topic 8: Selecting the Best Alternative Design Strategy Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra,
Oman College of Management and Technology Course – MM Topic 7 Production and Distribution of Multimedia Titles CS/MIS Department.
Impact Research 1 Enabling Decision Making Through Business Intelligence: Preview of Report.
Software Architecture Architecture represents different things from use cases –Use cases deal primarily with functional properties –Architecture deals.
Ganga/Dirac Data Management meeting October 2003 Gennady Kuznetsov Production Manager Tools and Ganga (New Architecture)
Online Performance Analysis and Visualization of Large-Scale Parallel Applications Kai Li, Allen D. Malony, Sameer Shende, Robert Bell Performance Research.
Kai Li, Allen D. Malony, Sameer Shende, Robert Bell
Introduction to Visual Basic 2008 Programming
Analysis models and design models
Enterprise Program Management Office
Presentation transcript:

Engineering Measurement System (EMS) Project Charter Thursday, January 23, 2003 Kim Constantikes Ramon Creager Paul Marganian Richard Prestage Nicole Radziwill

PTCS Vision The mission of the Precision Telescope Control System (PTCS) project is to collect and synthesize measurements related to the structure of the telescope, allowing for more accurate monitoring of the telescope structure and improved control of telescope alignment and pointing. Traditional telescope control can allow the GBT to observe at low to medium observation frequencies. Beyond these frequencies structural uncertainties, gravitational, temperature and wind induced deformations and a variety of other effects render traditional means inadequate. The ultimate goal of the PTCS is to enable the telescope to perform at these higher frequencies.

Need for EMS PTCS: At the top level, the PTCS consists of two main components: Precision Measurement System (PMS): –Uses metrology devices such as Laser Rangefinders and Quadrant Detector, together with other devices (inclinometers, accelerometers, etc) to precisely measure the location, orientation and shape of the optical elements of the GBT Precision Control System (PCS): –Uses the input demands and PMS measurements to control the optical elements of the GBT. EMS: The optimal measurement strategies and data-processing algorithms for the PMS are not yet known. A key role of the EMS is to provide a prototyping environment to experiment with a variety of different measurement and processing strategies. The EMS will also provide a production platform with which engineering metrology measurements may be made, independently of the PTCS (e.g. surveying the antenna for structural integrity checks). The EMS is a key component in the development path to the full PTCS!

The goal of the EMS is to prototype processing data from the laser range finders to generate required information for PCS (or engineering applications) – in a routine and straightforward way. This is a challenging problem for which significant R&D is required. The goal of the EMS is to prototype processing data from the laser range finders to generate required information for PCS (or engineering applications) – in a routine and straightforward way. This is a challenging problem for which significant R&D is required. EMS Vision STEP 1 STEP 2 STEP 3 Implement tools to enable rapid algorithm development Explore and develop algorithms and models Implement a production-quality system to manage the collection and analysis of appropriate measurements on a regular basis

Step 1: Implement Tools

A Real-Time Rapid Prototyping Environment PTCS engineers and scientists must have the means to easily investigate control methods and algorithms. They should be able to configure experiments and test these algorithms without the need to re-compile and re-install production quality software systems. The EMS Algorithm Development Platform (ADP) will provide them with a real-time rapid prototyping environment that will allow them to: generate complex experiments test algorithms, and immediately view results without the need for support from software (except to create and refine this environment). Step 1 is primarily a software integration activity, with the goal of leveraging as much commercial off-the-shelf software as possible.

The EMS Algorithm Development Platform (ADP) 1: User Interface and Workflow Manager (WiT) 4: Visualization (Matlab) Note: Although the EMS ADP is being developed for PTCS, could be used as an algorithm development platform for other projects as well. 2: Data Acquisition (New) 3: Computation (Matlab) The complete platform integrates 6 capabilities to enable algorithm development, plus the ability for investigators to easily share results with one another for optimal time-to-convergence of algorithms. 5: Interapplication Communication 6: Data Sharing

WiT – for Workflow Management WiT is a visual programming tool targeted to the image processing community. Algorithms are created by dragging and dropping icons that represent operations onto a workspace to create executable block diagrams called igraphs. Links between the icons direct data from one icon to the next. WiT provides a DLL interface to allow users to create custom operation icons. Signal Flow representation of a signal processing task. Similar to Argonne National Laboratory’s EPICS

Matlab – for Computation and Visualization Matlab is a powerful, integrated mathematical computation and visualization tool. It is an ideal environment for developing and testing mathematical algorithms. Because of its open architecture, it lends itself readily to being integrated into EMS. Because of this, it can serve as the computing engine for EMS. Its key features are: –Numerical computation tools –Graphics for visualization and analysis of data –Interactive development –Interfaces to allow integration with other applications through COM, DDE & DLLs.

EMS ADP Application Architecture ZY … WiT Environment ZIY Data Stream TCP Client (DLL) ZIY Service ZIY Client (Metrology GUI) ODBC Interface (DLL) EMS Database Generic Matlab Interface (DLL) Matlab M&C System (GBT Control) Existing components New EMS components PSM Stream TCP Client (DLL) TCP Server (DLL) PSM Antenna Monitor Goal of the EMS Database is to preserve measurements in an easily accessible format to allow tracking over time: Locations of various targets or points on the telescope within specified coordinate systems Calibrations associated with the laser range finders Characterizations and model output Data Recording, Playback Capability (T.EXE) Data Record/Playback Path

A Database Driven System To be developed from the existing gbt_metrology MySQL database, which already contains a large proportion of the data fields that will be necessary for the EMS Will provide a clear distinction between measured and inferred values Components: Measurements – contains up-to-date knowledge about, but not limited to, the laser rangefinder system, including: calibrations on the laser rangefinders and piers, locations of and constants relating to the retros, and calibrations pertaining to the atmosphere Experiments – contains descriptions of experiments, application environment settings, experimentally determined data, and any other values needed to accurately and specifically characterize the experiment

EMS ADP User Scenario EMS is conceived to allow the engineer unfettered access to the metrology system, and see immediate results. Can be used in real-time or off-line. When a PTCS scientist or engineer conceives of an experiment, he/she would use EMS something like this: 1.If necessary, write algorithm(s) in Matlab 2.If necessary, create the signal flow diagram in WiT, specifying the instruments and targets needed for the experiment 3.Optionally, the engineer could test the experiment offline using old data and the playback capability of the T.EXE utility ( T.EXE can read a file saved earlier and play it back displaced in time through a TCP server port, effectively mimicking the ZIY Service). 4.Set up the Metrology system and the GBT using their respective user interfaces 5.Run the experiment and check results. Using EMS, the engineer can then easily change the configuration or the algorithms and test again!

EMS ADP Enables Faster Algorithm Determination The EMS goal (1-2 days?) A more traditional approach (2-3 months): Engineer Writes Requirements Engineer Request Software Support Design Implementation Test OK? Software Delivered to Engineer Success? End Start Engineer Plans Experiment Engineer Sets up Experiment Success? End Engineer Plans Experiment Engineer Sets up Experiment No Yes No

Solution Components: Definitions The following terms have been used throughout this solution strategy: COM: Component Object Model. The distributed object architecture used by Microsoft. DLL: Dynamic Link Library. A type of shared binary library used by the Win32 family of operating systems. These are the key components used in extending programs such as WiT and Matlab. Matlab: A mathematical & numerical computation and graphical display tool. Provides the EMS computation and visualization capabilities. M&C System: The GBT monitoring and control software system. The EMS will not control any hardware, thus M&C may be required to control some components needed by the EMS. Metrology Interface: The portion of the Metrology software system that provides a monitoring and control GUI for the operation of the system. ODBC: Open DataBase Connectivity. This is an Application Programming Interface (API) that allows a programmer to abstract a program from a database. PTCS: The Precision Telescope Control System. That subset of the M&C system that will be responsible for allowing the GBT to observe at frequencies higher that would be possible using traditional telescope control. Trilateration: The computation of a target’s location given ranges from at least 3 ZY devices whose location is well known. Visual C++: The Microsoft C++ software development tool. Needed to develop DLLs for Matlab and WiT. These DLLs will act as the integration points between the two commercial applications. WiT: A graphical programming environment for rapid prototype development. Provides the environment that allows for the specification of workflow. ZIY: The Metrology System monitor and control software. Orchestrates the actions of the ZY units. ZY (Laser Rangefinder): The precision distance ranging instrument developed by NRAO.

In Scope Data Acquisition capabilities for the EMS ADP will initially be developed based on interfaces that currently exist to the GB M&C system and Metrology system. Implementation of the EMS ADP will be performed with full cognition of decisions made for the GBT Small Footprint Data Acquisition and Control Package (GDAQ), to be developed separately from the EMS. Additional interfaces may be developed to accommodate this. If the PTCS project team determines that incremental updates are required to the laser rangefinder system, these may also be performed in the context of EMS ADP development.

The EMS ADP will not control any hardware, but will simply provide a dashboard for the investigation of data provided by using other systems: –Laser Metrology hardware & software will be controlled from the Metrology System operator interface, ZIY Client –GBT will be controlled by operator through M&C/Cleo –Other PTCS metrology components (accelerometers, quadrant detector, etc.) will be accessed and controlled through M&C In initial implementation, EMS will not trilaterate on moving targets Out of Scope

Step 2: Explore Algorithms

Algorithm Exploration Will Include: 1.Trilateration using arbitrary retros, stationary telescope 2.Trilateration with moving telescope 3.Determining the position of a retro seen by any one or two laser rangefinders at a particular point in time 4.Fusing multiple measurements using optimal estimators (e.g. Kalman filters) 5.Sophisticated interpolation of signals 6.Extracting data that is regularly spaced in time from irregularly sampled data 7.Many more topics, to be determined dynamically throughout the R&D process

Step 3: Migrate to Production Systems

Migration Plan Once the algorithms are determined, they will be A) reimplemented in the GBT M&C framework for speed, reliability, robustness and compatibility reasons, or B) the algorithm development platform will be evolved to become the PMS Design details will be determined after the appropriate algorithms, and expected data rates through the system, are identified. EMS Algorithm Development Platform Precision Measurement System (PMS) Key PTCS component used in conjunction With M&C system to improve telescope Alignment and pointing Engineering Measurement System (EMS) Surveying tool that engineers can use to Measure the antenna independent of the PTCS becomes Is deprecated * May need to include new user’s interface that integrates telescope control, metrology control, and the EMS/PMS.

Project Planning

Task List 1Complete EMS Charter 21 st releaseThis encompasses the bare minimum code to make EMS work (prototypes of all new components in application architecture, perhaps using existing Wells database) 31 st TestsTest the EMS infrastructure implemented in 1 st release 41 st TrilaterationThis will be the first experiment run by a functional EMS 52 nd releaseImprovements to expand EMS capability. Includes: – transition to full featured database – trilateration of moving target – grid trilateration 6Tutorial/DocumentationA simple and straightforward document to explain EMS basics