Examples of DCS Interaction with an FSI Bob Krzaczek.

Slides:



Advertisements
Similar presentations
Testing Relational Database
Advertisements

Campus02.at don't stop thinking about tomorrow DI Anton Scheibelmasser Setubal ICINCO /25 Device integration into automation systems with.
MapReduce Online Created by: Rajesh Gadipuuri Modified by: Ying Lu.
Selecting & Defining Command and Control Systems for Mine Ventilation Presented By: Sancar James Fredsti.
Software Process Models
1 CEOS/WGISS20 – Kyiv – September 13, 2005 Paul Kopp SIPAD New Generation: Dominique Heulet CNES 18, Avenue E.Belin Toulouse Cedex 9 France
1 Databases in ALICE L.Betev LCG Database Deployment and Persistency Workshop Geneva, October 17, 2005.
ProActive Task Manager Component for SEGL Parameter Sweeping Natalia Currle-Linde and Wasseim Alzouabi High Performance Computing Center Stuttgart (HLRS),
A Brief Introduction to Software Design and Design Quality By Laura Leventhal.
HAWCPol / SuperHAWC Software & Operations J. Dotson July 28, 2007.
SOFIA DCS History and Overview Ian Gatley. SOFIA March DCS Preliminary Design Review2 The South Pole CARA Project: A DCS demonstration A data.
Verification Joel Kastner. HAWC/DCS Verification Describe observing sequence for a test target Generate simulated data Process through HAWC and DCS pipelines.
DCS Architecture Bob Krzaczek. Key Design Requirement Distilled from the DCS Mission statement and the results of the Conceptual Design Review (June 1999):
Paradigms for Process Interaction ECEN5053 Software Engineering of Distributed Systems University of Colorado, Boulder.
Octopus system1 Moshe Tocker Avihai Mejer. Octopus system2 The Octopus system Goal The system’s primary goal is to Measure performance parameters in real.
SIM5102 Software Evaluation
Dynamic Reconfiguration of Component-based Real-time Software Words February 2005 Sedona, Arizona, USA Andreas Rasche, Andreas Polze and Martin.
Software Engineering Module 1 -Components Teaching unit 3 – Advanced development Ernesto Damiani Free University of Bozen - Bolzano Lesson 2 – Components.
Chapter 10: Architectural Design
C++ fundamentals.
What is Software Architecture?
1 EECS 231 ADVANCED PROGRAMMING. 2 Staff Instructor Vana Doufexi Ford Building, 2133 Sheridan, #2-229 Teaching Assistant.
COGNITIVE RADIO FOR NEXT-GENERATION WIRELESS NETWORKS: AN APPROACH TO OPPORTUNISTIC CHANNEL SELECTION IN IEEE BASED WIRELESS MESH Dusit Niyato,
SCRAM Software Configuration, Release And Management Background SCRAM has been developed to enable large, geographically dispersed and autonomous groups.
A Pattern for Gradual Transitioning during Dynamic Component Replacement in Extreme Performance UAV Hybrid Control Systems Murat Guler, Linda Wills, Scott.
Pixel Upgrade Plans ROD/BOC PRR July 17, 2013 T. Flick University of Wuppertal.
DCS Overview MCS/DCS Technical Interchange Meeting August, 2000.
Michał Zaczek Tutor: dr inż. Krzysztof Poźniak Data Base of Distant Universe Events Institute of Electronic Systems Group : PERG.
Chapter 2 소프트웨어공학 Software Engineering 임현승 강원대학교
Internal usage only Nestle Chembong – IND780 Q.i System Overview.
IMPROUVEMENT OF COMPUTER NETWORKS SECURITY BY USING FAULT TOLERANT CLUSTERS Prof. S ERB AUREL Ph. D. Prof. PATRICIU VICTOR-VALERIU Ph. D. Military Technical.
SPACE TELESCOPE SCIENCE INSTITUTE Operated for NASA by AURA COS Pipeline Language(s) We plan to develop CALCOS using Python and C Another programming language?
Magnetic Field Measurement System as Part of a Software Family Jerzy M. Nogiec Joe DiMarco Fermilab.
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 07. Review Architectural Representation – Using UML – Using ADL.
An Introduction to Design Patterns. Introduction Promote reuse. Use the experiences of software developers. A shared library/lingo used by developers.
Architecting Web Services Unit – II – PART - III.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 7: Focusing on Users and Their Tasks.
What are the main differences and commonalities between the IS and DA systems? How information is transferred between tasks: (i) IS it may be often achieved.
Doug Tody E2E Perspective EVLA Advisory Committee Meeting December 14-15, 2004 EVLA Software E2E Perspective.
Integrated Data Cycle Systems Harvey E. Rhody Chester F. Carlson Center for Imaging Science.
Unit 2 Architectural Styles and Case Studies | Website for Students | VTU NOTES | QUESTION PAPERS | NEWS | RESULTS 1.
SSC SI Data Processing Pipeline Plans Tom Stephens USRA Information Systems Development Manager SSSC Meeting – Sept 29, 2009.
GAYA Analyzer SDD Presentation. GAYA Analyzer Introduction OMS40G256 is a hardware device used for detection of radioactive radiation for medical imaging.
Safety-Critical Systems 7 Summary T V - Lifecycle model System Acceptance System Integration & Test Module Integration & Test Requirements Analysis.
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 13. Review Shared Data Software Architectures – Black board Style architecture.
Gedae, Inc. Gedae: Auto Coding to a Virtual Machine Authors: William I. Lundgren, Kerry B. Barnes, James W. Steed HPEC 2004.
August 2003 At A Glance The IRC is a platform independent, extensible, and adaptive framework that provides robust, interactive, and distributed control.
Marcelo R.N. Mendes. What is FINCoS? A set of tools for data generation, load submission, and performance measurement of CEP systems; Main Characteristics:
A user interface framework for Grid-based computational steering and visualization. Jason Wood*, Mark Riding and Ken Brodlie.
Or how to work smarter when building solutions.  2:30 – 3:30 Mondays – focus on problem solving (with some terminology thrown in upon occasion)  All.
WASP Airborne Data Processor Laboratory for Imaging Algorithms and Systems Chester F. Carlson Center for Imaging Science Rochester Institute of Technology.
Motivation FACE architecture encourages modularity of components on data boundaries Transport Services Segment interface is centered on sending and receiving.
More Patterns CS 124. More Basic Patterns Patterns you’ve already seen (without knowing it) Observer / Listener Wrapper Composite Decorator / Filter Patterns.
Slide 1 2/22/2016 Policy-Based Management With SNMP SNMPCONF Working Group - Interim Meeting May 2000 Jon Saperia.
From Use Cases to Implementation 1. Structural and Behavioral Aspects of Collaborations  Two aspects of Collaborations Structural – specifies the static.
Event Management. EMU Graham Heyes April Overview Background Requirements Solution Status.
GLAST Large Area Telescope Instrument Flight Software Flight Unit Design Review 16 September 2004 Instrument Configuration by File James Swain Stanford.
From Use Cases to Implementation 1. Mapping Requirements Directly to Design and Code  For many, if not most, of our requirements it is relatively easy.
CLASSIFICATION OF DESIGN PATTERNS Hladchuk Maksym.
Managing, Storing, and Executing DTS Packages
Programming paradigms
Architecting Web Services
SOFTWARE DESIGN AND ARCHITECTURE
Introduction to Design Patterns
FAULT TOLERANCE TECHNIQUE USED IN SEAWOLF SUBMARINE
Architecting Web Services
Ch > 28.4.
Authors: Barry Smyth, Mark T. Keane, Padraig Cunningham
Software Architecture
Gordon Erlebacher Florida State University
Presentation transcript:

