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

20030418: Alternate EXP feed

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: 20030418: Alternate EXP feed
  • Date: Sun, 20 Apr 2003 09:56:44 -0600
>From: "Mark Fenbers" <address@hidden>
>Organization: DOC/NOAA/NWS - National Weather Service
>Keywords: 200304181815.h3IIFh7U020918 IDD LDM feed type

Mark,

>We currently use the LDM's EXP feed to share files between us and another
>office.  We would like to use LDM for sharing a different set of files between
>us and a third office, but would like to use another feedtype besides EXP
>because filenames  may conflict.

OK, this should be no problem.

>Certain feeds like AFOS and WMO expect product
>headings in a certain format so it knows how to parse the products,

The LDM does not care what data is included in a stream (feed type).
pqact actions in ~ldm/etc/pqact.conf, however, are setup to do
processing based on the feed type and product header.

>but the EXP
>feed seems to permit a wide range of productname formats.

There are no preconceived notions of what must be in a certain feed
_except_ when that feed is used in a project.  The IDD, for instance
does segment data into various feeds, and, by convention, those feeds
do have certain kinds of data in them.  If you objective is to simply
use the LDM to move data to machines that are not participating in
the IDD, then you can use any feed type that you like.  Problems arise
only when the machine you are sending data to is feeding particular
types of data assuming a convention, like, for example, a site requesting
IDS|DDPLUS from a machine that is getting those products from the Unidata
IDD.

>Which other feedtype would you recommend for sharing UNIX files (e.g.,
>"put_graphs_iln.pl" or "cle.pahps.dat") without any particular naming
>convention?  FSL5?  SPARE?  FSL2?

Again, if the machines using the feed (sending and receiving) are not
participating in a project where feed types are defined by convention,
you can use anything you like.  If the receiving machine is participating
in such a project, then you have to be careful to select feed types that
are not in use for that project.  In the case of the IDD, you could use
feeds like EXP, SPARE, FSL2, etc. since those feeds are typically used
internally by sites.

>Thanks for the advice...

Sorry if this answer is a little confusing, but how you use feed types
in your operation really depends on more factors than are evident by
your question.

Tom Yoksas