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

(Fwd) Re: sequence numbers, ... (fwd)

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: (Fwd) Re: sequence numbers, ... (fwd)
  • Date: Tue, 1 Jun 1999 13:53:34 -0600 (MDT)

===============================================================================
Robb Kambic                                Unidata Program Center
Software Engineer III                      Univ. Corp for Atmospheric Research
address@hidden             WWW: http://www.unidata.ucar.edu/
===============================================================================

---------- Forwarded message ----------
Date: Tue, 1 Jun 1999 13:27:36 -0600
From: Mike Schmidt <address@hidden>
To: address@hidden
Subject: (Fwd) Re: sequence numbers, ...


--- Forwarded mail from Chad Johnson <address@hidden>

Date: Tue, 01 Jun 1999 13:56:10 -0500
From: Chad Johnson <address@hidden>
To: Mike Schmidt <address@hidden>
CC: address@hidden
Subject: Re: sequence numbers, ...

Mike Schmidt wrote:
>
> Chad,
>
> What's the latest thinking on the sequence number issue -- do you have
> code available to update the systems we have here?

Hi Mike,

Over the weekend I tested the code changes to pull the sequence number out of
the
PDH from the NOAAPORT broadcast. All appears to be functioning correctly. I
also
made a change such that if the environment variable NOSEQNUM is set, the
sequence
numbers remain static at 999. This should make it easier to transition all the
top level nodes to the new software with the minimum number of duplicate
products
produced. Please let me know when you intend to do this so I can make the
change
on SSEC's system.

You only need to update the executable file 'inge' in /opt/nport/bin. Stop the
ingestor before loading the new file. If you want static sequence numbers, edit
the file /etc/init.d/ingcntl in the 'start' section and export the env variable
NOSEQNUM=yes. Then restart the ingestor. To get sequence numbers again, remove
the line that exports NOSEQNUM and restart the ingestor.

The new inge executable can be obtained via anonymous ftp at
gold.ssec.wisc.edu/pub/unidata/inge

> Also, did the
> differences in the products received (between the systems here) give
> you enough information to determine what is happening?  Let me know if
> you want me to run another test...

Is the exceptions file (/opt/nport/exceptions) identical between the two
systems?
If not, that may account for the differences. If they are the same, could you
run
another diff.

-Chad

--
Chad W. Johnson                           E-mail: address@hidden
Programmer/Meteorologist                  Voice: (608) 265-5292
Space Science and Engineering Center      Fax: (608) 263-6738
University of Wisconsin -- Madison


---End of forwarded mail from Chad Johnson <address@hidden>