-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathskedf.ctl.example
228 lines (226 loc) · 7.83 KB
/
skedf.ctl.example
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
***********************************************************************
* skedf.ctl - sked/drudg program control file
*
* This file is free-field except for section names which must begin
* in column 1 with a $. Either upper or lower case is OK for section
* names. Remember that path and file names in Unix are case-sensitive.
* Some sections are used by sked, some by drudg, and some by both.
* Edit or un-comment the lines that you need.
*
* sked and drudg read two versions of this file. The first version is
* the system control file which is read from a path specified at
* compile time. The second version is read from the user's local area.
* Any items in the local area control file override those in the
* system control file.
***********************************************************************
*
$mysql
host localhost
user oper
password aim!burst!shower!0
database vlbi
port 0
flag 0
$catalogs
* Note: The $catalogs section is used by sked but not by drudg.
* Please do not edit the first word on the line because these are key words.
*
***** OBSOLETE *********************
* Catalog program path:
* Enter here the absolute path where the java catalog class files reside.
* Example:
program /box3/skedv/catalogues
parameter /box3/skedv/parameters
****** END OBSOLETE ***************
*
master /500/oper/master
*
* Default catalog directory. If absent, assume full path.
cat_dir /space/sked/sked_cat
* Enter on the next lines the paths for sked's catalog files.
* Examples:
source source.cat.geodetic.good
hdpos hdpos.cat
flux flux.cat
comments flux.cat.comments
antenna antenna.cat
position position.cat
equip equip.cat
mask mask.cat
loif loif.cat
freq freq.cat
modes modes.cat
rx rx.cat
tracks tracks.cat
rec rec.cat
modes_description modes_description.cat
* CAN also give full path name for a catalog, EG:
*source /home/ftp/pub/sked/catalogs/source.geodetic_2007apr.cat
*flux /home/ftp/pub/sked/catalogs/flux.geodetic_2007apr.cat
*
$schedules
* Enter the path name for schedule (.skd) files. If not specified,
* the default is null, i.e. use the local directory. Both sked and
* drudg look for schedules in this path.
* Example:
*/home/jmg/schedules/
*/usr2/prog/
*
$snap
* Enter the path name for reading or writing SNAP (.snp) files. If
* not specified, the default is null, i.e. use the local directory.
* This is used by drudg.
* Example:
*/usr2/sched/
*
$proc
* Enter the path name for writing procedure (.prc) files. If not specified,
* the default is null, i.e. use the local directory.
* This is used by drudg.
* Example:
*/usr2/proc/
$scratch
* Enter the path name for temporary files. If not specified, the default
* is null, i.e. the files will be written into the local directory.
* This is used by both sked and drudg.
/tmp/
*
$print
* Printer type:
* Enter the printer type for drudg. If not specified, default is laser.
* Recognized names: laser, epson, epson24.
* This can be changed interactively with option 9.
* Examples:
* printer laser
* printer epson
* printer epson24
*
* Printer type:
* Enter any command strings or scripts to be used for printing in
* portrait or landscape. The key words "landscape" and "portrait"
* indicate the orientation. Following the key word, all characters
* on the line (including blanks) are read as the command.
* If no commands or scripts are specified, drudg defaults to embedding
* escape sequences for the output desired into the file and uses
* the system command "recode latin1:ibmpc" piped to "lpr" to print
* the temporary file.
* Examples:
* This example is for a laser printer, 6 lines/inch, 10 char/inch:
*portrait lpr -ofp10 -olpi6 $*
* This example is the same as above but for landscape:
*landscape lpr -ofp10 -o1pi6 -olandscape $*
* These examples are the same as above but for a smaller font:
*portrait lpr -ofp16.66 -olpi6 $*
*landscape lpr -ofp16.66 -o1pi6 -olandscape $*
*portrait <script name for portrait output>
*landscape <script name for landscape output>
*
* Output control:
* Enter the desired orientation and font size for listings. Key words
* are option1, option4, and option5 for the three listing options.
* Follow the key word by a 2-letter code, first letter "p" or "l" for
* portrait or landscape, second letter "s" or "l" for small or large
* font. If none are specified, the defaults are as listed below:
*option1 ls (landscape, small font)
*option4 ps (portrait, small font)
*option5 ps (portrait, small font)
*
* Tape label script:
* Enter a script for printing tape labels. If no script is specified,
* the default is to use "lpr" to print the temporary file.
* Examples:
*labels <script name for label printing>
*
* Tape label printer:
* Enter the name of the label printer. If no name is specified, drudg
* will not attempt to print tape labels. Recognized names are postscript,
* epson, epson24, laser+barcode_cartridge.
* Examples:
*label_printer postscript
*label_printer laser+barcode_cartridge
*label_printer epson
*label_printer epson24
*
* Label size:
* Specify label size parameters, only valid for "postscript" type. If
* no size is specified, drudg cannot print labels.
* The option that has the largest product of <rows>*<cols> is a good choice
* if you are just printing to plain paper, for example Avery 5160 prints 30
* labels per page.
* <ht> height of a single label, in inches
* <wid> width of a single label, in inches
* <rows> number of rows of labels on the page
* <cols> number of columns of labels on the page
* <top> offset of the top edge of the first row of labels from the
* top of the page, in inches
* <left> the offset of the left edge of the first column of labels
* from the left side of the page, in inches
* Format:
* label_size <ht> <wid> <rows> <cols> <top> <left>
* Examples:
label_size 1.0 2.625 10 3 0.5 0.3125 Avery 5160
*label_size 1.333 4.0 7 2 0.5 0.25 Avery 5162
*label_size 2.0 4.0 5 2 0.5 0.25 Avery 5163
*label_size 1.5 4.0 6 2 0.75 0.25 Avery 5197
*label_size 1.375 2.75 8 3 0.0 0.0 HP 92285L
*label_size 1.5 3.9 7 2 0.5 0.16 Avery L7163
*
$misc
*
* Epoch:
* Enter the epoch for drudg to use on the SOURCE commands in SNAP files.
* Default is 1950 if none is specified. Only 1950 or 2000 are valid.
* Examples:
*epoch 2000
epoch 1950
*
* Station equipment:
* Station equipment may be specified in drudg. Equipment names are
* case sensitive. Allowed rack and recorder names are:
*
* Racks | Recorders
* -------- | ---------
* none | none
* Mark3A | Mark3A
* VLBA | VLBA
* VLBA4 | VLBA4
* Mark4 | Mark4
* VLBA/8 | S2
* VLBA4/8 | K4-1
* K4-1 | K4-2
* K4-2 | unused
* K4-1/K3 |
* K4-2/K3 |
* K4-1/M4 |
* K4-2/M4 |
*
* Relationship between skedf.ctl and equip.ctl file names:
*
* skedf.ctl equip.ctl
* (and VEX files)
* --------------- --------------------------------------
* Mark3A mk3 mk3b
* VLBA vlba vlbag
* VLBA/8 vlba vlbag (8 BBCs only)
* VLBA4/8 vlba4 (8 BBCs only)
* Mark4 mk4
* VLBA4 vlba4
* K4-1/K3 k41 k41u k41/k3 k41u/k3
* K4-2/K3 k42 k42a k42bu k42/k3 k42a/k3 k42bu/k3
* K4-1/M4 k41 k41u k41/m4 k41u/m4
* K4-2/M4 k42 k42a k42bu k42/m4 k42a/m4 k42bu/m4
* K4-1 k41 k41/dms
* K4-2 k42 k42/dms
* S2 s2
*
* If the schedule file does have equipment specified, then the
* equipment in the schedule file will be used.
* If the schedule file does not have equipment specified, then the
* equipment in the control file will be used.
* A warning message is issued if the control file and schedule file
* equipment are different.
* Format:
* equipment <rack> <recorder A> <recorder B>
* Examples:
* equipment Mark4 Mark4 none
* equipment VLBA VLBA VLBA