OBSERVER='robot' EXPTIME=100 OBJECT='HR6806' PROCEDUR='oseti' RA='18:09:37.4' DEC='+38:27:27' EPOCH=2000 MAG=6.40 ENDThe RA, DEC, EPOCH keywords specify where the telescope will point. The PROCEDUR (the bizarre spelling results from the 8 character limitation of the FITS standard) keyword specifies the name of the program to be executed. The EXPTIME (or OBSTIME) keyword specifies how long the observation will take to execute (for purposes of scheduling it). The OBJECT string is stuck into the FITS header of the resulting file. Other keywords such as MAG might be used to set things in the procedure.
A very crude program mkrequest.c to generate request files from a target list can be found in ~treffers/seti/lists.
Each observation is assigned a unique id code specified by the DATID enviroment variable. This id is of derived from the time of observation and looks like May0vxmy or Mar0ejvp. Details can be found in the description of the mkid command.
A very crude draft of the the oseti procedure written as a C-Shell script follows: It opens the observatory, points the telescope, finds and centers on the star and takes the data. Ultimately writing the data into the file with a name specified by the DATID environment variable.
#!/bin/csh # procedure to make an optical seti observation echo running oseti openup if ($status ) exit 1 tx point ra=$RA dec=$DEC epoch=$EPOCH | grep done if ($status ) exit 1 tx dac dac0 dac0=100 dac1=100 spiral if ($status ) exit 1 center back=300 if ($status ) exit 1 adjust if ($status ) exit 1 qseti outfile=$DATID nsamples=1000 rate=20 if ($status ) exit 1 putsym file=$DATID.fits object=\'$OBJECT\'Notice: that the keywords from the request file are transferred into action via the environment (e.g. $RA means the value of the RA environment variable).
telco datid verbose HR6806.rqs
To run the scheduler you must do the following:
Note: The startins script is somewhat bizarre and I I recommend reading the source script before executing it. Once fired up the show ins command can be used to look at what is happening.
The startins script starts insgen as a program running as a separate process writing its output into the file insgen.log. To modify its behavior commands are transmitted to it via the tin command. With it you can:
NOTE: some tin requests may take 5-10 seconds to execute.
tin newreqs xxx.rqs yyy.rqs
tin wait newreqs *.rqs
There is a syntax checker called accepter for request files that points out some of the more obvious errors. Try it with no worry of moving anything by typing.
You can do some simple tests of the request file without moving anything by typing
telco shell datid myname.rqsThis command will pop up an xterm window with the environment loaded with the stuff from the request file. Type env to see what variables are in the environment. You may then type the program name of the command to be executed (watch out this might move the telescope). Or type other procedures that might use this environment.
You may want to inspect them with the show command.