Note: (Almost) All configuration for gribmaster is accomplished by editing the conf/gribmaster.conf
and various conf/<dataset>_gribinfo.conf files. Although there are default settings in place,
you are strongly encouraged to read and edit these files as necessary.
Also, most of the default settings may be overridden
with command line arguments.
In the absence of the --dset DATASET option, gribmaster will read each of the dataset files located in the "active" directory. If you plan on running gribmaster for real-time data downloading then it is recommended that you copy the data set configuration files from the "conf" directory to the "active" directory and then then edit them as necessary.
| --help |
| --[no]verbose |
Turns verbose mode on [off] |
| --date [YY]YYMMDD |
Date of the data file to access. Default is current date |
| --cycle HOUR |
Cycle hour of data set. See --guide for more arguments to --cycle |
| --length HOURS |
The period, in hours, that you wish to download and process |
| --nodelay |
Ignore the DELAY setting in <data set>_gribinfo.conf. You want your data now |
| |
|
| --tiles LIST |
list of tile number separated by a comma (03,23,33,...) and without spaces |
| --members LIST |
list of ensemble members separated by a comma (mean,n1,p1,...) (not working yet) |
| --ftp [SERVER] |
Obtain files via ftp from the list of available servers or [SERVER] |
| --http [SERVER] |
Obtain files via http from the list of available servers or [SERVER] |
| --nfs [SYSTEM] |
Obtain files crom a local system via the copy (cp) or remore copy (rcp) commands |
| |
|
| --noarchive |
Do not archive the files to the location specified in the <data set>_gribinfo.conf file |
| --noaltdir |
Do not move the files to the alternate location specified in the <data set>_gribinfo.conf file |
| --[no]gempak |
[Do not] process the incoming grib files to gempak format |
| --[no]grads |
[Do not] process the incoming grib files to GrADS format |
| --[no]convert |
Do [not] convert downloaded grib 1 (2) files to version 2 (1) |
| --force |
Force processing of all grib files after downloading |
| |
|
| --query [DATASET] |
list information in the data set configuration file |
| --dslist |
list the available data sets. |
| --guide |
Print out much more semi-usefull information than can be provided here |
a. Configuring the gribmaster/conf/gribmaster.conf file
b. Configuring the various grib information files
In the conf directory you will find a _gribinfo.conf file for selected model data set
on the NCEP and TOC servers. You may add additional data sets by simply copying one
of these files and making the appropriate changes to reflect the new set. Note that
the <data set> portion of the <data set>_gribinfo.conf file will be used when
executing gribmaster to identify the desired data, so name it wisely.
The file is relatively well-documented so the configuration should be straight
forward. The exception may be in the CYCLES parameter simply due to the many
different options available to the user, some of which I failed to document.
Feel free to send email if you have problems.
c. Running gribmaster
Most of the gribmaster options (flags) override the default values for a particular
data set; however, there are a minimum number of arguments that you must pass to
gribmaster. Here are a few examples:
1) % gribmaster --ftp --dset gfs
Will use all the default values in the gfs_gribinfo.conf file to download
grib files from the most current (date and cycle) run and place them in the
default directory on your local machine. Because there are no arguments
passed to --ftp the program will seach ALL defined remote servers (SERVER-FTP) looking
for the data.
2) % gribmaster --ftp NCEP --dset gfs
Just like (1) above except that gribmaster will only access the NCEP ftp
server.
3) % gribmaster --ftp --gempak --dset gfs
Just like (1) above except that the downloaded grib files will be converted
to gempak format.
4) % gribmaster --http --gempak --dset gfs
Just like (3) above except use the http servers identified in the gfs_gribinfo.conf file to access the data files.
3) % gribmaster --http --gempak --dset gfs
Just like (1) above except that the downloaded grib files will be converted
to gempak format.
4) % gribmaster --nfs --gempak --dset gfs
Just like (3) above except that gribmaster will try to get the files
from a NFS mounted partition.
5) % gribmaster --nfs /data/incoming --gempak --dset gfs
Just like (4) above except that gribmaster will try to get the files
from a the /data/incoming directory
6) % gribmaster --ftp --cycle 00 --dset gfs
As in (1) above except that gribmaster will get the data from the 00Z cycle
run from the current date (UTC on machine).
7) % gribmaster --ftp --cycle 00:24 --dset gfs
As in (6) above except that gribmaster will start with the 24 hour forecast
from todays 00Z run and download through the FINLFH hour as defined in the
gfs_gribinfo.conf file. Frequency of forecast grids are also defined in
the configuration file. See the documentation in the _gribinfo.conf file
for more information on the dark powers of the --cycle option.
8) % gribmaster --ftp --cycle 00:24:FINLFH:12 --dset gfs
As in (7) above except use the default final forecast hour (FINLFH) and
override the default forecast grid file frequency with 12 hours. See the
documentation in the _gribinfo.conf file for more information on the
dark powers of the --cycle option.
9) % gribmaster --ftp --cycle 00:24 --length 48 --dset gfs
As in (7) above except override the default value for FINLFH and
get 48 hours worth of forecast grids beginning with the 24 hour
forecast. Thus you get the 24 to 72 hour forecast.
10) % gribmaster --query gfs
List out the default settings for the gfs data set.
11) % gribmaster --verbose --ftp NCEP --dset gfs
Just like (2) above except print out information about what is going on.
12) % gribmaster --ftp --cycle 00 --date 20040820 --dset gfs
Just like one of the examples above but get the 00Z cycle data from
20 August 2004.