Skip to end of metadata
Go to start of metadata

October 15, 2010


  • Rich Signell
  • Chris
  • Jeff
  • Matthew
  • Charly


  • EOI Task Status Report
  • Review OOICI/IOOS Milestones Document
  • Question(s) about HFRADAR
  • Is the UCSD source considered part of IOOS? YES!
  • IDD/LDM setup at OOI
  • Rich's Title within OOI
  • IOOS DMAC implementation plan, including OOI-CI components.
  • Is there still just one CI for IOOS and OOI?


Brian Powell uses radials rather than processed grid product. May have some difficulties getting this in a nc form. Would be 2 wins to get radials on the network along with the appropriate governance for the community using that data.
Rich - even if we can't get those two wins - the feedback provided by simply trying to get this data is a boon for the community.

Jeff DLB will talk to Jack Harlan first, and possibly to the IOOS Program Manager, to discuss HFR distribution policy and determine whether some changes can be made.

Lisa Hazard confirmed that the UCSD HFRADAR is an official IOOS source. NDBC is the "main" site, UCSD is a "backup", and Rutgers is an offshoot (the product is different than the other two)

AI - Chris - generate confluence page listing all data products we are going after and for each, where we are with regards to acquisition strategy

Major component of Release 2 work is moving processing functionality into the network - processing of HFRADAR would be an ideal usecase - requres that radials are available!

IOOS currently working on budgeting for the next couple of years and is seeing potential overlap with OOICI goals
OOICI could provide syndication, format conversion capabilities, user-defined processing chains. IOOS would then like to expose these things to their customers as well as contribute processing chains to the network

AI - Setup meeting with Brian Powell to do what we did with Rugers - should be done by end of November
AI - Return to ERDDAP and really look at how it's composed. Matthew's understanding is that Roy and Bob reorganized the codebase based on OOI's decomposition such that it should be easier to decompose at this point. Verify that there is an "extra" in-memory model that could be avoided. IF that's the case, look at the algorithms to determine the specification. work with ERDDAP to rebuild their engine to utilze the "one-to-one" memory model (with feature types, etc) - Alex and Dorian performed the first OOI decompositon of ERDDAP

Brian Powell / ERDDAP meeting:
AI - Rich - Investigate a meeting at Pacific Grove with Brian Powell, Roy, Bob Simonds. Aim for 1st week in December - perhaps the Thursday and Friday before EGU.
AI - Rich - Setup call (prior to above meeting) for a briefing on the new ERDDAP (1.5 - 2 hours)

Rich's Title within OOICI: Scientific Liaison

IDD/LDM - Jeff learned that the distinction between the two is that IDD comprises the set of LDM implementations that are officially maintained by Unidata. You can install LDM without being part of IDD. Will OOI be part of Unidata IDD, or just another entity that runs LDM? Rich thinks the answer is yes. There are other places providing that feed.
Rich - IDD is the by far the biggest pipe backed by LDM. Has far more data (including GTS) than any other that Rich is aware of.
Rich has offered to set up IDD/LDM on an OOI machine

Mohan Ramamurthy (Unidata) wrote: "There is always confusion about IDD versus LDM: the former is the distribution network that Unidata manages, which we call Unidata IDD, while the latter is software that can be used independent of the IDD."

Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.