1 / 22

The ORAC-DR pipeline

The ORAC-DR pipeline. Frossie Economou & Tim Jenness Joint Astronomy Centre, Hawaii. ORAC-DR. How it all started Design overview How to modify it. How it all started. UKIRT set up the ORAC project with the UK ATC to modernise observing software ORAC-OT: observation preparation

john
Download Presentation

The ORAC-DR pipeline

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. The ORAC-DR pipeline Frossie Economou & Tim Jenness Joint Astronomy Centre, Hawaii

  2. ORAC-DR • How it all started • Design overview • How to modify it ORAC-DR

  3. How it all started • UKIRT set up the ORAC project with the UK ATC to modernise observing software • ORAC-OT: observation preparation • ORAC-OM/OS: acquisition control • ORAC-DR: online data reduction ORAC-DR

  4. The way it was • UKIRT early pioneer of online data reduction systems • Instrument specific packages tied to the acquisition software • Wheels were frequently re-invented • JCMT had no on-line data reduction facilities ORAC-DR

  5. What UKIRT wanted to do • Have one DR system for all present and future UKIRT instruments • Minimize software effort required to cope with a new instrument • Take advantage of developments in the community • Maintain staff and user expectations of quality and robustness ORAC-DR

  6. What JCMT wanted to do • SCUBA widened the traditional JCMT community • Flexible scheduling was introduced • These created a need for online data reduction software to allow inexperienced observers to monitor data quality ORAC-DR

  7. Cunning plan • ORAC-DR was initially destined for UFTI… • … but we used CGS4 and SCUBA in the design • Very different instruments • Different acquisition systems • Different observing modes ORAC-DR

  8. What’s it for • ORAC-DR is or will be the pipeline for • UFTI • SCUBA • IRCAM/TUFTI • CGS4 • MICHELLE • UIST • and more

  9. Requirements • Flexibility • Extensibility • Robustness • Hardware is cheaper than people ORAC-DR

  10. ORAC-DR

  11. ORAC-DR components • Pipeline • Recipes and primitives • Messaging interface to algorithm engines ORAC-DR

  12. Pipeline • perl • data detection • housekeeping ORAC-DR

  13. Recipes • “English” (code is allowed but frowned upon) • Individual steps can be re-arranged at will • Edited with a text editor but could use a drag-and-drop style GUI ORAC-DR

  14. Primitives • perl code • may contain other primitives • one astronomically meaningful step • order independent ORAC-DR

  15. Object oriented design • Primitives query and/or manipulate a set of global objects • Frame • Group • Calibration • Display ORAC-DR

  16. Frame object • Knows what the actual file is called • Generates output filenames • Knows about sub-frames associated with the observation ORAC-DR

  17. Group object • Knows what the actual file is called ORAC-DR

  18. Calibration object ORAC-DR

  19. Display object ORAC-DR

  20. Stuff that comes with ORAC-DR • oracman • oracdisp ORAC-DR

  21. Adding instruments to ORAC-DR • Similar to present: 1-4 weeks • Different but same infrastructure: 6-8 months • Different with new infrastructure 8-12 months ORAC-DR

  22. ORAC-DR wishlist • interface to the IRAF message bus • interface to glish • gui launchpad • gui recipe builder ORAC-DR

More Related