[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
20050620: Increasing maxgribsize for dcgrib2
- Subject: 20050620: Increasing maxgribsize for dcgrib2
- Date: 20 Jun 2005 09:59:01 -0600
Steve,
Unless you are running a really old version for dcgrib2,
the program will try to increase maxgribsize on its own,
and only emmit that message if it could not allocate the resources.
What version are you running?
The default MAXGRIBSIZE is defined in
$NAWIPS/unidata/ldmbridge/decode_grib.c
at the top of the file in a DEFINE statement.
Increasing that, and then recompiling with:
cd $NAWIPS/unidata/ldmbridge/dcgrib2/
make clean
make all
make intall
will solve that problem. Now, if the decoded grid (nx*ny) ends up larger
than LLMXTG in $GEMPAK/include/GEMPRM.PRM (and gemprm.h), you would have
to increase those and recompile the entire package.
The default for LLMXTG is 750,000 grid points in current distributions.
Steve Chiswell
Unidata User Support
On Fri, 2005-06-17 at 16:08, Steve Mullen wrote:
> Steve,
>
> How do I increase the max grib length to prevent dcgrib2 from gagging?
> Example below.
>
> Steve
>
> $ dcgrib2 radar.gem < ST4.2002013112.06h
> [30564] 050617/1434 [DC 3] Starting up.
> [30564] 050617/1434 [DCGRIB -50] griblen [1377052] > maxgribsize [1000000]
> [30564] 050617/1434 [DC 5] Normal termination.
> [30564] 050617/1434 [DC 2] Number of bulletins read and processed: 0
> [30564] 050617/1434 [DC 6] Shutting down.
