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

(Fwd) Fwd: LDM - Current Status, 20031023

Date: Fri, 24 Oct 2003 13:03:33 -0600
Subject: Fwd: LDM - Current Status, 20031023

Return-Path: <address@hidden>
Received: from MZIEMER20 ([204.227.119.55]) by
          crmsg1.crh.noaa.gov (Netscape Messaging Server 4.15) with ESMTP
          id HN854L00.61N; Thu, 23 Oct 2003 14:07:34 -0500 
From: "Mark Ziemer" <address@hidden>
To: "Andy Miller" <address@hidden>,
         "Holly Reckel" <address@hidden>,
         "Lipinski Dan" <address@hidden>
Cc: "Robert Wavrin" <address@hidden>,
         "Bruce Aslesen" <address@hidden>,
         "Daniel Luna" <address@hidden>,
         "John Halquist" <address@hidden>,
         "Mike Deweese" <address@hidden>
Subject: LDM - Current Status, 20031023
Date: Thu, 23 Oct 2003 14:07:30 -0500
Message-ID: <address@hidden>
MIME-Version: 1.0
Content-Type: multipart/alternative;
        boundary="----=_NextPart_000_0002_01C3996E.FF83DCF0"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165

Holly, I have included you here since items 6 and 7 have to do with fxa
changes.

Bob, future items will require computer team involvement.

==========================================

During the last couple of days and today, I have made changes to the ldm /
ldad system files.  Also, info needs to be shared on future changes.

1.    The major problems with data transfer between the USGS ND and us via
ldm has been found.  For your info, the problem was that when RedHat Linux
as installed, the firewall option was included at the "high" level.  To make
things worse, they are having problems turning the firewall off.  But, this
is being fixed now and we do know what the work around is.  Run the ldmd
process as root.

2.    Talked to Brian Asifan, CEMVR, about different data feeds.  CEMVR is
currently using FSL4 so we can not us this feed to send them data.  FSL3 and
FSL5 are ok.  Brian would like us to move the non-noaaport data from the PPS
data feed.  This would be most of what we are send now.  This would then
allow offices to easier block the WMO feed of which PPS is a subset.  Brain
also asked if we could be a backup noaaport text feed for CEMVR.

3.    Talked to Bill Gery, CR, about ldm data feeds.  He has no problems
with us using FSL3 and FSL5.  When we move the items to a different feed
type, just let Mike Manker know so he can make the changes.  I asked about
CEMVR's request for a backup noaaport  text feed.  Bill had no problems with
this.

4.    MD and I got together yesterday and came up with some draft ldm file
names for what I will name:
    The COE/NWS/USGS Private LDM Network.  This will be using the FSL3 feed
type.

Mike's email on this follows:

-----------------------------------------------------------------------

-----Original Message-----
From: Mike DeWeese [mailto:address@hidden]
Sent: Wednesday, October 22, 2003 5:43 PM
To: Terry Ortel; Richard Pomerleau; Ringo H Lee; Anthony R Koebele
Cc: Mark Ziemer
Subject: LDM files


Hello All,
It appears we are finally at a point where we can send data back and forth
between all offices.  In order to get the process started, Mark and I came
up with some proposed filenames to use in our initial testing.  I spoke to
some of you already and these naming conventions seem to meet our needs.  If
for some reason this changes or complications arise we can always make
modifications.  The files we are proposing to transfer are listed below:
USGS
usgsxx.rating     (rating tables)
usgsxx.meas    (measurement data)
usgsxx.log        (general comments, this is currently being sent routinely
as a test by usgsnd)
(where xx is the state designator)

CORPS
cemvp.dcp    (gage data)
cemvp.ldq    (lock and dam data)
cemvp.res    (reservoir flows)
cemvp.miss    (unet model data)
(where cemv is the Corps of Engineers, Mississippi Valley Division, and the
last letter is the district office.  e.g. p=st. paul, r=rock island, s=st.
louis)

NWS
ncrfc.MSPRVFxxx        (official forecasts where xxx is the basin, e.g.
MSPRVFRED)
ncrfc.badgages            (gages turned off in our model due to suspicious
data)
ncrfc.msmt.request        (locations where we would like a measurement if
possible)
ncrfc.fcst.crests            (expected crest information for modeled basins
that are not official forecast      points)

Mark also mentioned that the feed type for these files should be FSL3, so
that we can restrict this information to specific cooperating offices only.
The ND USGS office is currently sending the usgs.log file several times a
day as a test message.  The NCRFC is sending the ncrfc.MSPRVFxxx files daily
already, so you should all be able to receive these also.  I will be
monitoring traffic on our end to see if things are working correctly.  If
you have problems on your end please let me know.

Thanks for all the cooperation so far.

Mike


-----------------------------------------------------------------------

5.    I changed the pqact.conf and ldmd.conf files for ls1 and alaska for
testing of the FSL3 product and the sending our RVF's as stated in the above
email.

6.    I added the RVF's to the triggers file and restart the triggers.
[ Holly, 6 and 7 are in the fxa area. ]

7.    I added the changes to the
/data/fxa/siteConfig/textApps/siteTrigger.template file.

8.    Wrote the shell needed to place the RVF's on ls1.

9.    Modified the check_coe and move_coe_on_ls1 files to handle the FSL3
feed type.

10.    Created new dir on ls1 to handle the FSL3 feed type.

11.    Wrote the send_FSL3 shell to manage the inserting the FSL3 files into
the correct ldm data stream.

12.    Completed testing of all changes this am.  We are able to send the
RVF's on one ldm server and it shows up on the other.

13.    The Future,  we will need to identify all of the products which we
are currently sending via ldm and ftp.
        a.    Current ldm data needs to be moved from the PPS to the FSL5
feed type.  Which will require close coordination with all office to include
CR so that data still shows up on the web.
        b.    The ftp items need to be moved to the ldm data feed.  Now
appears to be a good time to do this.
        c.    Need to inform all ldm users of the new products on the FSL5
data feed.

14.    We need to send an email to all ldm users to request that they let us
know which products from the noaaport feed they are using.  As NCRFC plans
on turning off this feed in the near future.
        a.    Once the products are listed, we will have to provided them
via other methods.
        b.    We will still have to make sure that we, ncrfc can get the
products which we require to feed our backup server.
        c.    We need to have a plan to quickly turn on this feed back on as
a backup to CEMVR as is needed.

15.    We need to complete the changes for the ldm conf files for all of the
data which we will be getting in the future.
        a.    ldm conf files
        b.    ldad conf files
        c.    ldad shells to handle the data.
        d.    shells / programs to display, notify the forecast that data
has come in.
        e.    shells / programs to allow the forecaster to send requests,
etc via ldm and FSL3.

16.    Doc's and data stream flow charts also need to be developed to allow
for troubleshooting and upgrading as is needed.

17.    Anything else which I am sure I have forgotten.


If you should have any questions with regard to anything here.  Just let me
know.


Mark.....