* written by Stephen Levine; modified by Gaguik Tovamssian.
* over several observing runs in 1995 and 1996. There are two versions
* of these macros, one for the new and one for the old verions of the
* PMIS CCD control system.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
These original macros have been changed to accomodate new instalments and
advices of some observers. The news include filling the RA and DEC in the
header of the fits files automatically from the new consola. Automatically
define the CCD (its GAIN and RDNOISE) owned by OAN and placing it also in
the header info. Define the exact place and size of the CCD and adding it
to the header as well. If program would be unable to identify CCD and its
parameters ind would inquire
parameters ind would inquire observer.
Yet another news is the requirement to install UT
time on the PC, which runs the PMIS programs. The newinit.cmd,
which should be first macro to execute at the begining of the
night will give a reminder to check/install the proper UT time
in the computer.
The new macros are placed in the same newtek.lst
and observer should check if it is installed or load
it from directory /PMIS/MACROS.
Gaguik Tovmasian (gag@bufadora.astrosen.unam.mx)
3 August 1997.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
These macros are designed to handle image sequencing
and adding fits
card header information on the PC at acquisition
time. The file names
are limited to a maximum of 8 characters before the
dot (like in old
DOS file names), and I have set this to use a series
of files named:
bias1001.fit, bias1002.fit ... for bias frames
flat1001.fit, flat1002.fit ... for flat fields
arc1001.fit, arc1002.fit ... for arc frames
dark1001.fit, dark1002.fit ... for dark frames
dark1002.fit ... for dark frames
obj1001.fit, obs1002.fit ... for object observations
The sequence counters are initialized in newinit.cmd. My own preference
is to use 1000 as the base number for night 1, 2000
for night 2 etc.
Before you get into PMIS, startup espia.exe, to handle automatic
transfer of fits files (named *.fit) from the PC ram disk to the
hard disk on the sun workstation. You can write directly to the
Sun disk, but writing to the RAM disk and letting espia move the
file reduces by about 1 minute the waiting time between
exposures.
When PMIS is opened, remember to setup the Camera and CCD formats
first, and then do a New Image. Then execute inits.cmd. All the rest
of the macros depend upon variables set up by inits.
0) newtek.lst - macro list for quick loading of all the below named
macros by PMIS. Pull down the macros menu, and cli. Pull down the macros menu, and click on Load List
then have it load newtek.lst.
Required arguments are shown as <arg>
Optional arguments are shown as [arg]
1) newinit.cmd - initialize internal variables for the CCD macros
usage: newinit - you will be inquired for:
<sequence number>
this sets the basic sequence number for separate
counters for bias, arc, flat, dark and object
images. It should be editted by the user to set
constant information for the fits cards (like
observers, site, and such).
ex: inits 4000 - files will be numbered as
bias4001.fit, bias4002.fit etc
arc4001.fit, arc4001.fit etc
<observer name>
<instrument>
<telescope>
<directory> of fits files and macros. These are installed by
defaults and I advise you not to change unless you
want to do something special.
2) onebias.cmd - take a single bias frame and write it out to disk as
a fite it out to disk as
a fits file
usage: onebias
no arguments
3) fivebias.cmd - take 5 bias frames -no arguments
4) onedark.cmd - take a single dark frame
usage: onedark <exposure time in seconds> [filter]
5) oneflat.cmd - take a single flat field frame
usage: oneflat <exposure time in seconds> [filter]
5a) 3flat.cmd - take 3 flats.
usage: 3flat <exposure time in seconds> [filter]
6) onearc.cmd - take a single comparison lamp frame
usage: onearc <exposure time in seconds> [filter]
7) oneobs.cmd - take a single object frame
usage: oneobs <exposure time in seconds> <name>
[filter]
7) newobs.cmd will do the same job as oneobs.cmd, but will inquire observer
necessary parameters.
8) 3obs.cmd - take 3 obs of the same object.
9) newsimg.cmd - this is the macro that actually does all the work.
typically it is never actually directly called by the user.
usage: simg.cmd <exp.time&
usage: simg.cmd <exp.time> <sequence #> <object type>