All,
The modification that Steve Chiswell recommended in his email to the
list earlier today has been rolled into a new ** TEST ** noaaport
release, noaaport-1.4.1.tar.gz.
This release is available by FTP as follows:
machine: ftp.unidata.ucar.edu
user: anonymous
pass: <your full email address>
directory: pub/noaaport
file: noaaport-1.4.1.tar.gz
Please be aware of the following changes to the code and their possible
impact on you and/or your users:
1) product bulletin sizes are compared to decoded GRIB lengths to
trap and prevent overruns (the cause of problems see in the current
release)
2) SDUS8 products are being moved from HDS to NEXRAD3
This allows future dual-polarization products to be included in the
NEXRAD3 datastream, and it will cause the SDUS DPA products to move
from the HDS to NEXRAD3 datafeeds.
Implication:
You, and/or users who feed from you may have LDM pattern-action file
actions that process DPA products from HDS. After the new code is
up and running, sites using the DPA products will need to modify
their setups to process the DPA products from the NEXRAD3 feed.
3) the g2clib library bundled with 'noaaport' was updated to version
1.2.0 to add the WAFS (thinned grids) coming in the near future
4) GRIB2 decoding tables were updated for new levels and parameters
5) an argument was added to 'dvbs_multicast' to specify the multicast
interface (in case a static route is needed instead of the default
route)
6) readnoaaport-1.4, like its predecessors, uses LDM configuration
files for its build. readnoaaport-1.4 has been tested with
LDM-6.8.x only. It is not expected to work with very old
LDM installations, and it is known to NOT build on systems
where the new test LDM-6.9.x is installed.
The build setup for noaaport-1.4 will need to be updated to
work with LDM-6.9.x. Until a new release of noaaport is made,
you are advised to continue using LDM-6.8.1.
NB:
Because of 2) above, we are requesting that sites running NOAAport
ingest systems whose output is fed into the IDD wait until the late
afternoon or evening of Tuesday, May 18 to transition to the new code.
On Monday, May 14 an email will be sent to the ldm-users@xxxxxxxxxxxxxxxx
email list notifying IDD participants of the impending change and
advising them of the action(s) that they will need to take to minimize
impacts to their data processing.
Please relay this message to folks you know are running the Unidata
NOAAPort ingest package but not subscribed to this list.
Please direct questions/comments to support-noaaport@xxxxxxxxxxxxxxxx.
Cheers,
Tom Yoksas
Unidata User Support
--
********************************************************************** <
Unidata User Support UCAR Unidata Program <
(303)497-8643 P.O. Box 3000 <
support@xxxxxxxxxxxxxxxx Boulder, CO 80307 <
---------------------------------------------------------------------- <
Unidata Web Support http://www.unidata.ucar.edu/support <
********************************************************************** <
