| Processing
Observe Files:
Open a Banshee window
Check your current directory;
at the prompt type pwd <CR>
Your current directory should
be /home/banshee/observe/to.be.fetched/
If your current directory
is not as shown above, change to that directory by typing cd
to.be.fetched
Run the script that processes
the observe files (New Fetch) by typing newfetch <CR>
You will see a screen with
the following prompt:
Welcome to newfetch version 2.1
Please enter your choice: soundbytes
(s), beeps (b), or no sound (n).
Choose your preference by
typing the appropriate letter s, b, or n <CR>
A numbered list of the email
messages will be displayed
Open the desired email message
either by hitting the “Return” key (to get the first message in the list)
or by entering the number of the message
When you have the file open,
make note of the following information contained in the first several lines
of the email:
Program name (AP401
on line 1 in figure 1 below)
Day the file is to be run
(58,516 on line 4 in figure 1 below)
Starting time of the file
(23 00 00 on line 4 in figure 1 below)
FIGURE 1
1 /.AP401 2180
2 //* ***
3 //* *** NRAO VLA Observe Program
4 //* *** Observation day 58,516 at 23 00
00 LST, 2000.09.15 23:28:MST.
5 //* ***
6 //* *** Observer
7 //* *** D.J. Pisano
Phone
8 //* *** UW – Madison
Office: 608-262-2965
9 //* *** Astronomy Dept. During
Observation:
10 //* *** 475 N. Charter St.
11 //* *** Madison, WI 53706
12 //* ***
13 //* *** E-Mail address
14 //* *** pisano@astro.wisc.edu
15 //* ***
16 //* *** Observing Mode (s) : line
You will compare this information
with that reflected on the Observe Schedule to make sure that the file
has the correct day and starting time.
In addition, you will want
to check that the ending time of the file is the same as it is on the Observing
Schedule. To quickly jump to the end of the email where the ending time
is, hold down the shift key and type the letter g shift
+ g
Ending time (05 00 00 on
line 125 in figure 2 below)]
FIGURE 2
124 //FISZTB
1507.000
1507.000 1420.405752 1420.405752
125 0137+331 2 05 00 00 01 37 41.2995
+33 09 35.134C LL A 4444
16.50
126 //DS 1A H 30
7 0 7 0
7 0 7 0
127 //LO -3.2 -3.2
3590 3590
0000
128 //FISZTB
2131.000 2131.000 1420.405752
Whether or not all of the
information checks out, that is to say, whether or not the file is the
correct program to run during the appropriate time frame on the appropriate
day as reflected on the Observing Schedule, you will continue through the
steps to process the file. If there is a discrepancy in any of the information,
make a note to yourself to check into it further after you have gotten
the hard copy of the observe file at the end of the New Fetch procedure.
Jump back to the top of the
email message by typing the letter g
Close the email message
by typing the letter q <CR>
Save the email message by
typing the letter s <CR>
Rename and save the email
message with the command s filename , using the following
naming convention: dddx###.tmp
Where “ddd” refers to the
last three digits of the five-digit sidereal day number;
“x” is the second letter
of the two letters of the program name;
“###” refers to the
three numbers of the program name
FIGURE 3
1 /.AP401 2180
2 //* ***
3 //* *** NRAO VLA Observe Program
4 //* *** Observation day 58,516 at 23 00 00 LST,
2000.09.15 23:28:MST.
For example, using the information
in figure 3 above, the filename would be 516P401.tmp
There are a few exceptions:
1) If you receive a revised
version of a file that has already been processed and named, or if a particular
program will be running more than once in the day, just add the letter
“A” (or B, C, D etc) at the end of the filename: i.e 516P401 exists,
so name the new file 516P401A.tmp
2) VLBI programs will have
a B in the name, eg. BR552. In this case, keep the letter b in the filename:
517BR552
3) You may see an unusual
program name such as TEST. You can name the file 516TEST, or 516PTST
where "P" is the first letter of the last name of the observer (see Figure
1, line 7 to see the observer's name location in the file).
After the file has been renamed
and saved, you will want to email the observer to acknowledge receipt of
the file.
To reply, at the prompt
type the letter r <CR>
Usually the “Re:” field
is filled automatically; if not, enter Observing File “Name” & hit
<CR>
You will skip to the "CC:"
field; enter analysts <CR> (this is not necessary if the file
came from the analysts!)
To insert the stock response
in the body of the email, type shift + ` (a tilda ~)
followed by the letter r, a space, obsrep.txt &
hit <CR> (the command will look like this: ~r
obsrep.txt)
Skip a few lines by hitting
<CR> a few times, then enter your own name & hit <CR> to advance
to the next line
To close and send the message,
type a period ( . ) in the first position on the line, then hit
<CR>
You will be returned to
the mail prompt
If you have more than one
observe file to process, open the next file at this time by hitting the
Enter key (this will take you to the next message in the list) ob by entering
the number of the message.
To see the list of email
messages again, type the letter h <CR>
Process any remaining observe
files in the method described above.
Occasionally new mail will
come in while you are in the midst of the New Fetch process. You are able
to include these new files in the process by typing the command, inc
<CR>
If any of the new email
messages are observe files, process them in the manner described above
If the messages are informative
email messages, be sure to print them in the manner described earlier
After all of the files have
been processed, quit the mail program with the quit command; type q
<CR>
Quitting the mail program
will initiate the next portion of the New Fetch process.
You will see the following
information in Figure 4 appear on the screen:
FIGURE 4
newfetch starting script: startfetch
Archiving observe files.
Moving 516p401.OBS to observe/obsArchive.
Moving 516p401b.OBS to observe/obsArchive.
Moving *.OBS.orig to observe/obsArchive.
End of script: endfetch.
Moving to /home/banshee/observe/to.be.fetched.
Removing the old PUTFILES.MC file
Turning off messages to this terminal while you are working.
Starting the mail program... See ya later!
FIND WHAT GOES HERE!!!!!! (if no mail, message is:
No mail for observe)
Starting cleanObsFiles...
Cleaning up all the .tmp files in the /home/banshee/observe/to.be.fetched.
FIND WHAT GOES HERE!!!! (if no mail, message is: There
are no *.tmp files in the directory!)
Turning messages back on to this terminal.
End of script: startfetch.
FIND WHAT GOES HERE!!!
(If no files
EXITING, It appears there are no fetched email files to process
at thtis time.
ENDING newfetch!
will return to prompt)
Next you will see the prompt
displayed below in Figure 5:
FIGIRE 5
Would you like to double check each of the files you just retrieved
for correct AIPS USER NUMBERS? (y/n)
You will answer yes to this
prompt by typing the letter y <CR>
The information shown in
Figure 6 below will appear:
FIGURE 6
Col Format Description
1-2 /.
Identifies indentification card.
3-8 A6
PROGRAM CODE (P.C., up to 6 characters ending in col 8, ie AA123)
9-13 I4 AIPS
USER NUMBER (AUN, ending in col 13)
Numbers 0-10 are reserved. General User is 20
14 $
24 HOUR PROGRAM
FILENAME: 516p401.OBS
0 1
12345678901234
||| || ||
vvv vv vv
/.AP401 2180
^^^ ^^ ^^
||| || ||
/. P.C. AUN $ TO BE LEFT BLANK TO END OF LINE
Is this Correct ? (y/n)
If the information is correct,
type the letter y <CR> to continue.
If the information is not
correct (eg. the program code does not fall within the proper column range,
or the AIPS user number is 10), type the letter n <CR>
You will then be given the
opportunity to enter the information correctly as diplayed beloew in Figure
7.
FIGURE 7
GET WORDING FOR CHANGE SCREEN
After the information above
has been verified as being correct, the information illustrated in Figure
8 below will appear:
FIGURE 8
Starting CHKFILES script version 1.2.0
Cleaning up from last session
Compressing postscript files.
Then placing them in /home/banshee2/obs.ps.files
COMPRESSING 516P401
ARCHIVING 516P401
COMPRESSING 516P401A
ARCHIVING 516P401A
Saving last OPCHK Log to:
/home/banshee/observe/to.be.fetched/fetch.stuff/opchk.last
Please enter you initials:
Enter your initials at the
prompt and hit <CR>; the program will continue and display the information
in Figure 9:
FIGURE 9
Opening an xterm for a telnet session to MONTY.
At the observe prompt of the newly opened xterm type: telmonty
At the MONTY prompt type the following MODCOMP instructions:
<NOTE: You may want to cut and past the entire MODCOMP
instruction
set that follows
with the mouse from this window to the MONTY
prompt in the
xterm that just opened.)
RUN TEL
JOB
OPSED
E
JOB
GETOBS !NoDurPls
JOB
OPCHK 516P401 LO
JOB
how does more than one file look???
DIE
As suggested by the script,
the easiest thing to do is to copy the text block starting with the line
"RUN TEL" and pasting it into the MONTY window that appears on the right-hand
monitor (see Figure 10).
To select the text block,
place the mouse cursor to the immediate left of the letter "R" in the word
RUN on the first line. Click once with the left mouse button and while
keeping the mouse button depressed, move the mouse cursor to the immediate
right of the letter "E" in the word DIE on the last line, then release
the mouse button. The block of text should be highlighted, with the last
of the dark highlighted area ending on the line below the word DIE.
To paste the text into the
MONTY window (Figure 10), simply move your mouse cursor to the body of
the window to the right of the prompt and single-click the MIDDLE mouse
button. The text will be pasted into the window, and the script will continue.
(The window illustrated in
Figure 9 will remain open while the file processing occurs; therefore
it is best to move the window to the bottom of the monitor screen so as
not to block the operations windows.)
FIGURE 10
Trying 146.88.201.18...
Connected to 146.88.201.18.
Escape character is '^]'.
MODCOMP Telnet Server -- SYS V/68
MONTY>
The length of time it takes
to process the file(s) depends upon the number of files being processed.
During this time lots of text will scroll through the window. Since this
process can take many minutes, it is wise to move the MONTY window to the
bottom of the monitor screen so it doesn't block other operations windows
that would be open.
When all of the files have
been processed without any errors occurring, the MONTY window will
automatically close, and the information in Figure 11 will displayed in
the banshee window in the left-hand monitor:
(If there are errors and/or the script crashes, skip to the directions
here)
FIGURE 11
Parsing 516P401 from opchk.log Opening file:
516P401.pre
File Parsing Complete. Converting to postscript
Preparing coversheet for: 516P401
request id is vla-hpd-447 (1 file)
Printing the cover sheet for: 516P401
request id is vla-hpd-448 (1 file)
Printing the observe file for: 516P401
newfetch: End of Script
banshee<observe>%
WHAT DOES IT LOOK LIKE FOR MORE THAN ONE FILE?
Checking the Printed Observe
File:
After the observe file has
printed, there are several things that must be checked.
Subarray
Fluke
Check off times
Special instructions?
Checklist
Tipping scans?
Need to show cover sheet
and short version of objects to show special scan modes.
Figure ##
Cover sheet
Blah blah blah
Figure ##
File illustrating tipping scans
Blah blah blah
What to do in case of
crashes:
CTRL+ C out of banshee window
Pick up scripts at appropriate
time
How to edit file using
Emacs:
In a Banshee window:
> emacs filename.OBS
Common commands:
ctrl+a
go to beginning of line
ctrl+e
go to end of line
esc+d
delete work
ctrl+p
display previous entry
Center mouse key will activate
scroll bar.
A straight save will save
the file to the proper directory.
How to edit .OBS file
using OPSED:
After making any changes
to an observe file, be sure to check the files. At Op3 terminal
$ JOB
$ FILECHK filename # (where
filename is the name of the file and # is the subarray)
Common Observe Files problems:
No space after comment
slashes |