[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[GEMPAK #DKY-490380]: What does this parameter name error mean?

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [GEMPAK #DKY-490380]: What does this parameter name error mean?
  • Date: Wed, 18 Mar 2009 17:04:37 -0600
Neil,

"Could not determine parameter name 2 3 203 0" seems to be a fairly common log 
message by dcgrib2, I see it frequently my machine.  I can't exactly say what 
the problem is, but it's likely just a parameter, date/time or level entry that 
can't be identified during the decoding of the grib file to gempak format.

Michael James
Unidata User Support


> Gempak 5.11.1
> ldm 6.4.5
> OS: FreeBSD 6.0-Release
> 
> I'm seeing this in our dcgrib2_CONDUITgfs.log:
> 
> [32371] 090227/1022[DC 3] Version 5.11.1
> [32371] 090227/1022[DC -11]
> [32312] 090227/1022[GB 1]
> [32312] 090227/1022[DECODE_GRIB2 -34] Could not determine parameter
> name 2 3 203 0 [0]
> [32312] 090227/1022[GB 1]
> [32312] 090227/1022[DECODE_GRIB2 -34] Could not determine parameter
> name 2 3 203 0 [1]
> 
> 
> resulting from this pqact decoder entry:
> 
> CONDUIT       prod/gfs.*pgrb[^2]
> PIPE  /unidata/GEMPAK5.11.1/os/freebsd/bin/dcgrib2 -d 
> data2/gempak/logs/dcgrib2_CONDUITgfs.log
> -e GEMTBL=/unidata/GEMPAK5.11.1/gempak/tables
> 
> What is the meaning and significance of the log entries?
> 
> Thanks,
> -Neil
> ----
> Neil R. Smith
> address@hidden
> Comp.Sys.Mngr.
> Atmospheric Sciences, Texas A&M Univ.
> 
> 


Ticket Details
===================
Ticket ID: DKY-490380
Department: Support GEMPAK
Priority: Critical
Status: Open