Hi Gilbert,
re: new ** TEST ** version of Unidata NOAAPort ingest package available
>Yay! Thanks, Steve. And Thanks, Tom! These are most welcome developments.
>Will it also do the same for products that run together on any other feed,
>not just GRIB2 products?
The portion of code that was vunerable to bad products is in GRIB2
processing. In particular, products that were suppoed to be individual
GRIB2 messages but were not were sent to g2clib routines for metadata
extraction. The problem was that g2clib assumed that the GRIB2
messages are error-free -- they did no sanity checking on their
size/contents. Since the product's size is available before g2clib is
called, it was straightforward to pass the product size to g2clib and
modify the g2clib code to check the indicated product size with what
was read and not proceed with badly formed messages.
re:
>BTW, College of DuPage and I (NIU) have been running it for about 8 hours
>now with no problems. I was wondering, however: I indirectly inject into
>the IDD through Unidata2@SSEC. Since I don't inject directly, am I safe to
>stay on this version, or should I revert back to 1.3.0 until Tuesday
>night?
I checked the one machine I could find that is requesting data from
your NOAAPort ingester and saw that NEXRAD3 is not being requested.
Given this, there is no chance of the DPA products "leaking" into
NEXRAD3 before users are alerted to the change. So no, you should not
need to revert.
Cheers,
Tom
--
********************************************************************** <
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 <
---------------------------------------------------------------------- <
NOTE: All email exchanges with Unidata User Support are recorded in the
Unidata inquiry tracking system and then made publicly available
through the web. If you do not want to have your interactions made
available in this way, you must let us know in each email you send to us.
