Configuring the GRIB Decoders

There are two options to choose from for decoding real-time NCEP GRIB messages.

The DMGRID decoder decodes the GRIB messages then creates and stores them in McIDAS Grid files.
The DMBIN decoder files the GRIB messages into GRIB files and populates the MySQL database.

You can activate either or both of the decoders and make their data available to your users in datasets defined in Configuring the Default ADDE Datasets. Keep in mind, however, that McIDAS Grid files consume much more disk space than GRIB files, as noted in the System Requirements.

See Chapter 5, Decoding GRIB Messages, for more information.

DMGRID Decoder for McIDAS Grid Files

If you want to decode the GRIB messages into McIDAS Grid files, activate the DMGRID decoder by running the command below from a McIDAS-X session running under the oper account.

Type: DECINFO SET DMGRID ACTIVE

DMBIN Decoder for GRIB Files

If you want to file the GRIB messages into GRIB files and populate the MySQL database, use the gribadmin and DECINFO commands below.

Create the MySQL database by running the command below from a Unix shell prompt. Before running the command, review the Configuration Sections section of the gribadmin script . It contains variables that change its behavior. These variables must be reviewed before using the script. In particular, the mysql_path and gcc_lib_path variables may need to be changed. After reviewing the Configurable Options, create the database with the command below. The command will prompt for a password. Enter the password for the MySQL root user, which was set by the person that installed MySQL.

Type: gribadmin makedb

Activate the DMBIN decoder by running the command below from a McIDAS-X session running under the oper account.

Type: DECINFO SET DMBIN ACTIVE

[Search Manual] [Table of Contents] [Go to Previous] [Go to Next]