Examples of DCS Interaction with an FSI Bob Krzaczek

FSI Chain Example: AIRES Some instruments are very easy to adapt, as they run in a scripted “batch” mode. Note potential for reuse: 2/3 of this simple chain is applicable to other instruments. Extract EXP plan for current flight leg Convert this leg’s EXP into target schedule Build AIRES EXP script

FSI Chains Chains are created by linking small function-specific modules together. Modules are small, and therefore easily used by or ported to similar instruments or modes. Data Acquisition Task Instrument or Simulator... Reduce EXP plan

DCS Pipeline Example: AIRES AIRES already has a pipeline of their own development with 12 separate reductions. We can encapsulate their pipeline as a single DCS “algorithm” to get running in the short term. DCS Storage “Faucet” “Sink” Existing Pipeline

DCS Pipeline Example: AIRES Later, as time and resources permit, we can port the existing AIRES pipeline over to the DCS structure. This will not impact existing reductions. Benefits include speed and fault tolerance. DCS Storage “Faucet” “Sink” Bad Pixel Mask Cosmic Ray Mask Combine Raw Data Gain Correction...

DCS Pipelines Pipelines are created by connecting algorithm elements together at runtime. Modules are small, and therefore easily used by or ported to similar pipelines. DCS Storage “Faucet” “Sink” algo

FSI Chain Example: ABU “Consider SPIREX/ABU as if it were a DCS instrument.” Other instruments may need to be commanded “on the fly”. The FSI Chain is lengthened with more modules that simply do further refinement. Extract EXP plan for current flight leg Convert this leg’s EXP into target schedule Emit target & mode according to GPS Send commands (“stare”, “nod”, “move”)

Additional DCS Design Requirements Each instrument mode will have one or more pipelines associated with it. The DCS must support new pipelines throughout SOFIA lifetime. Previous pipelines should remain available for reducing old data or validating new algorithms.

DCS Design Goals The addition of a new pipeline to the SOFIA program should not impact the existing DCS system. All infrastructure and support for interfacing with the DCS will be provided to the pipeline designer. Enable the reuse of software components between similar pipelines.

DCS Pipelines Each planned observation includes a pipeline and its required parameters. The DCS provides the communication and distribution mechanisms; pipeline designers need only focus on algorithm development. Current design allows for easy porting of existing pre-DCS pipelines to DCS structure.

Example Pipeline Description aires_001 rawAiresData rawAiresFrames reducedAiresData airesImages