TRMM Satellite Validation Office is in GVBOX. It contains the programs necessary for building ZR tables. These ZR tables are stored as ASCII files.
NEW for 1.5: The gauge_gui_main.pl has a new appearance, but, no new functionality.
NEW for 1.0: The ZR table generation is fully automated. It is automated from the 2nd intermediate file through the ZR table. The progam that does this is called automatic_zr.pl. It is possible to perform no QC and provide your own gauge filter file. It is possible to save the list of gauges, with their time range, that were removed during the QC step.
NEW for 1.0: The
build_zr_table has been added.
This program has a command line interface to provide parameters to generate
the ZR table. It is identical in function as build_dual_zr_table.c,
but, has a command line interface. The program is only capable of
generating a ZR table for stratiform and convective rain types and for
a predetermined range dependancy: 0-15km, 15-100km, and beyond 100km.
The ZR table is meaningfull for the
NEW for 0.26: The software contains the automated quality control of the merged gauge and radar dataset. The result of the quality control is a new merged gauge and radar dataset that only contains data that is acceptable -- all bad, or suspect, gauges have been removed. This program is called automatic_qc.pl.
Each ZR table may contain multiple ZR relationships. Typically, each ZR table represents the ZR relationships for all raintypes. For example, a single ZR contains a ZR relationship for only one rain classification. In such a case, only one ZR relationship is present in the ASCII file, whereas a dual ZR contains a ZR relationship for each of two rain types. In such a case, both ZR relationships are present in the ASCII file; one is listed after the other. The ZR table is then used as input for processing the 2A-53 product (2A-53 is rain rate product in the second level of GVS).
The construction of ZR tables requires the products 2A-54 and 2A-55 from GVS, and the gauge data as shown in the Flow Diagram below. From the flow diagram, several major independent processing steps are involved to produce the ZR tables file. The result file from the first step will be used by the second step, the result file from the second step will then be used by the third step, and so on. The major processing steps are:
How to Build a ZR Tables FileFollow the steps below to build a ZR tables file.
Comparing 2A-53 with gauge dataThis step follows the production of 2A-53. Production of 2A-53 requires quality controled gauge data and the ZR tables as described above. To summarize:
An example:get_2A53_data_over_gauge 2A53.980207.1.MELB.1.HDF zzzz.gdbm
get_2A53_data_over_gauge 2A53.980207.2.MELB.1.HDF zzzz.gdbm
get_2A53_data_over_gauge 2A53.980207.3.MELB.1.HDF zzzz.gdbm
(Execute for all granules, it appends to zzzz.gdbm)
first2ascii zzzz.gdbm > zzzz.ascii
merge_radarNgauge_data -f /rain2/merritt/melb_gauge.gdbm zzzz.ascii zzzz_2nd.ascii
Filter out unwanted gauges; this is known from
Now for the plotting. Note: -R.
gauge_radar_plot_batch.pl -f gaugefilter.file