Purpose of EFS

The Echelle Format Simulator (EFS) is used primary in two ways. The first is to run the NIRSPEC Instrument. It does this by allowing the user to set up a number of options and settings, such and slit width, filter, and exposure time, and sending a script of commands to the NIRSPEC server, which carries out these commands. The second use is to set up one of these scripts but instead of running, save it for use at another time. By using the EFS, an observer can set up a script from the comfort of his or her office, home, or any other location, save it, and execute it at the instrument, saving valuable observing time.

Interaction with the DRP

The NIRSPEC software package is an interweaving collaborative effort in which the multiple programs all interact with each other, the server, and the instrument. In this way, NIRSPEC becomes increasingly more powerful, while at the same time, easier to use. This is clearly evident in the interaction between the EFS and the Data Reduction Pipeline, or the DRP. When the EFS writes a script, the DRP, which is constantly monitoring the server, takes note and begins to process the script itself. It therefore knows what the instrument is going to do, and begins to prepare for the incoming data. The data, upon arrival, is then processed, using the various information stored in the script by the EFS. After processing, the reduced data is either saved to disk, or sent to another component of the NIRSPEC software package, Quicklook. Therefore, when used in conjunction, you can go from a simple user interface like the EFS to a reduced image with minimal effort.

Scripts and Configurations

Information about the instrument and telescope setup is stored in a script. A script is a text file in which a set of commands are written, and when desired, is executed as a C-Shell program. They typically have the extension of *.csh. A configuration is the set up of every parameter to be set by the EFS. This includes filters, slits, integration times, object name, etc. When a you hit the Save Configuration As? button in the main menu, the configuration is saved to a file in the form of a script. When the GO button is hit, first the configuration is saved to a script, then the script is exectued. If a previously written script is opened, EFS looks through the script to determine the configuration, then sets up the fields and dropdown menus and such in the EFS to reflect this configuration.