Status Report: Sep 2011 - Mar 2012

Steve Emmerson, Tom Yoksas, Mike Schmidt

Strategic Focus Areas

The LDM group's work supports five of the funding proposal's six focus areas:

  1. Broadening participation and expanding community services
    Dispite the existence of "pull" clients, (e.g., the IDV), people still want the ability to subscribe to meteorological data and have it automatically processed as soon as it's available. The LDM is one of the few mechanisms for doing this with high-volume data flows.
  2. Advancing data services
    As institutions adopt the LDM to receive IDD data and to distribute their own locally-generated data, more data becomes available to the larger community (quid pro quo).
  3. Developing and deploying useful tools
    The LDM is, apparently, useful and is being deployed more and more.
  4. Providing leadership in cyberinfrastructure
    You know you're providing leadership in cyberinfrastructure when the NWS makes the LDM part of AWIPS-II.
  5. Promoting diversity by expanding opportunities
    Even small colleges and high-schools can use the LDM to receive and process massive amounts of data.

Activities Since the Last Status Report

Released Version 6.10.1

Major differences from the version in the last report are

  • Squashed bugs in the installation procedure, the ldmadmin script, the pqutil utility, and the LDM library
  • Created an LDM code-repository in the Unidata team-account on GitHub and populated it
  • Improved some documentation

Planned Activities

Ongoing Activities

We plan to continue the following activies:

  • Support LDM users
    • Email, phone, etc.
    • Training workshops
  • Incrementally improve the LDM as necessary
  • Incorporate additional AWIPS-II-related changes into the LDM
  • Update table-driven decoding of GRIB products as necessary

New Activities

We plan to organize or take part in the following:

  • Migrate LDM development to a more open-source paradigm:
    • Official code-repository on GitHub
    • Issue-tracking via Jira
    • Continuous integration via Jenkins
  • Further investigate distribution and installation of the LDM via RPM packaging