next up previous contents
Next: Programmer's reference Up: OYSTER support for other Previous: Motivation   Contents

OIFITS reader

The primary access to OYSTER procedures is via the OIFITS reader (get_oifits), which stores the data internally in the scans and other auxilliary IDL structures. Alternatively, VLTI MIDI and AMBER data can be reduced using the MyMidiGui and MyAmberGui front ends (http://www.eso.org/$\sim$chummel/midi/mymidigui/mymidigui.html,
http://www.eso.org/$\sim$chummel/amber/myambergui/myambergui.html). These provide easy to use GUIs for the externally developed data reduction softwares (MIA+EWS and amdlib), and automatically store data internally using OYSTER's data structures, as well as write data to disk in OIFITS format.

For data to be stored internally in OYSTER many requirements are to be met, mostly for historical reasons of a data package first released over 15 years ago. These procedures are handled in a mostly transparent way, but need to be kept in mind in case of adaptations of the code to specific applications. Here we point out relevant ``pecularities'' of OYSTER.


next up previous contents
Next: Programmer's reference Up: OYSTER support for other Previous: Motivation   Contents
Christian Hummel 2009-10-20