-
Notifications
You must be signed in to change notification settings - Fork 4
/
Copy pathREADME
222 lines (188 loc) · 9.34 KB
/
README
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
Installation:
A few items are required to run tkmap:
1. GrADS. You can get the most recent version at http://cola.gmu.edu/grads/.
2. tkmap.sh. This script runs tkmap and creates all the necessary output. You must modify the last line of this script to point to GrADS.
3. An executable for tkmap (xtkmap). If you are on a mac, you can download this executable directly. Otherwise, you must compile the code (tkmap.f) using a fortran compiler to create the xtkmap file (example: gfortran -o xtkmap tkmap.f).
4. plotdrops.gs. This is a GrADS script that will plot the flight track.
5. Four files that allow GrADS to run (ens.ctl, ensc0.t00z.pgrbf00, ensc0.t00z.pgrbf00.gmp, ensc0.t00z.pgrbf00.idx).
6. Three files for plotting the locations of RAOB observations (stnlist00, stnlist12, stnlist0012).
Running:
This program creates three output files required by AOC to file a flight plan: a file of turn points, a file of drop locations, and a graphical version of these text files. The points can be input as latitude/longitude locations or by distance and direction from the center of the tropical cyclone. In the latter case, the program has the option of accounting for the storm motion during the flight. The total time of the proposed flight is calculated, with time added for each turn to allow for the added time necessary for that maneuver. The ground speed of the P-3s are calculated based upon the proposed height of the mission; the ground speeds of the other aircraft are constants.
To run the program, you will need to create an ascii file for each plane with the turn and drop locations for the flight (more on this shortly). The files must be in the directory in which the script resides and must be names currentX.ftk, where X is either 1, 2, or 3, depending upon the number of planes for the mission. If only one plane is to be used, neither current2.ftk nor current3.ftk can exist. [The code can be updated to account for more aircraft.]
The program will print two tables, one listing the turn points, and one with the drop points, with total distance and time to each, and the map. The tables will be called turnX.txt and dropX.txt, with X having the same meaning as above.
The input file is basically just a sequential list of lats, lons and altitudes. An example is given below. On the first line you must specify the aircraft and takeoff time (dd/hhmmZ).
42 - NOAA P-3: FL=5000:218kt; FL=6000:223kt; FL=7000:227kt; FL=8000:232kt; FL=9000:237kt; FL=10000:242kt; FL=11000:247kt; FL 12000:252kt; FL=14000:264kt; FL=18000:288kt; FL>=20000:300kt
43 - NOAA P-3: same as NOAA 42
49 - NOAA G-IV: FL=41000-45000:442kt
50 - AF C-130J: FL=18000-25000:290kt
51 - NASA DC-8: FL:18000-25000:350kt
52 - GLOBAL HAWK:FL=55000-60000:335kt
57 - NASA WB-57: FL>=60000:400kt; FL=55000:550kt; FL=50000:500kt; FL=45000:450kt; FL<=40000:300kt)
You may optionally include a title (like the storm or experiment name). On subsequent lines, the first character indicates what type of data follow.
The next line will have the location of the storm or target and its expected motion vector.
**NOTE**
the storm motion can be the motion at take-off time or if the storm is expected to accelerate during the mission, a mean storm motion can be used
**NOTE**
H Lat Lon Dir Spd
Follow the "H" by the lat and lon in decimal degrees at the time on the previous line (with north and west positive), then a motion vector (toward decimal degrees and speed in kt). So the first two lines of the input file might look like this:
49 07/1800Z Genesis
H 18.5 82.5 270 12
the storm position should be the position at the time of take-off…this is especially important if storm relative points are included in the track (see below)
The next line specifies the takeoff location. A city name (all CAPS) from the following list must be specified for take-off (A) and landing (Z):
City Name Location Latitude/Longitude
ANCHORAGE AK 61.18N 150.00W
ANDREWS Camp Springs, VA 38.81N 76.87W
ARMSTRONG Edwards AFB, CA 34.92N 117.87W
BARBADOS Barbados, WI 13.06N 59.49W
BERMUDA Bermuda 32.36N 64.68W
BOSTON MA 42.37N 71.01W
BRUNSWICK ME 43.90N 69.93W
CHARLESTON SC 32.90N 80.04W
CORPUS CHRISTI TX 27.77N 97.50W
CURACAO Curacao, Caribbean 12.18N 68.97W
EDWARDS Edwards AFB, CA 34.92N 117.87W
ELLINGTON Houston, TX 29.61N 95.16W
FT LAUDERDALE FL 26.07N 80.15W
GRAND CAYMAN Cayman Islands 19.29N 81.36W
HALIFAX Nova Scotia, Canada 44.88N 63.52W
HARLINGEN TX 26.22N 97.65W
HOMESTEAD Hoemstead AFB, FL 25.49N 80.39W
HONOLULU HI 21.30N 157.90W
JACKSONVILLE FL 30.23N 81.68W
KEESLER Biloxi, MS 30.41N 88.92W
LA PAZ Baja Mexico Sur, Mex 24.07N 110.36W
LAKELAND Lakeland, FL 27.99N 82.02W
LIBERIA Costa Rica 10.59N 85.54W
MACDILL Tampa, FL 27.85N 82.52W
MIAMI FL 25.79N 80.29W
NEW ORLEANS LA 29.99N 90.26W
OPA LOCKA FL 25.91N 80.28W
PORTSMOUTH NH 43.08N 70.82W
PROVIDENCE RI 41.73N 71.43W
ROBINS Robins AFB, GA 32.64N 83.59W
SAN DIEGO CA 32.85N 117.12W
SAN JOSE Costa Rica 9.98N 84.22W
SAN JUAN Puerto Rico 18.44N 66.00W
SAVANNAH GA 32.13N 81.20W
ST CROIX USVI 17.70N 64.80W
TAMIAMI Miami, FL 25.65N 80.43W
WALLOPS NASA Wallops, VA 37.93N 75.48W
What follows will be a sequential list of turn and drop points and altitudes, one on each line. The first character in each line indicates the type of point. Turn points (with no drops) are indicated by a "T". A blank in the first character (the default) means that the point is both a turn and a drop point. The location is specified by lat and lon.
You may also specify locations relative to the storm location (the "H" line in the file). This is done by specifying the storm-relative radius (nm) and azimuth (deg from N). The following example places sondes at 180, 135, 90, 60, and 30 nm from the center on the 330 degree azimuth, and then another sonde at the center, all at 8000 feet altitude:
S 180 330 8000
S 135 330 8000
S 90 330 8000
S 60 330 8000
S 30 330 8000
S 0 0 8000
Adding intermediate drop points between way points:
The following example will distribute evenly 4 sondes between the turns (and drops) at 15N 70.5W and 15N 60W (note that the flight level altitude must be included in the interpolate line and that these interpolated points are added to the dropsX.txt file, but not to the turnsX.txt file.
15 70.5 8000
I 4 8000
15 60 8000
The last line in the file indicates the recovery site. It must begin with a "Z". The same list of cities can be used, or specify the site by lat and lon.
Once the files are complete, type "tkmap.sh." The graphics will be written to the screen; if you wish to remove this capability, edit the file tkmap.sh and change "-l" in the last line to "-lb."
Running tkmap.sh will create the output files and the map. It should take just a couple of seconds. The output files will be ftk.png (graphics) and turnsX.txt and dropsX.txt, where N is the number from currentX.ftk. Check to make sure that the flight duration is within the limits (below) and that the graphics look fine.
Maximum P-3 Flight Durations (determined by landing site):
Bermuda: 8.0 hr (~2150 nm)
Barbados/St. Croix: 9.0 hr (~2400 nm)
Mainland: 9.0 hr (~2400 nm)
P-3 2015 engine upgrade allows for up to 11.0 hr (~2900 nm) nm)
11.0 hr flight consideration: slips in take-off time will result the following day (crew rest requirements)
Maximum G-IV Flight Durations (determined by landing site):
Bermuda: 7.5 hr (~3300 nm)
Barbados/St. Croix: 8.0 hr (~3500 nm)
Mainland: 8.5 hr (~3750 nm)
Maximum Global Hawk Flight Duration
All deployment sites: ~24.0 hr (~8,000 nm)
24.0 hr includes ~30 min for the initial climb out plus ~30 in for the final decent out of/back to NASA Armstrong/Wallops.
tkmap automatically adds 30-min & 167.5 nm to the track after take-off and after the last way point to account for these aircraft maneuvers
Sample current.ftk file #1:
49 07/1800Z Genesis
H 18.5 82.5 270 15
A MACDILL
24 83.5 20000
23 85.5 10000
21 85.5 10000
S 180 330 5000
S 135 330 5000
S 90 330 5000
S 60 330 5000
S 30 330 5000
S 0 0 5000
S 30 150 5000
S 60 150 5000
S 90 150 5000
S 135 150 5000
S 180 150 5000
S 180 90 5000
S 135 90 5000
S 90 90 5000
S 60 90 5000
S 30 90 5000
S 0 0 5000
S 30 270 5000
S 60 270 5000
S 90 270 5000
S 135 270 5000
S 180 270 5000
S 180 210 5000
S 135 210 5000
S 90 210 5000
S 60 210 5000
S 30 210 5000
S 0 0 5000
S 30 30 5000
S 60 30 5000
S 90 30 5000
S 135 30 5000
S 180 30 5000
19 77 10000
19 74.5 10000
21 73.5 10000
23 73.5 10000
24 77 10000
Z MACDILL
Sample current.ftk file #2:
42 23/2200Z
H 25.0 83.2 000 00
A MACDILL
S 105 0 12000
S 105 180 12000
S 105 135 12000
S 105 315 12000
S 105 270 12000
S 105 90 12000
S 105 45 12000
S 105 225 12000
S 105 180 12000
S 105 0 12000
Z MACDILL
Sample current.ftk file #3:
49 04/1730Z BONNIE
H 14.0 65.7 0 0
A ST CROIX
18.761 64.013 45000
17.786 62.542 45000
17.100 59.000 45000
18.067 57.058 45000
19.950 57.078 45000
20.068 58.942 45000
21.978 59.046 45000
23.003 61.004 45000
23.991 63.009 45000
24.000 65.004 45000
23.867 66.915 45000
22.002 66.093 45000
20.999 68.002 45000
19.865 69.838 45000
18.272 68.405 45000
17.089 69.355 45000
15.480 68.129 45000
14.894 69.928 45000
13.095 68.936 45000
14.162 67.486 45000
13.187 65.975 45000
13.161 64.099 45000
14.192 63.529 45000
Z BARBADOS