Instructions to produce swaths ============================== (notes taken from meeting with George Soukup, 9/5/2003) 1) Patience, a lot of patience. Long and tricky instructions. 2) # ssh username@cat5.nhc.noaa.gov (140.90.48.207) # mkdir Swath (or any name you like; this will be your working directory) # cd Swath # ls ~analysis For the sake of providing more understanding, the instructions use event 'Grace' as an example. 3) Identify the analysis directories relevant to your event. They are easy to spot because they are named like '200308310130Grace1430136135'. The pattern is 'yyyymmddHHMMeventnameRandomNumber'. You might find several directories for the same analysis time, but be sure to always pick the latest one generated. Easy way to display all concerned: # ls -ld ~analysis/*Grace* drwxrwxr-x 2 analysis 1536 Aug 31 09:03 200308301930Grace-97253484 drwxrwxr-x 2 analysis 1536 Aug 31 10:26 200308310130Grace1430136135 drwxrwxr-x 2 analysis 1536 Aug 31 11:28 200308310730Grace-1155723232 drwxrwxr-x 2 analysis 1536 Aug 31 11:37 200308310730Grace-1226693098 drwxrwxr-x 2 analysis 1536 Aug 31 11:14 200308311330Grace-1689390842 drwxrwxr-x 2 analysis 1536 Aug 31 10:08 200308311330Grace-1935978200 drwxrwxr-x 2 analysis 1536 Aug 31 09:22 200308311330Grace1262407253 drwxrwxr-x 2 analysis 1536 Aug 31 09:52 200308311330Grace1723282476 drwxrwxr-x 2 analysis 1536 Aug 31 08:30 200308311330Grace332699407 drwxrwxr-x 2 analysis 1536 Aug 31 09:42 200308311330Grace4869195 In this case, you would ignore one of the 0730z analyses and 5 of the 1330z analyses. 4) From every relevant directory, copy the file "enhanced_amp" to your working directory with a new name, 'ampfileNumber'. The convention is to follow a chronological order. Therefore, in this case: # cp ~analysis/200308301930Grace-97253484/enhanced_amp ampfile1 # cp ~analysis/200308310130Grace1430136135/enhanced_amp ampfile2 # cp ~analysis/200308310730Grace-1226693098/enhanced_amp ampfile3 # cp ~analysis/200308311330Grace-1689390842/enhanced_amp ampfile4 5) Create a file called 'anlyfile.dat' (without the -----------): ----------------- GRACE ... ANALYSIS LIST day hr min 1 19 30 2 1 30 2 7 30 2 13 30 --------------- This event spans over 2 days, August 30 and 31. The 1930z analysis occurred on day 1, and the rest on day 2. It can continue for any number of days. 6) Create a file called 'spexfile.dat': ------------------ GRACE ... landfall swath results ndg elod nlad min thresh dxyksw 4 -95.744 28.750 1 33.45 5. (XXMARE,YXMARE),(UXMARE,VXMARE) ( 174.650, 144.538)( -17.8136, 14.6307) day hr min 2 13 15 -1 00 00 -------------------- Line (1): Edit for correct event name Line (2), leave as shown: > ndg = number of degrees of coverage (default to 4) > elod, nlad = longitude, latitude coordinates of the center of swath domain, typically the same as the landfall coordinates. (Note the negative sign for longitude) > min = frequency of samples taken (in minutes). (default to 1 minute) > thresh = threshold; (default to hurricane strength, 33.45m/s). > dxyksw = resolution in km of swath domain (default to 5km) Line (3): values for above parameters Lines (4) and (5): Cut and paste lines 5 and 6 from the last of the 'ampfile*', in this case from ampfile4, which should correspond to the analysis closest to landfall. (XXMARE,YXMARE),(UXMARE,VXMARE) ( 174.650, 144.538)( -17.8136, 14.6307) Line (6): Leave as shown Line (7): relative day, hour and minutes of time of landfall. In this case, day 2 at 1315z. This time does not have to coincide with position or analysis times; you should enter values as accurate as possible. Line (8): Leave as shown 7) Create a file called 'trackfile.dat': ----------------- GRACE ... trackfile.dat eltcen nltcen -95.744 28.750 93.200 25.600 1 18 00 1 93.683 25.133 1 21 25 2 94.000 25.200 2 00 00 3 95.000 26.000 2 06 00 4 96.050 27.317 2 07 09 5 96.000 28.000 2 12 00 6 95.744 28.750 2 13 15 7 95.400 29.760 2 14 56 8 94.706 31.690 2 21 00 9 ----------------- Line (1): Edit for correct event name Line (2): Leave as shown Line (3): Landfall lon, lat coordinates (Note the negative sign for longitude) They might or might not be the same as the coordinates in 'spexfile.dat' Rest of lines: Smooth track without kinks. It MUST include positions of the forecast track beyond landfall (George thinks they are given in landfall advisory from NHC) In the past, Shirley provided George with the tracks. Her philosophy and tips: a) Run H*Wind b) Load all ATCF and Vortex positions for approx. the last 2 days prior to landfall c) Remove fixes with abrupt directions TIP: Instead of clicking on "Update Map", zoom-in and zoom-out, which will refresh the map avoiding the process of checking for new data. d) export the track (Top menu: QC Set->Export->Storm Track File) e) edit the exported track to adapt to above pattern. Replace the last column of the exported track file with an enumeration of fixes; replace the dates with the relative day number, and separate hours and minutes values. Longitudes are positive numbers. WITHOUT CENSUS DATA ------------------- 8) # ~analysis/Programs/IDLSwath/idlSwath.sh 9) The final output file will be called 'swathco.ps', which contains 5 images: - maximum wind contours (mph) - maximum wind contours (m/s) - maximum wind contours (knot) - steadiness - duration The associated gridded file will come in the future. Waiting for George Soukup. WITH CENSUS DATA ---------------- 8) Prepare file 'census.idl' (zipcode file): # ls ~analysis/Programs/IDLSwath/Census/ alaba3.txt.gz census19.idl.gz census_FL.idl.gz mryld14.txt.gz census.idl.gz census2.idl.gz concensus.m.gz nhamp21.txt.gz census1.idl.gz census20.idl.gz connt16.txt.gz nthca8.txt.gz census10.idl.gz census21.idl.gz delaw11.txt.gz nyork19.txt.gz census11.idl.gz census22.idl.gz distc10.txt.gz penns15.txt.gz census12.idl.gz census3.idl.gz flori6.txt.gz rdcensus.m.gz census13.idl.gz census4.idl.gz georg5.txt.gz rhode17.txt.gz census14.idl.gz census5.idl.gz jersy13.txt.gz sthca7.txt.gz census15.idl.gz census6.idl.gz louis2.txt.gz texas1.txt.gz census16.idl.gz census7.idl.gz maine22.txt.gz virgn9.txt.gz census17.idl.gz census8.idl.gz massc18.txt.gz vrmnt20.txt.gz census18.idl.gz census9.idl.gz missi4.txt.gz wvirg12.txt.gz Interpretation: "*.txt.gz" represent states. George has prepared the corresponding IDL files matching by number. For example, for Grace, we would pick "census1.idl.gz" because it corresponds to "texas1.txt.gz". For Florida, it would be census6.idl.gz. ONE U.S. STATE involved ----------------------- Copy the appropiate file to your working directory with the name 'census.idl.gz' # cp ~analysis/Programs/IDLSwath/Census/census1.idl.gz census.idl.gz # gunzip census.idl.gz MULTIPLE U.S. STATES involved ----------------------------- Basically, need to concatenate various census#.idl.gz files. For example, let's assume there are 4 states involved, involving files census5.idl.gz, census8.idl.gz, census10.idl.gz and census13.idl.gz. 8.1) Copy them to your working directory. # cp ~analysis/Programs/IDLSwath/Census/census5.idl.gz . # cp ~analysis/Programs/IDLSwath/Census/census8.idl.gz . # cp ~analysis/Programs/IDLSwath/Census/census10.idl.gz . # cp ~analysis/Programs/IDLSwath/Census/census13.idl.gz . # gunzip census5.idl.gz # gunzip census8.idl.gz # gunzip census10.idl.gz # gunzip census13.idl.gz 8.2) Start IDL session # idl > restore,'census5.idl' > help View contents. Need to rename variables to avoid overwriting them when restoring the second census file. > elon1=elon & id1=id & jd1=jd & maxelon1=maxelon & maxnlat1=maxnlat & minelon1=minelon & minnlat1=minnlat & nlat1=nlat > help > restore,'census8.idl' > elon2=elon & id2=id & jd2=jd & maxelon2=maxelon & maxnlat2=maxnlat & minelon2=minelon & minnlat2=minnlat & nlat2=nlat > help > restore,'census10.idl' > elon3=elon & id3=id & jd3=jd & maxelon3=maxelon & maxnlat3=maxnlat & minelon3=minelon & minnlat3=minnlat & nlat3=nlat > help > restore,'census13.idl' > elon4=elon & id4=id & jd4=jd & maxelon4=maxelon & maxnlat4=maxnlat & minelon4=minelon & minnlat4=minnlat & nlat4=nlat Combine all arrays > elon=[elon1,elon2,elon3,elon4] & id=[id1,id2,id3,id4] & jd=[jd1,jd2,jd3,jd4] & maxelon=[maxelon1,maxelon2,maxelon3,maxelon4] & maxnlat=[maxnlat1,maxnlat2,maxnlat3,maxnlat4] & minelon=[minelon1,minelon2,minelon3,minelon4] & minnlat=[minnlat1,minnlat2,minnlat3,minnlat4] & nlat=[nlat1,nlat2,nlat3,nlat4] > save,/variable,filename='census.idl' > exit 9) IMPORTANT: In case you are re-running the swath program in the same working directory, make sure to delete 'rts*.idl,trk.idl,etc.idl'. If you don't, the swath program will completely ignore your input, and only consider these files to generate the output. Run IDL scripts, type: # ~analysis/Programs/IDLSwath/idlCensusSwath.sh Program will output an "overlapping time" message indicating progress. The amount of time it takes to run will depend largely on the span of the track and on the minute frequency. Smaller time span and lower frequency will take less execution time. 10) The final output file will be called 'swctk.dat', a gridded file. You probably would like to rename it to something like 'gracectk.dat'. It is ready to be sent to the proper authorities; I assume the scientists know about the final destination. HOW TO PRODUCE A NON-CENSUS SWATH GRIDDED FILE ---------------------------------------------- While we wait for George to incorporate it in the official code... Still logged into cat5.nhc.noaa.gov. 1) With the file 'rtswath.idl' in the current directory: # ~carrasco/bin/swath.sh al112004_0926_03_30 (could be any filename WITHOUT extension) It will create: al112004_0926_03_30.csv al112004_0926_03_30.dbf al112004_0926_03_30.shp al112004_0926_03_30.shx and the zip of all of them al112004_0926_03_30.zip 2) Rename it to follow archive convention: # mv al112004_0926_03_30.zip al11.2004_0926_03_30swathShape.zip ^ DON'T FORGET 3) Place it under cat5://home/FTP/year/Operational Place it under ftp.aoml.noaa.gov:/aoml/ftp/hrd/pub/hwind/year