LOFAR Self-Calibration Using a Blackboard Software Architecture ADASS 2007Marcel LooseASTRON, Dwingeloo.

Slides:



Advertisements
Similar presentations
MicroKernel Pattern Presented by Sahibzada Sami ud din Kashif Khurshid.
Advertisements

Construction process lasts until coding and testing is completed consists of design and implementation reasons for this phase –analysis model is not sufficiently.
Ch:8 Design Concepts S.W Design should have following quality attribute: Functionality Usability Reliability Performance Supportability (extensibility,
Presentation by Prabhjot Singh
MINJAE HWANG THAWAN KOOBURAT CS758 CLASS PROJECT FALL 2009 Extending Task-based Programming Model beyond Shared-memory Systems.
Element Loads Strain and Stress 2D Analyses Structural Mechanics Displacement-based Formulations.
Atacama Large Millimeter/submillimeter Array Expanded Very Large Array Robert C. Byrd Green Bank Telescope Very Long Baseline Array Whoever North American.
Development of Parallel Simulator for Wireless WCDMA Network Hong Zhang Communication lab of HUT.
Best-First Search: Agendas
Software Design Deriving a solution which satisfies software requirements.
Real-Time Human Pose Recognition in Parts from Single Depth Images Presented by: Mohammad A. Gowayyed.
Unified theory of software evolution Reengineering – Business process reengineering and software reengineering BPR model – Business definition, process.
Reference: Message Passing Fundamentals.
Computational Astrophysics: Methodology 1.Identify astrophysical problem 2.Write down corresponding equations 3.Identify numerical algorithm 4.Find a computer.
Memory Management 2010.
High Performance Computing 1 Parallelization Strategies and Load Balancing Some material borrowed from lectures of J. Demmel, UC Berkeley.
CS350/550 Software Engineering Lecture 1. Class Work The main part of the class is a practical software engineering project, in teams of 3-5 people There.
Computer Organization and Architecture
Distributed Processing of Future Radio Astronomical Observations Ger van Diepen ASTRON, Dwingeloo ATNF, Sydney.
Objectives Design Class Diagrams Issues in system design Generalization Review UML papers.
1 L07SoftwareDevelopmentMethod.pptCMSC 104, Version 8/06 Software Development Method Topics l Software Development Life Cycle Reading l Section 1.4 – 1.5.
U.S. Department of the Interior U.S. Geological Survey David V. Hill, Information Dynamics, Contractor to USGS/EROS 12/08/2011 Satellite Image Processing.
1 Reasons for parallelization Can we make GA faster? One of the most promising choices is to use parallel implementations. The reasons for parallelization.
Managing Large RDF Graphs (Infinite Graph) Vaibhav Khadilkar Department of Computer Science, The University of Texas at Dallas FEARLESS engineering.
Introduction to Parallel Programming MapReduce Except where otherwise noted all portions of this work are Copyright (c) 2007 Google and are licensed under.
Introduction to the Enterprise Library. Sounds familiar? Writing a component to encapsulate data access Building a component that allows you to log errors.
The Design Discipline.
Lesson 7 Guide for Software Design Description (SDD)
Implementation Yaodong Bi. Introduction to Implementation Purposes of Implementation – Plan the system integrations required in each iteration – Distribute.
Object Oriented Analysis and Design Introduction.
Network Coding Testbed Jeremy Bergan, Ben Green, Alex Lee.
MapReduce: Simplified Data Processing on Large Clusters Jeffrey Dean and Sanjay Ghemawat.
SAMANVITHA RAMAYANAM 18 TH FEBRUARY 2010 CPE 691 LAYERED APPLICATION.
Andreas Horneffer Status of MKSP LOFAR Observations.
Performance Measurement. A Quantitative Basis for Design n Parallel programming is an optimization problem. n Must take into account several factors:
1 “Genetic Algorithms are good at taking large, potentially huge search spaces and navigating them, looking for optimal combinations of things, solutions.
Chapter 10 Analysis and Design Discipline. 2 Purpose The purpose is to translate the requirements into a specification that describes how to implement.
1 Computing Challenges for the Square Kilometre Array Mathai Joseph & Harrick Vin Tata Research Development & Design Centre Pune, India CHEP Mumbai 16.
Server to Server Communication Redis as an enabler Orion Free
A Fault-Tolerant Environment for Large-Scale Query Processing Mehmet Can Kurt Gagan Agrawal Department of Computer Science and Engineering The Ohio State.
System-level power analysis and estimation September 20, 2006 Chong-Min Kyung.
1 IBM Software Group ® Mastering Object-Oriented Analysis and Design with UML 2.0 Module 9: Describe the Run-time Architecture.
 Design goals are derived form the non- functional requirements  Every subsystem is assigned to a team and realized independently  During system design,
Yazd University, Electrical and Computer Engineering Department Course Title: Advanced Software Engineering By: Mohammad Ali Zare Chahooki The Rational.
A Roadmap towards Machine Intelligence
Coevolutionary Automated Software Correction Josh Wilkerson PhD Candidate in Computer Science Missouri S&T.
August 2003 At A Glance The IRC is a platform independent, extensible, and adaptive framework that provides robust, interactive, and distributed control.
Big traffic data processing framework for intelligent monitoring and recording systems 學生 : 賴弘偉 教授 : 許毅然 作者 : Yingjie Xia a, JinlongChen a,b,n, XindaiLu.
Component Patterns – Architecture and Applications with EJB copyright © 2001, MATHEMA AG Component Patterns Architecture and Applications with EJB Markus.
1. 2 Purpose of This Presentation ◆ To explain how spacecraft can be virtualized by using a standard modeling method; ◆ To introduce the basic concept.
Banaras Hindu University. A Course on Software Reuse by Design Patterns and Frameworks.
1 Architecture and Behavioral Model for Future Cognitive Heterogeneous Networks Advisor: Wei-Yeh Chen Student: Long-Chong Hung G. Chen, Y. Zhang, M. Song,
Onlinedeeneislam.blogspot.com1 Design and Analysis of Algorithms Slide # 1 Download From
Parallel Computing Presented by Justin Reschke
Learning A Better Compiler Predicting Unroll Factors using Supervised Classification And Integrating CPU and L2 Cache Voltage Scaling using Machine Learning.
Software Architecture Architecture represents different things from use cases –Use cases deal primarily with functional properties –Architecture deals.
PDEVS Protocol Performance Prediction using Activity Patterns with Finite Probabilistic DEVS DEMO L. Capocchi, J.F. Santucci, B.P. Zeigler University of.
XFEL The European X-Ray Laser Project X-Ray Free-Electron Laser Wojciech Jalmuzna, Technical University of Lodz, Department of Microelectronics and Computer.
Wednesday NI Vision Sessions
Victoria Ibarra Mat:  Generally, Computer hardware is divided into four main functional areas. These are:  Input devices Input devices  Output.
HIERARCHICAL TEMPORAL MEMORY WHY CANT COMPUTERS BE MORE LIKE THE BRAIN?
Distributed Correlation in Fabric Kiwi Team PSNC.
Foundations of Computer Science
SDLC Model A framework that describes the activities performed at each stage of a software development project.
MBF1413 | Quantitative Methods Prepared by Dr Khairul Anuar
GENERAL VIEW OF KRATOS MULTIPHYSICS
SAMANVITHA RAMAYANAM 18TH FEBRUARY 2010 CPE 691
Object Networks—ATLAS' Future Control Framework For Offline?
Presented By: Darlene Banta
MapReduce: Simplified Data Processing on Large Clusters
Presentation transcript:

LOFAR Self-Calibration Using a Blackboard Software Architecture ADASS 2007Marcel LooseASTRON, Dwingeloo

ADASS 2007, GML-2- Overview The Setting Architectural Design Design Considerations Blackboard Pattern System Overview Subsystems Strategies and Steps Current Status and Future Work

ADASS 2007, GML-3- The Setting Raw UV-data must be calibrated iteratively to Correct for instrumental effects, like Band-pass Beam shape Correct for ionospheric effects Faraday and phase rotation Create a local sky model, containing Point sources Gaussian sources Extended sources

ADASS 2007, GML-4- Architectural Design Design Considerations Data Volume Distributed Processing Scalable Architecture Blackboard Pattern

ADASS 2007, GML-5- The Challenge Data Volume of an average observation will be tens of terabytes. Size must be reduced, otherwise… Long-term archiving will be impossible Local (post-)processing will be impossible Data Rate will be in the order of a gigabyte per second. Data must be distributed, because… A single hard-disk cannot write a GB/s A single computer system cannot handle a GB/s

ADASS 2007, GML-6- Divide and Conquer Data should be distributed such that, for all processing: It does not have to be reordered Large chunks can be processed locally Only little data have to be exchanged

ADASS 2007, GML-7- Divide and Conquer Data could be distributed along a few axes Time is a bad choice The data size of a single time-slot is too large to be sent to a single machine Baseline is a better choice However, it will lead to imaging problems Frequency is the best choice Images are usually made per channel, so imaging could be done locally

ADASS 2007, GML-8- Scalable Architecture Heterogeneous cluster Decouple the computing nodes Process locally. Bring the process to the data Communicate through a global shared memory Several architectural patterns describe this approach

ADASS 2007, GML-9- Blackboard Pattern Ideal for solving problems for which no predetermined algorithm is known. But… “Best” Self-Calibration algorithm can be chosen from a relatively short list of strategies in advance The Shared Repository pattern is probably a better match

ADASS 2007, GML-10- Shared Repository Pattern † Specialization hierarchy of patterns based on the Shared Repository pattern Shared Repository pattern Controller pattern Repository Manager pattern Blackboard-based Control pattern Hierarchical Blackboard pattern Blackboard pattern † Philipe Lalanda, in Proceedings of PLoP’98

ADASS 2007, GML-11- Shared Repository Pattern Controller pattern Introduces a control component in the system that rules the system and schedules activation of other components Can be applied to deterministic problems where sequences of components activation can be determined off-line and coded in the controller Repository Manager pattern Is applicable in a distributed environment Introduces a repository manager that sends notification of data creation or modification to the software components Blackboard pattern Refines the Controller pattern to deal with non-deterministic problems

ADASS 2007, GML-12- Separation of Concerns Maximize scalability by complete separation of global and local controller Global controller issues sequences of commands Local controllers control the so-called “kernels” that execute the commands A database system acts as a shared memory for storing commands and results

ADASS 2007, GML-13- Blackboard Self-Cal System Subsystem overview BBS Control Takes care of the distributed processing by means of the Blackboard pattern BBS Kernel Does the actual processing; it executes a series of steps, where each step consists of an operation like SOLVE or CORRECT BBS Database Consists of two databases — Command Queue and Parameter Database — that together form the blackboard

ADASS 2007, GML-14- BBS Control subsystem Global design of the BBS Control system

ADASS 2007, GML-15- BBS Control subsystem Global Control Acts as the main process Posts one or more commands (steps) to the Command Queue Local Control Controls a BBS Kernel subsystem Fetches the next command from the Command Queue and forwards it to the BBS Kernel subsystem Command Queue Stores the commands to be executed by the BBS Kernel and the status results returned by each kernel Parameter Solutions Stores (intermediate) solutions of the model parameters calculated by the BBS Kernel.

ADASS 2007, GML-16- BBS Kernel subsystem Implements the Measurement Equation Consists of two components: The Kernel implements operations like PREDICT, SUBTRACT, and CORRECT The Solver calculates estimates for the model parameters by minimizing the difference between model and observation

ADASS 2007, GML-17- Strategies and Steps Strategy One iteration in the so- called Major Cycle † Defines a relationship between the observed data and the model parameters. Defines the size of a work domain Consists of a number of steps † J.E. Noordam, LOFAR Calibration Framework, ASTRON

ADASS 2007, GML-18- Strategies and Steps BBS Step Is designed as a Composite pattern; each step can be made up of one or more (sub)steps Leaf classes define a single piece of work that can be handed over to the BBS Kernel subsystem

ADASS 2007, GML-19- Strategies and Steps Work domain A subset of the data that fits in RAM memory As many commands as possible are executed on these data before the next data chunk is accessed. A strategy defines the size of the work domain (in time and frequency)

ADASS 2007, GML-20- Current Status Control framework has been deployed on a 12 node cluster PostgreSQL database is used as shared repository First successful calibration runs on gigabyte-sized datasets

ADASS 2007, GML-21- BBS Image Tycho CygA (remnt) CasA (remnt) 3CR58 3CR84 3CR CR CR61.1 3CR CR CR452 SUN

ADASS 2007, GML-22- Future Work Test actual scalability of the control framework Add support to kernel for calibration of Beam-shape Ionospheric effects Etc.

ADASS 2007, GML-23- See Also ADASS Presentations O4b.3: Distributed Processing of Future Radio Astronomical Observations P9.9: LOFAR Core Station 1 post-processing and inspection tools P9.15: Early LOFAR images with third generation calibration Thank you for your attention!