1 / 18

JCMT, UKIRT and Gemini Scheduling Workshop

JCMT, UKIRT and Gemini Scheduling Workshop. Day 1 Review. Agenda - Day 1. Session 1: UKIRT projects and plans. (Subaru) 08:45-09:00 Introduction and welcome - Nick Rees 09:00-09:45 Current ORAC project - Gillian Wright 09:45-10:30 Planned ORAC Scheduler - Alan Bridger

aldis
Download Presentation

JCMT, UKIRT and Gemini Scheduling Workshop

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. JCMT, UKIRT and Gemini Scheduling Workshop Day 1 Review

  2. Agenda - Day 1 • Session 1: UKIRT projects and plans. (Subaru) • 08:45-09:00 Introduction and welcome - Nick Rees • 09:00-09:45 Current ORAC project - Gillian Wright • 09:45-10:30 Planned ORAC Scheduler - Alan Bridger • Session 2: JCMT projects and plans. (Subaru) • 11:00-11:30 Current JCMT OCS project - Richard Prestage • 11:30-12:15 JCMT OM project - Remo Tilanus • 12:15-12:45 ACSIS project and expectations - Bill Dent • Session 3: Merging plans and requirements. (JAC) • 14:00-16:30 Discussion of morning session, agreement on shared JCMT/UKIRT requirements, priorities, timescales. Who from UKIRT, JCMT and ATC might be available to work on the project, at what level and for how long?

  3. 1. ORAC Stage 1 • UKIRT. Observation Reduction and Acquisition Control • Modular: • ORAC/Gemini OT (Beta) - for observation preparation. • Chooser (Alpha -)- Translator between SGML and different instrument and telescope ‘languages’, classical observing user interface. • Data Handling System (Beta) - Gemini ICD-3 generating NDF’s, Quick Look using Gaia/SkyCat • ORAC-DR (Beta) - Modular: pipeline, algorithm engine, recipes and primitives. Implemented in Perl with Starlink algorithms. • Final release of ORAC Stage 1 September 1999.

  4. ORAC Stage II - 1 • Scheduler to optimize scheduling both for short term (nightly and classical) and long term (semester). • Improve observing efficiency, flexible observing etc. • Originally replacement for Chooser, now a separate tool. • Tools to assist efficient flexible scheduling.

  5. ORAC Stage II - 2 • Modular: • Scheduling engine: use or derive from an existing system. • Observation and plan database: commercial - OO or relational? • User interface(s). • Database query and manipulation handlers: • select next observation to be passed to chooser. • checking sanity of plans generated by scheduler. • assist flexible scheduling process (observation feedback, notifying PI, shipping data). • interacting with data archive. • Reports.

  6. JCMT OCS project - 1 • Observatory Control System • Current JCMT system: • Heterodyne Instruments and SCUBA are two separate control programs that control a: • Core system of TELescope, Tertiary Mirror Unit (TMU) and Secondary Mirror Unit (SMU). • OCS project developed Telescope Observation Designer and Driver (Todd) to replace SCUBA and Heterodyne control programs because: • heterodyne CONTROL task is difficult to maintain. • Single control system to maintain, not two.

  7. JCMT OCS project - 2 • Todd can be driven from: • higher level scheduler or • command line. • Todd sequence driven by an Observation Definition File (ODF) and performs a single observation. • A single observation generates a single data file, just like UKIRT’s observe concept.

  8. JCMT OMP - 1 • Observation Management Project • Flexible Scheduling • will become norm, rather than exception • Always schedule most scientifically appropriate observation. • Project oriented, not observer oriented (opposite of classical). • Flexible/Scheduled and Service/P.I. observing are not synonyms, but orthogonal. • Must, at a minimum, result in data equal to that of average, experienced observer.

  9. JCMT OMP - 2 • Current suite of utilities • Data reduction pipeline (ORAC-DR) • Very successful, needs user interface • Observation desk • Scusky - helps plan individual observation. • Scunoise - monitoring Scuba noise for given observation. • Source plot - helps plan nights observations. • Observation desk log - review nights observing • Queue management • ODF generator • End of night summary

  10. JCMT OMP - 3 • Still to come • RMS calculator. • Queue assistant. • Communications are vital! • Four way: P.I., Observer, Scheduler, Queue Manager • BugZilla (off the shelf action request system). P.I. BUG ZILLA Scheduler Observer Queue Manager

  11. JCMT OMP - 4 • Flexible observing has three phases • Phase 1 (proposal), • Phase 2 (preparation and data generation), • Phase 3 (data hand-over, archive, close of project). • … and four layers • Processes • Products • People • Tools • Over-emphasis on tools, neglecting other layers

  12. ACSIS project • Autocorrelator and Spectral line Imaging System • imaging heterodyne system • HARP-B front end. • Requires OCS project, and observing tool. • Observing Tool • output is ODF’s. • needs pre-defined templates, must guide novice observer • avoid repeating information. • needs careful user interface design. • automatic display of predicted sensitivity

  13. Discussion - 1 • Requirements: • In an ideal world, JCMT and UKIRT are nearly identical. • Priorities are similar: UKIRT 1. Database 2. BugZilla 3. Scheduler JCMT 0. Queue to drive Todd. 1. Database. 2. Observing tool. 3. BugZilla 4. Scheduler

  14. Discussion - 2 • Timescales: • UKIRT • requires as much flexible scheduling as they can afford before second coming of Michelle (mid 2001?). • Would immediately benefit if some features can be realized for UFTI, UIST and Michelle commissioning scheduling. • JCMT • has immediate requirements for more assistance with flexible scheduling • ACSIS needs Observing Tool before mid 2000, preferably earlier.

  15. Discussion - 3 • Manpower - UKIRT • ORAC Stage II PDR proposed 3.5 dsy total starting in November 1999. Nominally: • 1.7 dsy/year) at ATC • 0.5 dsy/year at JAC • Difficult to afford this (ATC effort will cost ~$200,000/year or ~10% of UKIRT Ops budget). • Manpower - JCMT • Must implement project within existing manpower. Possibly: • 0.5 dsy/year at ATC (maybe not from JCMT budget?) • 0.5 dsy/year at JAC

  16. Discussion - 4 • Design • JCMT has been forced to take approach of developing tools to fulfil immediate needs, using cheap student effort. • UKIRT has been able to concentrate on global design. • ORAC global design was acceptable to JCMT, but need an observation queue immediately since it has many of the functions of ‘a poor mans scheduler’ • ORAC team had proposed an observation queue, but was rejected by a review since fully featured scheduler maybe was anticipated. • Review decision may be wrong. Queue could/should be reinvestigated - if cost is minor then maybe increase scope of ORAC Stage I, otherwise ORAC Stage II de-scope option.

  17. Conclusions • I thought it was a very positive day. • We have great scope for working together, but we will need to remain pragmatic.

  18. Agenda - Day 2 • Session 4: Gemini projects and plans. (Subaru) • 09:00-09:30 Summary of Tuesday - Nick Rees • 09:30-10:30 Gemini high level software/plans - Phil Puxley • Session 5: Overlap between all three projects. (JAC) • 11:00-12:30 Discussion of overlap between all three. • Session 6: Design and interface discussions. (JAC) • 13:30-15:00 Interface discussions. • 15:00-16:30 Work-package discussions.

More Related