|
Документ взят из кэша поисковой машины. Адрес
оригинального документа
: http://www.naic.edu/~cima/cima_file_obs_new.html
Дата изменения: Thu Mar 1 19:02:27 2012 Дата индексирования: Mon Oct 1 23:16:35 2012 Кодировка: Поисковые слова: http astrokuban.info astrokuban |
The pulsar version of command file observing which was called Pulsar Catalog Observing in earlier versions of CIMA has been removed. Pulsar observers should use the general command file observing facility.
Note that command file observations have its own pecularities. Since the command file is executed by the CIMA executive, many parameters are not communicated back to the CIMA frontend. Thus, if You look at parameter values in the CIMA menus, they may not correspond at all to the values that are actually used. For example, if You are running a command file using the WAPPs and open the back-end menu, it may - incorrectly - tell You that the interim correlator is being used. Command file observing is thus an activity considered suitable for more advanced CIMA users.
The first thing to do is to use the 'Load' button to select and load a command file into CIMA. Once loaded, the command file will be listed in the window with line numbers added in front of each line. The listing is color-coded with valid command lines shown in blue and black, comments in green and invalid lines in olive. The line numbers refer to the physical lines in the command file, continuation lines will thus have line numbers as well, although they will be shown in yellow to indicate that they are continuation lines.
The start line is shown with yellow background. You can select another start line by typing a line number in the 'Start from line' entry or, more simply, by left-clicking on the line in the listing.
Another option available is to specify whether the command file should be run once, several times or indefinitely until stopped by the user.
It is not necessary to edit the command file if You want to exclude some lines in it. You can deactivate lines by right-clicking on them in the listing. Deactivated lines will appear grayed out and will be ignored during execution of the command file. Right-clicking a second time on a deactivated line reactivates it.
Three other command buttons are enabled while the command file is executing: 'Skip', 'Abort' and 'Stop'. The 'Abort' button will aborting the execution immediately and return control to the observer. The 'Stop' button will stop the execution more gracefully by allowing the current command or observing loop to finish before stopping the execution. These buttons have the same funtion as the 'Abort' and 'Stop' buttons on the CIMA observation log display. The 'Skip' button, however, is different. The 'Skip' button works like the 'Abort' button in the sense that the current line is aborted immediately. However, after aborting the current line, CIMA will continue with the next line in the command file, thus skipping the line that was executed when You pressed the 'Skip' button.
When the command file stops executing there will be a big "bong" (only for on-site observers) and control will be returned to the observer. If the command file terminated normally, the original start line will be restored. However, if the execution was terminated by an 'Abort' or 'Stop' command or by an error, the command line where the termination came will be indicated by a red background and the following line will be selected as the new start line. Lines that are skipped with the 'Skip' command will also be indicated with a red background.
#' is also ignored,
and '#' can thus be used to
provide comments or to comment out lines of code. NOTE though
that this only applies to the first character on the line! A
'#' anywhere else in a line -
even if it just preceeded by spaces - will be considered part of a
command!
ON cal=hcorcal dur=2 loop=1 dop=each dopl=each adjpwr=firstNOTE thus that NO lines, except continuation lines, can begin with white space!
Some commands take one or more direct
options. For those commands the option value is given directly.
For example, the CATALOG command expects one direct option
specifying the name of the catalog file to use:
CATALOG monkeys.catHowever, many commands instead use specified options. Specified options removes the requirement that options are given in a certain order. They are also remembered so they do not need to be repeated unless they are changed. A specified option has the following general syntax (white space is allowed):
name = valuewhere
name is the name given in lowercase and
value is the new value for the option. Multi-word
values can be specified by using {}-brackets or ""-signs. The
following are some examples of valid assignments of specified options:
calsecs=5
calmode=loopend
caltype = "hcorcal"
calwhen= {top and bottom of each}
In the following example, the first ONOFF is taken with the default
settings for all ONOFF options, while the second ONOFF is taken
according to the new options given. The third ONOFF is taken with the
same settings as the second ONOFF since the last assigned values for
all specified options are remembered. The fourth ONOFF also uses the
same settings as the second ONOFF with the only exception being the
number of loops that have been changed to five:
ONOFF ONOFF loop=1 dur = 2 cal= "hcorcal" ONOFF ONOFF loop = 5Specified options are independent for each observing mode. The second ONOFF in the following example will thus use an integration time of 3 minutes since that was the last value specified for ONOFF-observations while the second ON observation will use an integration time of 1 minute:
ONOFF dur=3 ON dur=1 ONOFF ONSpecified options can be set up with the
SETUP command which takes an observing
mode as its first argument and then a list of specified options
belonging to that particular observing mode. The SETUP command allows a cleaner way of
writing command files where the options can be separated from the
actual observing commands. The following two examples are, however,
equivalent:
# Example 1 ON dur=2 loop=5 cal="hcorcal" ON
# Example 2 SETUP ON dur=2 loop=5 cal="hcorcal" ON ON
IF conditional THEN commandwhere
command is any valid
command from the list below and conditional is a valid Tcl/Tk
expression. Tcl/Tk accepts the following comparison operators: '==', '!=', '<', '<=', '>' and '>=' as well as
the following logical operators: '&&' for
AND, '||' for OR and '!' for NOT.
The most typical application for a conditional test is to check what
to do depending on the current LST. The conditional can thus include the word
LST (case doesn't matter)
which will be converted to the current LST. Any number given as a
comparison to LST should be a
time given either as decimal hours (23.955) or using hhmmss[.ss]
notation (235718.0). The LST will be automatically wrapped to avoid
problems at LST midnight roll-over - thus, the conditional LST < 001000 will evaluate as TRUE if the
current LST is 23:55, while LST >=
013000 will evaluate as FALSE at the same LST. The
following example will move the telescope to the source
baboon if
the current LST is within the range 23:30:00 and 00:15:42
IF lst >= 23.5 && LST<001542 THEN SEEK baboonFor more examples of command files, see the bottom of this page.
Name receiver
"Carriage House 430/47" ch
"327 MHz" 327
"430 MHz" 430
"610 MHz" 610
"L-Band Wide" lbw
"S-Band Low (wide)" sbw
"S-Band Radar" sbn
"S-Band High" sbh
"C-Band" cb
"C-Band High" cbh
"X-Band" xb
"S-Radar transmitter horn" sbtx
"ALFA" alfa
receiver, tsys
and stay can be given either in uppercase
or in lowercase
Velocity frame Velocity type T[opocentric] v[elocity(optical)] G[eocentric] zo OR z(optical) H[eliocentric] zr OR z(radio) L[SR]
Apply' --- note
that this command may load the configuration for the back-end but it
does NOT apply it!
skyangle = 0.0 sky angle in degrees type = specified tracking type: "specified" or "equal" trackrate = 10 update rate in seconds maxdev = 2 max sky angle deviation in degrees method = both tracking method: "rate", "deviation" or "both" limithit1 = stay limit action: "stay", "wrap_60" or "wrap_180" limithit2 = stop limit action: "keep", "stop" or "abort"
caltype = nocal calibration type or "nocal" calduration = continuous calibration duration: "continuous" or "25Hz"
caltype = hcorcal calibration type or "nocal" calmode = onoff calibration mode: "onoff" or "on" calsecs = 5 calibration time in seconds
cal = hcorcal calibration type or "nocal" dur = 1 duration of scan in minutes loop = 1 number of loops dop = each when to update Doppler: "never", "first" or "each" dopl = each how to Doppler correct: "each" or "NAME:FREQ" adjpwr = first when to adjust power: "never", "first" or "each"
cal = hcorcal calibration type or "nocal" dur = 1 duration of scan in minutes loop = 1 number of loops wait = 1 wait time between ON and OFF in minutes dop = each when to update Doppler: "never", "first" or "each" dopl = each how to Doppler correct: "each" or "NAME:FREQ" adjpwr = first when to adjust power: "never", "first" or "each"
loops = 1 number of loops adjpwr = first when to adjust power: "never", "first" or "each" caltype = hcal calibration type or "nocal" calsecs = 5 calibration time in seconds length = 6 scan length in beams secs = 60 scan time in seconds rotang = 0.0 ALFA rotation angle in degrees beams = "0 1 2 3 4 5 6" list of beams to use (one cross on each) ncross = 4 type of cross: 2 (cross) or 4 (spider)
az = 180.0 azimuth in degrees
source = none source name or "none"
epoch = J coordinate epoch: "J", "B" or "Apparent"
ra = 000000.0 source RA in hhmmss[.s] notation
dec = +100000.0 source DEC in ddmmss[.s] notation
velocity = 0.0 source velocity in km/s
velframe = Topocentric velocity frame: "Topocentric", "Geocentric",
"Heliocentric" or "LSR"
rotang = 19.0 ALFA rotation angle in degrees
drifttype = truly type of drift: "truly" or "follow" (Dec J2000)
secs = 60 scan time in seconds
loops = 1 number of loops
fitswhen = 1 number of loops written per FITS-file
calmode = loopend-ON+OFF calibration mode: "loopstart-ON", "loopstart-ON+OFF",
"loopend-ON", "loopend-ON+OFF" or "async"
caltype = hcal calibration type or "nocal"
extracal = no add extra calibration: "yes" or "no"
calsecs = 1 calibration time in seconds
calmult = 0 asynchrounous calibration time rate in seconds
adjpwr = first when to adjust power: "never", "first" or "each"
If source is set to "none",
then the values for source, epoch, ra and dec are ignored. Instead the values for the last
selected source is used. This allows observers to select a source with
SEEK or GOTO
without having to repeat those values when running FIXEDDRIFT --- NOTE, however, that FIXEDDRIFT changes those parameters when running,
so a new SEEK or GOTO command has to be issued before each call to
FIXEDDRIFT when run with source set to "none" --- the
velocity type is always "velocity(optical)".
"traditional" mode runs the
telescope in RA/Dec with a negative sidereal rate, while the the
"azza" mode runs in Az/ZA
coordinates --- basketweave observations use the following specified
options with defaults indicated:
source = none source name
ra = 000000.0 start RA in hhmmss[.s] notation
dec = +100000.0 start DEC in ddmmss[.s] notation
lst = 000000.0 start LST in ddmmss[.s] notation
rarate = 15 RA rate in arcsecs/sec
loops = 1 number of loops
secs = 60 scan time in seconds
declen = 2.0 DEC length in degrees
turntime = 13 turn around time in seconds
mode = traditional basketweave mode: "traditional" or "azza"
ncals = 1 number of calibrations
calwhen = "top and bottom of each" when to calibrate: "bottom of first",
"bottom of each", "top and bottom of each"
or "never"
calsecs = 3 calibration time in seconds
caltype = hcal calibration type or "nocal"
dop = never when to update Doppler: "never", "first" or "each"
dopl = each how to Doppler correct: "each" or "NAME:FREQ"
fitswhen = 1 number of loops written per FITS-file
NOTE that the mode option was introduced in
CIMA version 2.2. When mode is set to "azza", the
values for ra and rarate are ignored.
freqs = 1420 list of frequencies to use secs = 5 observing time in seconds loops = 1 number of loops caltype = hcal calibration type or "nocal"
calmode = onoff calibration mode: "onoff" or "on" calsecs = 5 calibration time in secondsNOTE that the calibration type is set up with the PULSARCAL command.
calsecs = 10 calibration time in seconds offset = 4 offset to go off source in units of HPBW
source = none name of source to observe
secs = 10 scan time in seconds
skyangle = 0 ALFA sky angle (only for ALFA)
timeoffset = 0 offset in seconds added to current LST when
calculating the sky angle (only for ALFA)
The option timeoffset is used to specify the
time for which the sky angle should be calculated counted as
seconds after the start of the scan. A value of zero indicates that
the sky angle should be set correctly for the beginning of the
scan. A typical use is to set it to half the value of the scan time in
order to have ALFA set to a sky angle that corresponds to the
mid-point of the scan.
source = none name of source to observe
secs = 240 scan time in seconds
calsecs = 10 calibration time in seconds
offsetsize = 4 cal offset in the unit given in 'offsetunit'
offsetdir = north cal offset direction: "north", "south",
"east" or "west"
offsetunit = beamwidths 'offsetsize' unit: "arcminutes" or "beamwidths"
skyangle = 0 ALFA sky angle (only for ALFA)
timeoffset = 0 offset in seconds added to current LST when
calculating the sky angle (only for ALFA)
The option timeoffset is used to specify the
time for which the sky angle should be calculated counted as
seconds after the start of the scan. A value of zero indicates that
the sky angle should be set correctly for the beginning of the
scan. A typical use is to set it to half the value of the scan time in
order to have ALFA set to a sky angle that corresponds to the
mid-point of the scan.
EXEC relies on the internal CIMA
syntax which may change without warning!
GOTO commands are used instead
of SEEK commands to allow the
ALFA rotation to take place in parallel with the slewing of the
telescope. The WAITTRACK
command is not needed since the ON observations don't start until the
telescope has reached the source.
# Command file example RECEIVER alfa LOADIF monkey_config.gui WAPPCONFIG CATALOG monkey.cat GOTO baboon SKYANGLE 0 ON cal=hcorcal dur=2 loop=1 dop=each dopl=each adjpwr=first NEWFITSFILE GOTO gorilla SKYANGLE 0 ON cal=hcorcal dur=2 loop=1 dop=each dopl=each adjpwr=first # End of programIn this example, the
SETUP
command is used to set-up all options for ONOFF observations. There is
a shorter calibration observation on the bright source gorilla which only requires 1-minute
integrations, so the following ONOFF has to restore the longer
integration time required for the other sources. GOTO commands are used instead of
SEEK since ONOFF observations don't start until the
telescope is tracking. This actually saves a few seconds since the
check if the telescope is tracking is done once instead of two times.
# Example using SETUP CATALOG monkey.cat SETUP ONOFF loop=1 dur=5 wait=1 cal="hcorcal" SETUP ONOFF dop="each" dopl="each" adjpwr="first" GOTO baboon ONOFF GOTO chimpanzee ONOFF GOTO gorilla ONOFF dur=1 GOTO orangutang ONOFF dur=5 GOTO mandrill ONOFFThe next example illustrates the use of conditional commands as well as the
SETUP command. It
consists of two scripts. The first one is a general script which
select ALFA and sets up the system for basketweaving. This script is
intended to be run at the start up of each observing session and sets
up all basketweave parameters that are not going to change. The second
script contains the actual data taking commands. This script is
different for each session and uses conditional commands to select
where to take the data based on the current LST using positions given
in the catalog-file baboon.cat.
# Script 1 # Basketweave general set-up script RECEIVER alfa LOADIF monkey_config.gui WAPPCONFIG ADJUSTPOWER NEWFITSFILE CATALOG baboon.cat SETUP basketweave rarate=15 loops=5 secs=180 declen=1.5 turntime=13 ncals=1 SETUP basketweave calwhen="top and bottom of each" calsecs=5 caltype=hcal SETUP basketweave dop=never dopl=each fitswhen=1 # Script 2 # Basketweave session script with conditional commands IF lst < 235500 THEN SEEK baboon_2355 IF lst < 235500 THEN BASKETWEAVE source=baboon_2355 ra=234202 dec=+120342.1 lst=235515 IF lst < 235800 THEN SEEK baboon_2358 IF lst < 235800 THEN BASKETWEAVE source=baboon_2358 ra=234722 dec=+120513.7 lst=235815 IF lst < 000100 THEN SEEK baboon_0001 IF lst < 000100 THEN BASKETWEAVE source=baboon_0001 ra=235133 dec=+120759.0 lst=000115The following script is a calibration script to run two loops of smart frequency switching. It is supposed to run after another observation and in order not to waste time it uses the TRACKCURPOS command to ask the telescope to track the position it is currently commanded to. The script automatically selects the ALFA receiver, rotates it to 19 degrees and configures the WAPPs before the observation. The RECEIVER command uses the stay option to avoid having the telescope trying to retrack the last commanded source, which may be far away on the sky if the last observation was a drift observation.
# Smart frequency switching stand-alone calibration script
RECEIVER alfa stay
LOADIF monkey_config.gui
WAPPCONFIG
TRACKCURPOS
ALFAANGLE 19
ADJUSTPOWER
NEWFITSFILE
SMARTFREQ freqs = {1415 1420 1425} secs = 10 loops = 2
The final example illustrates an ALFA pulsar observation where a
series of pulsars from the catalog
orangutang.cat are observed for 150 seconds
each. The sky angle is set to be 45 degrees at the mid-point of each
scan. ALFA has already been selected and the WAPPs have been
configured from the normal pulsar menu. There is a calibration done on
the source monkey and another one done on
the source mandrill just after it has been
observed.
# Pulsar observations CATALOG orangutang.cat STARTPULSAR caltype=hcal calduration=continuous ALFABEAM 0 SEEK monkey PULSARCAL calmode=onoff calsecs=10 SETUP pulsarcatobs secs = 150 skyangle = 45 timeoffset = 75 PULSARCATOBS source = baboon PULSARCATOBS source = gorilla PULSARCATOBS source = mandrill PULSARCAL
You can return to the main CIMA page by clicking here.