Degrib: degrib1.63.txt

	NOAA / NWS's Meteorological Development Laboratory
	Degrib (NDFD GRIB2 Decoder)

Local forecast by "City, St"
Search by city. Press enter or select the go button to submit request

About Purpose Screen Shots

Installation How to Install Compile Windows Compile Unix Testing

Versions Registration Download Release Notes Change History To Do

Documentation Man Pages Tutorial Appendix Links NDFD FAQ Degrib FAQ

NDFD / NDGD Data Locations Custom Grids NDFD & Weather Past Weather Gotcha's

General Info Contact Us Acknowledgments

Subject: Degrib 1.63
Date: Tue, 30 Nov 2004 15:33:22 -0500
From: Arthur Taylor
To: arthur.taylor@noaa.gov

Hi everyone,

You all have the unique distinction of being registered on my degrib
(aka NDFD_GRIB2Decoder) mailing list (all 595 of us) (I'd like to
welcome: joshuautt, a.bohlander, Killian.Tobin, rehak, gblair, zmarsh,
e.quarles, addcoachglen, lmilhan, darcikelly, nuts, nrl, david.keller,
info, evtgm, Scott.Holder, jmorgan, baudouin.raoult)

Please let me know (email me) if you want to unregister. The latest
version of the program is on:
www.nws.noaa.gov/mdl/NDFD_GRIB2Decoder/

----------- General News.

I just wanted to remind everyone that tomorrow, Dec. 1, the NDFD
variables: "maxt", "mint", and "pop12" will become operational. As far
as I know, only the CONUS (and CONUS sectors) versions of these
variables will become operational. Which means that "maxt", "mint", and
"pop12" in Puerto Rico, Hawaii, and Guam will remain "experimental".

What does this mean? From our perspective, when a variable becomes
operational it moves from "/SL.us008001/ST.expr/DF.gr2/DC.ndfd/" to
"/SL.us008001/ST.opnl/DF.gr2/DC.ndfd/".

Note: As far as I know there will be NO OVERLAP! So sometime tomorrow,
"ds.maxt.bin" "ds.mint.bin", and "ds.pop12.bin" will either disappear or
no longer be updated in "/SL.us008001/ST.expr/DF.gr2/DC.ndfd/conus/"
(and CONUS sectors). Presumably at the same hour they will appear in
"/SL.us008001/ST.opnl/DF.gr2/DC.ndfd/conus/" (and CONUS sectors).

What do we do? If you don't use the CONUS or CONUS sectors, you can
continue on happily. If you use the CONUS, or CONUS sectors, I built
into previous versions of degrib the ability to turn a variable from
experimental to operational. To do so, use tkdegrib's file menu option
to select configure. On the "Variables" tab, highlight maxt, mint, and
pop12, and click the "Operational" button. Next, on the "Extra" tab,
change "Operational NDFD HTTP Root Dir" and "Operational NDFD FTP Root
Dir" from "ST.expr" to "ST.opnl". Then click "OK". (Note, you can do
the same thing by editing "/degrib/bin/ndfd.ini".)

Problems with this:
1) In previous versions, I hadn't taken into account that variables
would be operational in some areas and not in others, so if you use both
CONUS and non-CONUS sectors, I would recommend downloading the latest
version.
2) In previous versions, it only tries to get a variable from the
"operational" or "experimental" directory, but not both. So you need to
toggle them to operational at the "RIGHT TIME", or it won't get "maxt",
"mint", "pop12".

----------- News about this release:
I have just finished putting together version "1.63" (last one that I
announced was "1.61" on 8/30/2004).

This release is mainly focused on the variables going "operational"
issues, and providing a fourth version of the "NDFD simple weather key".

1) To handle variables going operational, I can now configure the status
of a variable by region. So maxt can be "operational" in CONUS,
"experimental" in Hawaii, and "not available" in Alaska. In addition,
to avoid transition timing issues, the program first checks for the data
in the supposed location twice. If the data is not there, the program
then tries the "other" location.

So if a variable is configured to be "operational" and the date is
actually "experimental", the program will look for the data first in the
"operational" area, but will find it in the "experimental" location.
Similarly, if a variable is configured to be "experimental", after the
data becomes "operational", the program will look for it first in the
"experimental" area, and then find it in the "operational" location.

2) Implemented the fourth version of the "NDFD simple weather key".

3) Thanks to "DNovak3098", fixed a bug with my
handling of missing / undef with GrADS ctl files.

4) Fixed a bug with GetOutputName when using "-out stdout". (bug
introduced in versions 1.60 and 1.61).

5) Fixed a bug with generating images. Previously, it would only
generate images if the whole set was needed. Now it should be able to
generate them for just the highlighted variables.

6) Some support for decoding / inventorying "TDLPack gridded messages"

-----------

Please let me know if you have problems.

Regards,
Arthur


Page last Modified: November 30, 2004.
US Dept of Commerce National Oceanic and Atmospheric Administration National Weather Service Meteorological Development Laboratory	1325 East West Highway Silver Spring, MD 20910 Degrib Questions? Arthur Taylor NDFD Questions? nws.ndfd@noaa.gov XML Questions? Paul Hershberg & John Schattel	Disclaimer Privacy Policy