[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 20040325:LEAD testbed data (fwd)



Doug,

That sounds good -- so Keith would be the person to contact about what form they'd like to have the data in for use in ADAS. They may already have their own decoders or maybe they just use it in the form in which it arrives. But, since that's the first non-Unidata tool we plan to work with, it's probably a good place to start asking about requested forms.

Thanks for tracking that down. I believe Keith was the person talking about how ADAS works at the earlier meeting.

-- Ben

--On Tuesday, March 30, 2004 11:20 AM -0700 Doug Lindholm <address@hidden> wrote:

Kelvin put out a request for tool info including data requirements. Keith
Brewster is slated to handle the ADAS description.

Doug

Ben Domenico wrote:
Hi Tom,

Regarding decoding formats, I suggest you find someone in the ADAS tech
staff at OU and find out what form they assume the datasets will be in
for use in their data assimilation package.  That's one that we
eventually want to interface with so it would be good to know what
assumptions they make about the input data.

Unfortunately I don't know if we ever got an official contact person
there.

-- Ben

--On Tuesday, March 30, 2004 10:48 AM -0700 Tom Baltzer
<address@hidden> wrote:

Hi Marcus,

FYI, you and I are on parallel paths in that I'm trying to get all these
elements up and running on the Unidata LEAD test bed as well as work on
documentation and other elements to assist other LEAD testbeds in
getting this stuff up and going.   It sounds like you're ahead of me,
(not surprising as I'm the new guy who has yet to figure much out!) but
I intend to catch up and collaborate with you on this effort.

Regarding the decoding of the data feeds, are you aware of any
indicators as to what form LEAD would like the various feeds?  I've
been looking to folks around here to see what they generally do with
each of the seven feeds and working towards setting up decoding in that
fashion.

I'm also interested in hearing about any "gotchas" you encountered in
installing the pieces you have in place so far.

Thanks,
Tom.


Tom Baltzer Software Engineer UCAR Office of Programs Unidata Program Center P.O. Box 3000 Boulder, CO 80307-3000 address@hidden 303-497-8637


-----Original Message-----
From: address@hidden [mailto:owner-thredds-
address@hidden On Behalf Of Robb Kambic
Sent: Tuesday, March 30, 2004 8:49 AM
To: address@hidden
Cc: address@hidden; support-thredds
Subject: Re: 20040325:LEAD testbed data (fwd)

Marcus,

The cookbook has much of the info you need, it's at:
http://www.unidata.ucar.edu/projects/THREDDS/tech/configurations/cookb
oo k. html

But... It's not complete in all the configurations and the thredds.war
file is not in place yet. It will be there soon.  If you have package
questions send those to support, they will be forwarded onto the
correct people.  Other questions should go to me so I can improve the
cookbook documentation and forward those onto the LEAD folks here.

Thanks,
Robb....

======================================================================
== == =====
Robb Kambic                       Unidata Program Center
Software Engineer III               Univ. Corp for Atmospheric

Research

address@hidden           WWW: http://www.unidata.ucar.edu/
======================================================================
== == =====

---------- Forwarded message ----------
Date: Mon, 29 Mar 2004 11:33:26 -0700
From: Ben Domenico <address@hidden>
To: Jeff Weber <address@hidden>
Cc: Robb Kambic <address@hidden>
Subject: Re: 20040325:LEAD testbed data (fwd)

Jeff,

Have you talked to Robb about this?  I thought he was working on an end
to end cookbook for these pieces.  He's especially aware of how the
decoders fit in.

-- Ben

--On Monday, March 29, 2004 10:11 AM -0700 Jeff Weber
<address@hidden> wrote:

> Hi Ben,
>
> FYI....
>
> Looks like that end-to-end documnent is needed sooner rather than
later
:)
>
> I'll be ramping up my work in that area.
>
> Jeff
> ---------------------------------------------------------------------
>
> ---------- Forwarded message ----------
> Date: Mon, 29 Mar 2004 11:25:39 -0500
> From: Marcus Christie <address@hidden>
> To: Jeff Weber <address@hidden>
> Subject: Re: 20040325:LEAD testbed data
>
> Jeff,
>
> Yes, things seem to be going well.  Regarding decoding data streams,
> this is where I am having great difficulty.  I can't seem to find any
> documentation that brings together how to use pqact.conf in
conjunction
> with the decoders, netcdf, etc.  Pointers on this would be most
> helpful.
>
> In general, I am at a loss as to what one actually does with this
data.
>   What I need is an end-to-end HOWTO or tutorial on how one sets up
>   LDM, configures pqact.conf with the appropriate decoders, sets up
> netcdf, set up OpenDAP/DODS to access these files, etc.  I've yet to
> find something that ties the whole picture together.  Again, any
> pointers would be very helpful.
>
> Thanks,
>
> Marc
>
> Jeff Weber wrote:
>> Hi Marcus,
>>
>> I see the data is flowing nicely to:
>>
>> lead.extreme.indiana.edu
>>
>> Can you update me on your successes or failures on decoding the data
>> stream?
>>
>> Thank you,
>>
>> Jeff
>> -------------------------------------------------------------------
>> -- Jeff Weber
address@hidden        :
>> Unidata Program Center
PH:303-497-8676        :
>> University Corp for Atmospheric Research      3300 Mitchell
Ln       :
>> http://www.unidata.ucar.edu/staff/jweber      Boulder,Co
80307-3000  :
>> -------------------------------------------------------------------
>> --
>
> --
> Marcus Christie
> address@hidden
> http://www.cs.indiana.edu/~machrist
> Yahoo IM: m_christie




-- *----------------------------------------------------------------------* | Doug Lindholm, Software Engineer | E-mail: address@hidden | | Unidata Program Center | Phone: 303-497-8659 | | UCAR Office of Programs | | | P.O. Box 3000 | There's no place | | Boulder, Colorado 80307-3000 | like $HOME | *----------------------------------------------------------------------*



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.