McIDAS-XCD Administrator's Guide
Version 2020.1
[Search Manual] [Table of Contents] [Go to Previous] [Go to Next]
As noted in Configuring the Data Monitors, the DMGRID, DMBIN and DMCOND data monitors control the GRIBDEC, GRBFILER and CONDUITFILER decoders, respectively. If activated, the data monitors perform the following actions with real-time NCEP GRIB messages.
You can activate the data monitors as needed and make their data available to your users in datasets defined in Configuring the Default ADDE Datasets. Keep in mind, however, that SSEC tests and supports real-time -XCD grid datasets only in GRIB format, and that McIDAS Grid files consume much more disk space than GRIB files. See Chapter 5, Decoding GRIB Messages, for more information.
The sections below contain instructions for configuring the data monitors.
If you want to decode the GRIB1 messages into McIDAS Grid files, activate the DMGRID data monitor by running the command below from a McIDAS-X session running under the oper account.
Type: DECINFO SET DMGRID ACTIVE
If you want to file the GRIB1 and GRIB2 messages into GRIB files of the same format and populate the MySQL/MariaDB database with GRIB1/GRIB2 metadata, use the gribadmin and DECINFO commands below.
Create the MySQL/MariaDB database by running the command below from a Unix shell prompt. The command will prompt for a password. Enter the password for the MySQL/MariaDB root user, which was set by the person that installed MySQL/MariaDB.
Type: gribadmin makedb
If you have problems running this command, review the Configuration Sections section of the gribadmin script. It contains variables that change its behavior. In particular, the mysql_path and gcc_lib_path variables may need to be changed.
Activate the DMBIN data monitor by running the command below from a McIDAS-X session running under the oper account.
Type: DECINFO SET DMBIN ACTIVE
If you will be decoding CONDUIT products in a separate spool file, you must activate the data monitor. Otherwise, the CONDUIT data will be filed using the DMBIN data monitor. First, you must recreate the DECINFO.DAT file to add DMCOND to the list of valid data monitors.
Type: DECINFO LIST
Type: rm ~oper/mcidas/data/DECINFO.DAT
Type: DECINFO
Type: DECINFO SET DMCOND ACTIVE
Type: DECINFO LIST
This procedure is optional and is available only to sites that receive data via the LDM. The procedure increases throughput for GRIB messages by creating a separate spool file for the CONDUIT feed. If you are doing both the CONDUIT and NGRID LDM feeds in the same spool file, the tendency for dropped messages is possible.
Complete the steps below to implement the procedure.
Type: DECINFO SET DMCOND INACTIVE
Type: CIRCUIT ADD NCON INGESTOR=INGEBIN CONFIG=CONDUIT.CFG SPOOL=CONDUIT.SPL "NOAAPORT NWSTG CONDUIT Binary Circuit
Type: REDIRECT ADD CONDUIT.SPL "/data_directory_path
For
example: REDIRECT ADD CONDUIT.SPL "/home/oper/xcd_data
CONDUIT ^.* PIPE /home/oper/mcidas/bin/ingebin.k NCON |
Type: rm ~oper/mcidas/data/CONDUIT.PRO
Type: ldmadmin restart
Type: DECINFO SET DMCOND ACTIVE
You should notice very soon after starting the CONDUIT decoder that there is another entry in the ingestor section of the statdisp display. Three instances of the binary ingestor (INGEBIN) will exist if you are doing the optional NEXRAD decoder as well. The CONDUIT data should now be written to CONDUIT.SPL by the binary ingestor using the NCON circuit.
[Search Manual] [Table of Contents] [Go to Previous] [Go to Next]