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

19990921: NOAAPORT SBN question on the NWSTG format

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: 19990921: NOAAPORT SBN question on the NWSTG format
  • Date: Wed, 22 Sep 1999 15:14:43 -0600
>From: Gregory Grosshans <address@hidden>
>Organization: .
>Keywords: 199909222059.OAA10722

>This is a multi-part message in MIME format.
>--------------5538DF4D0BFAFC24D5433013
>Content-Type: text/plain; charset=us-ascii
>Content-Transfer-Encoding: 7bit
>
>Steve,
>
>What is the purpose of prod.info.seqno?  By default in this code its set to 0,
>  but
>a sequence number
>isn't added into the product.  Is this value normally assigned by pulling the
>seqno from the
>actual product?

Greg,

In FOS, every product has a sequence number- and prod.info.seqno
was set to that sequence number. Otherwise, prod.info.seqno is
generally postincremented for each product. When you use ldmadmin watch,
or notifyme, the sequence number for each product is part of the output-
and the existance of the number genererally makes tracking ingestion
and/or decoder problems much easier. For my Noaaport ingest, I set
it to the pdh sequence number. Say, you might have attenuation
at your dish, then by tracking the sequence numbers, you can determine
what products are dropped....or, what product that isn't following
the appropriate protocol is causing the ingestion to fail.

When comparing ingestion on streams at several receivers, having
a common sequence number can make syncing up your product logs
much easier.



>
>On another note, NAWIPS and Linux.  I've recently started using Linux and just
>built the latest
>version of NAWIPS from the NCEP/CDB on RedHat.  What window managers are peopl
> e
>using so NTL has enough colors?  Most of the Linux window managers (e.g. KDE,
>AfterStep, FVWM95) seem to use too many colors... I've been able to get NTL to
>start when running fvwm2.
>
>In HP-VUE and CDE there is a setting to tell the window manager to make more
>colors
>available for applications.  I'm sure there is something similiar for
>KDE/AfterStep/etc., but I haven't found it.

I've used fvwm2 with sucess also. To get FVWM95 to work, reportedly
you have to shut down the file manager on the desktop which is
eating colors. 

>
>Thanks,
>Gregg
>
>Unidata Support wrote:
>
>> Greg,
>>
>> I think you'll find that not all nwstg products end with
>> the \r\r\n\ETX sequence. I can think of the
>> SDUS97 products off the top of my head right now for example.
>> You might want to check for that and add that trailer as necessary.
>>
>> I use the product defnition header sequence number for the FOS-like
>> sequence number- not from the CCB. My comment was that I compute
>> the length of the CCB from the first 2 words of the CCB
>> rather than assuming it will be 20 bytes.
>>
>> Steve Chiswell
>> Unidata User Support
>>
>
>--------------5538DF4D0BFAFC24D5433013
>Content-Type: text/x-vcard; charset=us-ascii;
> name="grosshans.vcf"
>Content-Transfer-Encoding: 7bit
>Content-Description: Card for Gregory Grosshans
>Content-Disposition: attachment;
> filename="grosshans.vcf"
>
>begin:vcard 
>n:Grosshans;Gregory
>tel;fax:405-579-0700
>tel;work:405-579-0720
>x-mozilla-html:TRUE
>url:www.spc.noaa.gov
>org:DOC/NOAA/NWS/NCEP/Storm Prediction Center
>adr:;;1313 Halley Circle                               ;Norman;OK;73069;
>version:2.1
>email;internet:address@hidden
>x-mozilla-cpt:;0
>fn:Gregory Grosshans
>end:vcard
>
>--------------5538DF4D0BFAFC24D5433013--
>