GENERIC - A GSMT spectrograph. The user is required to specific wavelength region and resolution and very little else and an unspecific instrument is "created" by means of an IRAF script.
MOMFOS - Multi-Object, Multi-Fiber, Optical Spectrograph. The Prime Focus, optical, fiber-fed spectrograph. Tables are set up which describe the properties of the telescope and this instrument in some detail.
NIRDIF - Near-IR Deployable IFU spectrometer. (ITC not ready yet.)
MIHDAS - Mid-IR High-Dispersion Astronomical Spectrometer. (ITC not ready yet)
spectimedb$GSMT/scripts/scripts.cl
Type:
epar spectime
and insert the above parameter in the scripts field. Having
set this parameter, invoking the spectime package will set up this pointer
to the necessary scripts.
For flexibility and control, the user is urged to copy the required files from the server into her own working directory. When the spectime package is invoked (with the scripts parameter set as above), a script is made available which will accomplish this. To invoke the script type cpfiles. This creates a top level directory GSMTTEST beneath your home directory and places the default directory structure in it, with separate directories for each of the ITCs and the associated files.
These files and the parameters in the tasks together serve to document the state of the telescope&instrument when the calculations are made. Since the user will very likely want to modify the tables it is important that she has full control over them. Thus, after running cpfiles:
cl>ls
GSMTTEST
cd GSMTTEST
ls
GENERIC/ MOMFOS/ scripts/ <- this list will grow
cd GENERIC
ls
HgCdTe
extinct_nearir generic_VIS
irsky1_5
bg
generic gsmt_cass
emissivity generic_IR_Cass
irsky
There are several levels at which the user may use an ITC. We will illustrate with a few example at different levels of complexity starting with the simplest. We will assume that the ITC in use is GENERIC because it is anticipated that this is the one where the user will want most control. But the same principles apply to all.
[N.B. In the other more specific ITCs, the setup will be "hardwired" in the parameters provided. Setup should not be run]
Then, to set up the spectrograph type:
setup
It will prompt you for the required parameters.
Once setup has been run one simply runs sptime. Default parameters are used for the other parameters of the spectrograph unless you change them. The task sptime does not prompt for parameters. You may want to type unlearn sptime to make sure you are starting from defaults. To set or change the observing parameters type epar sptime and edit the parameter set.
Further notes on the spectrograph "designed" by setup:
When you run setup, the blaze wavelength and the observing wavelength
have been set equal for simplicity. In addition, for simplicity, the spectrograph
is always working in Littrow (angle between incident and diffracted beams
= 0.0). When you change the operating wavelength (in sptime) and don't
re-run setup, the spectrograph parameters are fixed and the grating is
automatically tilted to put the central wavelength at the center of the
detector.
>sptime time=100 output=ALL - same as above but also opens a graphics window and displays a series of graphs. Quit the sequence with q; step through the graphs with any other key.
>sptime sn=20 - gives text output with exposure time required to reach specified S/N ratio. Note there is a parameter which sets the maximum integration time (default 3600 sec). If the requested S/N ratio is not achieve in less than the max, the number of multiple integrations required will also becomputed.
>sptime sn=50 refflux=23 - computes time to reach S/N of 50 for an object of magnitude 23 (whose flux at the reference wavelength corresponds to a body of magnitude 23).
>epar sptime - one can adjust the parameters freely. For example, one will frequently want to change the following parameters:
output - select different output graphs to be displayed (ALL gets everything). extinction - insert the name of different atmospheric extinction tables spectrum - insert the name of an (ascii) table containing the target object spectrum (the default is a blackbody spectrum and the user specifies the magnitude at the central wavelength. Read the example: spectrum_example for format. [This file is not very interesting at the moment. Would Joan or Arjun be interested in providing a useful example? The format is described in the sptime documentation.])
>lpar sptime
>lpar specpars | page (the list is long)
Parameters are mostly either numbers, strings, or the names of a tables. The tables can contain parameters themselves (the same parameters which occur in sptime) but more importantly contain multi-column lists giving wavelength dependent quantities like efficiency or atmospheric emission. For an example, type irsky1_5.
To change a parameter type epar sptime (or specpars) and edit the list.
[more examples]
[discuss handling
sky conditions
spectral resolutions]
Use of PSETs. In the GENERIC ITC, the script setup sets some
parameters in the PSET specpars. You can inspect the parameters by typing
>lpar specpars (Type: lpar sptime |
page to page through the long list).
or
>epar specpars
You can also accomplish this within the sptime parameter editor
by typing :e<return> in the field for specpars.
The specpars contains most of the spectrograph-defining parameters. Note, however, that the observing wavelength, diffraction order and slit width are set in sptime, not in specpars.