Min Cluster
Defines the minimum number of neighbors needing to achieve the confidence.
3.10.3 Using MLHGT Data Flow with Other Products
To make full use of the MLHGT product, it should be distributed to other IRIS nodes to
support product generation and user display. The MLHGT product should also be returned to
IRIS/Radar and the RVP900 signal processor at the radar site.
The following figure is an example of MLHGT product distribution. The figure assumes the
RAW product is received at a centralized IRIS/Analysis node. The IRIS/Analysis node is
configured to generate a MLHGT product. This node would have the climatological settings
of the 0 °C heights. Optionally, there may be custom external process that obtains more
realistic 0 °C from other sources and updates the 0 °C stored in temporary memory. The
node generates the first MLHGT product according to the saved configuration and saves it
as a file. IRIS then manages this product file in a similar to other types of products.
Figure 15 MLHGT Data Flow for Use with Other Products
Ideally the MLHGT product is disseminated from the IRIS/Analysis node to the IRIS/Radar
node located at the radar site. IRIS/Radar automatically shares the information in the
MLHGT product to the RVP900 RDA software process through OP_CODE in the DSP API.
See RVP900 Digital Receiver and Signal Processor User Guide.
RVP900 uses the knowledge of the melting level for real-time attenuation correction, real-
time hydrometeor classification, and PhiDP conditioning for adaptive Kdp computation.
When the original ingest files are created, the radar derived melting level is also stored in the
metadata. The ingest files containing the radar derived melting level heights are typically
transferred back to the IRIS/Analysis for use in product generation.
IRIS Product and Display User Guide M211319EN-H
54 RESTRICTED
To Next Page
Loading...