Scheduling Toolkit Observation Scheduling Boyd Waters, NRAO

Slides:



Advertisements
Similar presentations
National Radio Astronomy Observatory June 13/14, 2005 EVLA Phase II Proposal Review EVLA Phase II Computing Development Bryan Butler (EVLA System Engineer.
Advertisements

SYSTEM ANALYSIS & DESIGN (DCT 2013)
Bill SahrEVLA M&C Transition System Software CDR December 5-6, EVLA Monitor & Control Transition System Software Overview.
Hunt for Molecules, Paris, 2005-Sep-20 Software Development for ALMA Robert LUCAS IRAM Grenoble France.
EVLA Computing Overview Gareth Hunt EVLA Advisory Committee 2002 June
1 Cronbach’s Alpha It is very common in psychological research to collect multiple measures of the same construct. For example, in a questionnaire designed.
Doug Tody E2E Perspective EVLA Advisory Committee Meeting December 14-15, 2004 EVLA Software E2E Perspective.
Overall Data Processing Architecture Review EVLA Monitor and Control Interfaces July , 2002EVLA Data Processing PDR Bill Sahr.
Bill Sahr EVLA M&C EVLA Advisory Committee Meeting December 14-15, EVLA Monitor & Control.
K. Y. LoEVLA Advisory Committee Meeting September 6-7, 2007 Charge to the Committee K. Y. Lo.
2007Sep06 EAC Butler - Software Overview 1 Software Overview Bryan Butler.
Observing Modes from a Software viewpoint Robert Lucas and Philippe Salomé (SSR)
P. NapierEVLA Advisory Committee Meeting September 8-9, EVLA Advisory Committee Project Overview P. Napier, Project Manager Management, Schedule,
P.NapierEVLA Advisory Comm, 14 Dec 2004 Project Overview Peter Napier, EVLA Project Manager Status 2003 Committee Response.
Introduction to EVLA Software Bryan Butler. 2006Dec05/06EVLA M&C Transition Software CDR2 EVLA Computing (Terse) History The original EVLA Phase I proposal.
Gustaaf van MoorselEVLA Advisory Committee Meeting December 14-15, 2004 EVLA Computing Organization/Development.
Pipeline Basics Jared Crossley NRAO NRAO. What is a data pipeline?  One or more programs that perform a task with reduced user interaction.  May be.
Station Board Testing EVLA Correlator S/W F2F 3-4 April 2006 D. Fort.
Data Standards Development August 29, Topics 1.Current Status 2.What was delivered for Build 2c 3.How was IPDA supported 4.What mission support.
EVLA Monitor & Control Software PDR E2E Interfaces: Observation Scheduling Complaints to: Boyd Waters John Benson, Barry Clark, Tim Cornwell, Rich Moeser,
N. RadziwillEVLA Advisory Committee Meeting May 8-9, 2006 NRAO End to End (e2e) Operations Division Nicole M. Radziwill.
EVLA Data Processing PDR E2E Data Archive System John Benson, NRAO July 18, 2002.
Correlator GUI Sonja Vrcic Socorro, April 3, 2006.
EVLA Monitor & Control Software PDR Status. May 15, 2002EVLA Monitor & Control Software PDR Bill Sahr 2 Requirements, Schedule Requirements (High Level,
Gustaaf van MoorselEVLA Advisory Committee Meeting December 14-15, 2004 EVLA Computing End-to-end (E2e) software.
Software Requirements for the Testing of Prototype Correlator Sonja Vrcic Socorro, December 11, 2007.
Computing Introduction Gareth Hunt EVLA System PDR 2001 December 04.
Overall Data Processing Architecture EVLA timeline and priorities.
EVLA Data Processing PDR Pipeline design Tim Cornwell, NRAO.
Scenario use cases Szymon Mueller PSNC. Agenda 1.General description of experiment use case. 2.Detailed description of use cases: 1.Preparation for observation.
© 2012 Cengage Learning. All Rights Reserved. This edition is intended for use outside of the U.S. only, with content that may be different from the U.S.
1 Team Skill 3 Defining the System Part 1: Use Case Modeling Noureddine Abbadeni Al-Ain University of Science and Technology College of Engineering and.
1 Mission preparation Fred Lahuis SRON / Leiden Observatory MIRI NL Meeting ASTRON, 3 th June 2010.
Confirm teams. Review of diagrams. SELECT problems.
Software Overview Sonja Vrcic
UML Diagrams By Daniel Damaris Novarianto S..
CMPE 280 Web UI Design and Development August 29 Class Meeting
Interaction of SSS Software
Bryan Butler EVLA Computing Division Head
Software Verification and Validation
Architecture Concept Documents
Project Controls: As-Built S-Curves
Introduction to New Product Development (Portfolio)
FORMAL SYSTEM DEVELOPMENT METHODOLOGIES
EAC Butler - SSS Software
EVLA Overall Software Design
INFS 6225 – Object-Oriented Systems Analysis & Design
Unit# 9: Computer Program Development
Introduction to Systems Analysis and Design
Software Requirements
EVLA M/C Software PDR, 14 May 2002
EVLA Data Processing PDR
VLA to EVLA Transition Plan
Bryan Butler (for Bill Sahr)
EVLA Computing Reorganization
EVLA Advisory Committee Meeting
EVLA Monitor & Control System
Gustaaf van Moorsel September 9, 2003
Software Requirements
Mark McKinnon EVLA Project Manager
Background Information P.Napier
Observing with Modern Observatories (the data flow)
EVLA Advisory Committee Meeting, March 19-20, 2009
Jeff Mangum (NRAO) Robert Lucas (IRAM) Baltasar Vila Vilaro (NAOJ)
ICT Gaming Lesson 2.
EVLA Monitor & Control Bill Sahr NSF Review May , 2006
Overview of Workflows: Why Use Them?
Topics discussed in this section:
Requirements Bryan Butler.
SDLC (Software Development Life Cycle)
Presentation transcript:

Scheduling Toolkit Observation Scheduling Boyd Waters, NRAO July 18 - 19, 2002 EVLA Data Processing PDR Observation Scheduling Boyd Waters, NRAO Originally, Bill Sahr was going to present this topic, but it really makes sense to have an e2e person do it. The material discussed in this presentation is the result of the work of the EVLA M&C Computing group, and the e2e Team. But I probably got some stuff wrong and left some stuff out, so complaints to Boyd Waters. Boyd Waters

e2e-EVLA Interaction Observation Scheduling Software Monitor & Control Scheduling Toolkit July 18 - 19, 2002 e2e-EVLA Interaction Observation Scheduling Software Proposal Preparation and Submission Observation Preparation Observation Scheduling Monitor and Control System Antenna Feed Receiver IF System Local Oscillator Fiber Optics Transmission System Correlator Image Pipeline Data Archive Data Post-Processing CBE Monitor & Control System This is the data-flow diagram that was in the documentation submitted to the National Science Foundation. I don’t expect you to read all the labels here. The point is that the green stuff is the primary responsibility of the Data Management Group (mostly the e2e Project), while the red stuff is the responsibility of the EVLA Project. The major interaction between these teams, discussed in this presentation, is between the “Observing layer” and the “Monitor and Control” systems. July 18 - 19, 2002 EVLA Data Processing PDR Boyd Waters

EVLA Data Processing PDR e2e-EVLA II Scheduling Toolkit July 18 - 19, 2002 Barry Clark presented this diagram on the first day of the EVLA M&C PDR. I’ve added the colors consistent with the previous diagram, to emphasize the similarity between these two diagrams. This diagram emphasizes that the piece of the “observing layer” that interacts with M&C is the Observation Scheduler. Diagram Design: B. Clark July 18 - 19, 2002 EVLA Data Processing PDR Boyd Waters

Observation Scripting Path Real-time Observing Table Glish Script XML XML July 18 - 19, 2002 EVLA Data Processing PDR

Scheduling Phases Scheduling Toolkit July 18 - 19, 2002 The data flow starts at the top-right of the diagram, with the Proposal Submission; Submissions turn into Approved Proposals, which are processed to obtain a Project that contains observation instructions (in a scripting language). Sets of Projects are examined by the Dynamic Scheduler, which orders the Projects according to observing logic based on current conditions and observation constraints (e.g., good weather for high-frequency observing). Boyd Waters

Dynamic Scheduling Structure the Observation… …so that we can… Respond to Events on a Short Time Scale Changing conditions (e.g. weather) Targets of Opportunity (e.g. GRBs) … Block-Based Scheduling July 18 - 19, 2002 EVLA Data Processing PDR

EVLA Data Processing PDR Scheduling Toolkit July 18 - 19, 2002 Observing Block Observing Block Preamble “Post-amble” 20 minutes is a typical calibration duty cycle. But the blocks can vary in size. The internal structure used by the observing block is To Be Decided. ~20(?) minutes nominal July 18 - 19, 2002 EVLA Data Processing PDR Boyd Waters

EVLA Data Processing PDR Observing “Session” A series of blocks Preamble is run ONLY for the FIRST Post-amble is run ONLY for the LAST Observing Block Preamble Observing Block Observing Block “Post-amble” … … July 18 - 19, 2002 EVLA Data Processing PDR

Observing Block Constraints Scheduling Toolkit July 18 - 19, 2002 Observing Block Constraints “Run this block until the calibrations converge” “I can’t run unless the previous block has run successfully” “I MUST run at 16:42:30 GST on 30 May 2002” (fixed scheduling is dynamic scheduling with time-domain constraints) These are EXAMPLES, not REQUIREMENTS. Requirements here have yet to be gathered, but we can collect such and use the requirements to get a better idea of what the observing blocks will need to express. July 18 - 19, 2002 EVLA Data Processing PDR Boyd Waters

EVLA Data Processing PDR Block Templates Debug blocks Template blocks “Default” blocks July 18 - 19, 2002 EVLA Data Processing PDR

Block-Based Scheduler Telescope sees ONE BLOCK AT A TIME: Block Queue Observing Block Preamble “Post-amble” Observing Block Preamble “Post-amble” Observing Block Preamble “Post-amble” “ready for next block” “here it is” Observing Block Preamble “Post-amble” Implications: Simplifies the telescope state data Telescope reports block execution status back to the block queue All “observing logic” is maintained by the Block Queue Telescope July 18 - 19, 2002 EVLA Data Processing PDR

EVLA Data Processing PDR Block Execution Observing Block Preamble “Post-amble” 1 Observing Block Preamble “Post-amble” 2 Observing Block Preamble “Post-amble” 3 Observing Block Preamble “Post-amble” Observing Block Preamble “Post-amble” Input Queue: Observing Block Preamble “Post-amble” 1 Observing Block Preamble “Post-amble” 2 Observing Block Preamble “Post-amble” 2 Observing Block Preamble “Post-amble” Observing Block Preamble “Post-amble” 3 Execution: July 18 - 19, 2002 EVLA Data Processing PDR

Block Execution: Detail Observing Block Preamble “Post-amble” 3 Observing Block Preamble “Post-amble” 1 2 3 4 Observing Block Preamble “Post-amble” 1 Observing Block Preamble “Post-amble” 2 Observing Block Preamble “Post-amble” Observing Block Preamble “Post-amble” 3 Observing Block Preamble “Post-amble” 4 ? Observing Block Preamble “Post-amble” 5 Input Queue: ready ready ready ready Failed! ready Observing Block Preamble “Post-amble” 1 Observing Block Preamble “Post-amble” 2 Observing Block Preamble “Post-amble” 2 Preamble 2 Observing Block Observing Block Preamble “Post-amble” Observing Block Preamble “Post-amble” 3 Execution: Measurement Set ok Measurement Set ok Measurement Set ok Measurement Set ok Archive: July 18 - 19, 2002 EVLA Data Processing PDR

EVLA Data Processing PDR Next Steps Gather and Codify Requirements Observing Block constraints M&C Observing System Interaction Formal Model Observing System Scripting How instrument commands and observing constraints are expressed July 18 - 19, 2002 EVLA Data Processing PDR