setenv MPLT_HOME /u3a/hein/util/bringi/pltYou also could execute this from the command line but it's easier to edit your .cshrc file. mpplt works only on the Suns.
When you run mpplt, the program will request information through a series of queries. Some of these queries are unnecessary, others are essential, and some are not easily understood.
Please enter TODAY's date ( m/d/y : eg. 9/18/92 ):You can just hit return here, or you may enter a date if you feel so inclined.
Enter: 1 -> in dbx (no display); 0 -> pop up XGKS windowYou will not need a display if you are not doing rayplots, otherwise you will need a display window (option 0). If you are only calculating Kdp you don't need a display so choose option 1 in that case.
CHOOSE PRINTER:
0. laserjet (default, RETURN)
1. color printer but for now black and white
2. don't print, just append to postscipt file plot.ps
Don't print, choose option 2. A file called plot.ps will appear in your current
directory. It is not needed.
Should file plot.ps be erased now? 0=no 1=yesMore unnecessary stuff. Doesn't matter what you choose here.
print com:
cgm2ncgm < meta.cgm | ctrans -d ps.mono -f font12 >> plot.ps
MPLT home directory is
/u3a/hein/util/bringi/plt
enter : 0. RETURN
1. CSU-CHILL
2. NCAR CP-2
3. ARMAR
Most likely you will be dealing with CHILL data, so choose option 1.
Is the DATA in: 1. ASCII; 2. BINARY; 3. UF?UF, choose option 3
Choose: 1. raw UF; 2. PLT processed UFIf you have not created the UF file using mpplt, choose option 1. If this is a file that was created using mpplt, choose option 2.
Enter first and last range bin numbers to process i.e. to get the first 512 gates, enter 1,512mpplt can only handle 75 km worth of data, which corresponds to roughly 512 range gates for CHILL data. For cases where the radar data go out farther than 75 km, you will need to choose an appropriate data window for consideration. To convert this distance window to range gates, remember that CHILL data have 150 m gate spacing in most instances. For example, your storm exists from 30 km to 60 km in range. So you will want to consider range gates from 30/0.15=200 to 60/0.15=400. Since we can consider up to about 500 range gates, you can widen your margins a bit and maybe enter 50,550 for your range gate endpoints. Or since in this case the storm is all within 75 km, you could just get away with entering 1,512.
Note: for tape input, enter device name in double quotes. e.g. "/dev/nrst0" Enter UF input file name:Enter the full name of your uf file here. Make sure you include path if it is not in the current directory.
DATE: 80196 & TIME: 12949
BEGIN: AZIMUTH = 335.05 & ELEVATION = .38
END: AZIMUTH = 335.05 & ELEVATION = .38
RECORD No. = 1 & RAY No. = 40
No. of BLOCKS in this RAY = 1
<<<< MAIN MENU >>>>
SELECT AN OPTION:
DATA SET LOCATING :
0. (RETURN) PROCESS NEXT RAY.
1. CHANGE DATA FILE. now : 0130.uf
2. SKIP RAYS.
3. REWIND TO BEGINING OF FILES.
CONSTANT VALUES CHANGING :
4. CHANGE Radar Constant Calibration Factor.
now : RCcf = .00(dB).
5. CHANGE Zdr Bias And ldrcal.
now : zdrbias = 1.55(dB).
now : ldrcal = 2.00(db).
6. CHANGE Front_End Matching Constant for Dfr.
now : DfrC = .00(dB).
7. SELECT RAINLINE info.
now : 1.152,-11.4960, 1.00, 2.0, 4.0
DATA PROCESSING :
8. GENERAL FILTER MENU.
9. KDP/A3/LDR ADAPTIVE FILTER MENU.
10. POLYNOMIAL FIT MENU.
OUTPUTS :
11. RAY PLOT MENU
12. SCATTER/STATISTICS PLOT MENU.
13. VERTICAL PROFILE PLOT MENU.
14. DATA OUTPUT.
15. STORM TRACT PLOT MENU.
16. QUIT.
$OPTION?
Here we are finally at the main menu for the program. You will need to choose
option 5 to change the current defaults for Zdr and LDR. They should
probably be set back to 0 for both, but you may want to check with Pat Kennedy to ensure that there are
no calibration corrections needed. So let's choose option 5 here.
ENTER Zdr Bias (in dB) And Ldrcal (dB):Let's assume no corrections are needed, so enter 0 and 0. After this you will return to the main menu. If you want to do rayplots, choose option 11.
DATE: 80196 & TIME: 12949
BEGIN: AZIMUTH = 335.05 & ELEVATION = .38
END: AZIMUTH = 335.05 & ELEVATION = .38
RECORD No. = 1 & RAY No. = 40
No. of BLOCKS in this RAY = 1
<<<<<<<<< RAY PLOT MENU >>>>>>>>>
SELECT AN OPTION :
0. (RETURN) EXIT TO MAIN MENU.
1. PICK VARIABLES FOR PLOTTING.
2. SCALE X-AXIS.
3. SCALE Zh
4. SCALE Zdr
5. SCALE Phidp
6. SCALE Rhv
7. RESET PLOT PARAMETERS.
8. PLOT a RAY.
9. HARD COPY a RAY.
10.SAVE the PLOT in rayfile.
$OPTION?
I won't go into this in too much detail. Most of these are pretty self-explanatory.
There are a large number of variables available for plotting. I suggest sticking
with the basic multiparamter variables. You can plot up to 4 variables. Note that
if you want to plot rays you will need to pop up a GKS window when you first started
mpplt.chill . Also, rays are chosen for plotting via a ray number, so you will
have to use an editor like solo or RDSS to determine the ray numbers of the rays in
which you are interested. The current ray number will be displayed in the header
information at the top of the ray and main menus. To change to a new ray, you must
exit to the main menu and choose option 2, skip rays. If you skip too far, use
option 3, rewind, to get back to the beginning. You can print out your rayplot if
you wish.
OK, time to calculate Kdp. At the main menu, choose option 14, data output.
SELECT an OPTION: 0. RETURN to MAIN MANU 1. Output ONE RAY on SCREEN 2. Output to intermediate file for STATISTICS 3. Output directly in Universal Format 4. Output a small volume to data file in ASCII FormatOutput directly to UF, option 3.
enter RANGE ( start, end (km) ) for DATA outputHere enter the approximate range that corresponds to the range gate data window you specified when initially reading in the file. For example, if you only looked at the first 500 gates or so, that corresponds to the first 75 km of data, so enter 0,75 here.
ENTER # of RAYS to PROCESSMake this a large number, enough to handle the whole file. A number like 32000 should be sufficient.
idata= 3
OUTPUT on: 1) 9-TRACK TAPE ?
2) EXABYTE ?
3) DISC-FILE ?
(OPTION 1 or 2 will NOT write 4-byte size headers
and trailers for each block of data written)
Choose option 3.
enter output filenameEnter the full name of the new file you wish to create. I suggest an extension like .puf or something similar, to stand for processed UF file.
After that the screen will start to be filled with garbage. This could take a while to output the entire file. Once that is done the main menu will appear and you can quit, option 16. Note that mpplt does a couple things to your data. First, it sets missing data values to 0. Second, it changes the two-letter UF codes for all the data fields. Reflectivity goes from DZ to ZH, differential reflectivity from DR to ZD, correlation coefficient from RX to RH, and velocity from VR to VE. The original differential phase field, DP, is now separated into three different fields. Phidp is PD, Kdp is KD, and the differential backscatter phase (delta) is DE. Ignore the other newly created fields. The newly created fort.* and stats.dat files are not needed.
To automate the Kdp calculation process, use the following script.
#!/bin/csh # This script assumes filenames have the form DATETIME.uf foreach times (0001, 0002, 0003) set file = 'DATE'$times cat > runfile50 << EOL 06/17/97 1 2 0 1 3 1 # This is the data window in range gates, change if necessary 0,500 $file.uf 5 0 0 14 3 # Start point of data window (km), change if necessary 0.0 # End point (km), change if necessary 75.0 32000 3 $file.puf 16 EOL mpplt.chill < runfile50 end rm runfile50 exit