130 likes | 256 Views
OCS/OMP Overview. Nick Rees Frossie Economou Tim Jenness. Some History. Apr 94 Discussion of JCMT Control System Futures Sept 95 “Upgrades to the JCMT Control System” Sept 96 ACSIS proposal Oct 96 Heterodyne OCS - Project Overview (OCS/SN/1) Apr 97 Original ORAC proposal (called OCSDR)
E N D
OCS/OMP Overview Nick Rees Frossie Economou Tim Jenness
Some History • Apr 94 Discussion of JCMT Control System Futures • Sept 95 “Upgrades to the JCMT Control System” • Sept 96 ACSIS proposal • Oct 96 Heterodyne OCS - Project Overview (OCS/SN/1) • Apr 97 Original ORAC proposal (called OCSDR) • Apr 97 OCS Design & Planning Meetings - TODD, Proj. Plan • Aug 97 First RTS Specs (ACSIS Note 6) • Oct 97 Joint ACSIS/OCS discussion meetings • Dec 97 Software Forward Look (OCS 6 months) • Feb 98 Beta-1 Release of the TODD • Apr 98 ACSIS PDR
More History • Jun 98 First OMP project plan (OMP/PN/002) • Jan 99 NPR becomes head of JAC software • Mar 99 JCMT, UKIRT and Gemini Scheduling Workshop • Aug 99 RMP left JAC • Jan 00 OCS put on hold • Apr 00 OCS project reformulated so it is at ATC (RTS, TODD, TODD recipes and OT for ACSIS. Observing Manager not part of ATC deliverables) • Jun 00 RTS Requirements Document. RTS starts taking shape • Aug 00 ORAC released, JCMT TCS released • Nov 00 OMP project restarts/JAC Software groups reorganized. • Dec 00 SCUBA OT added to OCS project deliverables • Jan 01 RTS written review
OMP Project Observation Preparation Schedulable Blocks Obs. Management Observation Database Observation Translation Observation Selection JCMT OCS Project OCS System System Configurations ORAC Project Pointing + Focus Observation Sequencing Ancillary Control System Telescope Control System Instrument Control System Data Handling Data Reduction JAC Observing Model
Why the OMP/OCS complications? (Why is the OCS project not responsible for the entire OCS system - why are they different?) • ATC work needs to be well specified • OMP and OCS systems overlap - OMP must replace considerable amounts of ‘bare OCS’ system. • Often summed up as “ORAC for JCMT” • Effort availability at both sites.
OCS Project SWOT • Successes • RTS prototype delivery • RTS review • Weaknesses • Lack of interface definitions • Lack of OT definition • Opportunities • Use of Martin Folger’s UKIRT OT experience • Meetings over the next few months • Threats • Manpower and funding
Milestones • Jan 01: RTS Review. • May 01: JCMT Board meeting. ACSIS reassessed. • Jun 01?: Delivery of upgraded OT to JAC. • Jul 01: OMP prototypes on UKIRT service. • Oct 01: OMP delivers to UKIRT. • Oct 01: Delivery of RTS to ACSIS and JCMT. • Nov 01?: OMP interim delivery to JCMT for SCUBA. • Dec 01?: Delivery of ACSIS OT. • Dec 01?: Proposed ACSIS delivery date. • Apr 02?: Delivery of SCUBA OT to JCMT.
What do we currently have? • OMP is fully ramped up. • TODD (from ATC in 1998). • Prototype frequency editor (from ATC in 1999). • Prototype RTS (from ATC in 2000). • ORAC-OT. • Lots of ORAC experience. • New TCS. • ACSIS and HARP progressing well.
What do we need now? OMP has decided on major technologies Sybase => Need training (expensive). also needed to support Sybase operationally CORBA => Appears fairly straight forward in our context XML => Pervades throughout JCMT system Must define OT upgrade Nothing has been done formally yet. We must meet to define UKIRT and JCMT requirements. Finalize RTS review and hence RTS design Must define lower level interfaces Large JCMT Interfaces meeting(s) early next FY.
Budget Estimates OCS may require resources in 2002/03?
Actions • EIR and AJA to discuss February travel and Sybase training. • EIR/NPR/PF to finalize JAC software project budget for next year. • NPR to generate ACSIS specific ATC effort and spend for ACSIS+ (JCMT board meeting) (end of week). • NPR/FE to sort out power outage support during week of 5-9 Feb. • NPR to put presentation in an accessible place.