Showing entries tagged [ldm]

LDM 6.13.2 Released

LDM 6.13.2 has just been released. It fixes a few bugs and performs better than the previous 6.13 versions. You can view a list of the changes in the CHANGE_LOG.

Please send any questions to support-ldm@unidata.ucar.edu or report issues via the LDM GitHub site.

LDM 6.13.0 Released

LDM Version 6.13.0 is now available. It has a new logging system that, by default, doesn't use the system logging daemon though this change should be invisible. It also has several other improvements and bug fixes.

[Read More]

LDM 6.12.7 Released

Version 6.12.7 of the LDM package has been released. Improvements include:

  • Additions to the GEMPAK GRIB2 tables for ingesting the NOAAPORT satellite broadcast. This should greatly reduce the number of "GB" error-messages in the LDM log file.
  • Support for running rsyslogd(8) on a Solaris system with configuration-file /etc/opt/csw/rsyslog.conf and PID-file /var/run/rsyslogd.pid.
  • Refactored and generally improved code in pqact(1), hopefully stopping it from receiving a SIGSEGV when executing regexec(3). This has only occurred on one host and it's not clear if it's due to the code or the host.

The complete set of changes can be found here.

This new package can be downloaded here.

The homepage of the LDM is here.

LDM 6.12.6 Released

Version 6.12.6 of the LDM has been released.

Besides supporting the new NOAAPORT channels (like version 6.12.5) this version understands how to handle HRRR and ESTOFS data-products that will soon be added to the NOAAPORT broadcast.

Support for two additional channels will be added for the GOES-R satellite sometime before it's launched (currently scheduled for the second quarter of 2016).

Additional information about this release is available on the LDM 6.12.6 page. You can find a link to the source download area on the main LDM page.

LDM 6.11.7 Released

Version 6.11.7 of the LDM has been released. It fixes a bug that caused the NOAAPORT ingest component to crash.

Here's the story:

The NOAAPORT Satellite Broadcast System contains a lot of GRIB-2 messages. Such messages require external tables in order to be interpreted. The NOAAPORT ingest component of the LDM uses the tables that come with GEMPAK to interpret GRIB-2 messages in order to generate meaningful LDM product-identifiers. Unfortunately, not all tables are complete and creators of GRIB-2 messages are free to add data for which no corresponding table-entry exists.

[Read More]
News@Unidata
News and information from the Unidata Program Center
News@Unidata
News and information from the Unidata Program Center

Welcome

FAQs

Developers’ blog

Recent Entries:
Take a poll!

What if we had an ongoing user poll in here?

Browse By Topic
Browse by Topic
« July 2017
SunMonTueWedThuFriSat
      
2
3
4
5
6
8
9
12
13
14
15
16
17
19
20
21
22
23
24
25
26
27
28
29
30
31
     
Today