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

19990730: no imagery

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: 19990730: no imagery
  • Date: Fri, 30 Jul 1999 13:18:14 -0600
>From: "David J. Travis" <address@hidden>
>Organization: University of Wisconsin-Whitewater
>Keywords: 199907301755.LAA07700 IDD

David,

>We have not been receiving any satellite imagery this week (none since July
>25th).  However, other data feeds seem to be active.  For instance, we have
>lightning data feeds up to the minute.

Our IDD topology list for the MCIDAS feed shows that UWW should be fed
by sunset.meteor.wisc.edu.

>Any idea what's going on?  

A quick 'notifyme' to the Wisconsin machine shows that they are getting
the imagery data:

(zero:ldm) 43 % notifyme -vxl- -o 3600 -f MCIDAS -h sunset.meteor.wisc.edu
Jul 30 18:30:57 notifyme[20595]: Starting Up: sunset.meteor.wisc.edu: 
19990730173057.745 TS_ENDT {{MCIDAS,  ".*"}}
        NOTIFYME(sunset.meteor.wisc.edu) returns OK
Jul 30 18:31:01 notifyme[20595]: NOTIFYME(sunset.meteor.wisc.edu): OK
Jul 30 18:31:01 notifyme[20595]: defcdbb8b22111bb1858bcddf53cf824   429852 
19990730173225.639  MCIDAS 000  LWTOA3 161 DIALPROD=UA 99211 173223
Jul 30 18:31:02 notifyme[20595]: dc009b5a17e541229f7cd0d0407a5daa   368001 
19990730173425.809  MCIDAS 000  LWTOA3 61 DIALPROD=UC 99211 173415
Jul 30 18:31:03 notifyme[20595]: c92bfc9dd5d06726c9cb575e211292c8  1359485 
19990730173639.423  MCIDAS 000  LWTOA3 151 DIALPROD=UI 99211 173608
Jul 30 18:31:03 notifyme[20595]: 67dbf6f16f7bda570f148cce0f393ea7   234607 
19990730173706.512  MCIDAS 000  LWTOA3 211 DIALPROD=UW 99211 173655
Jul 30 18:31:03 notifyme[20595]: c003181f21504aafae47abf163900cc5  2152351 
19990730173725.922  MCIDAS 000  LWTOA3 141 DIALPROD=UV 99211 173656
Jul 30 18:31:10 notifyme[20595]: 021c93e0e703ed63976c81dc425adb5c    47422 
19990730180708.456  MCIDAS 000  LWTOA3 205 DIALPROD=U3 99211 180700
Jul 30 18:31:11 notifyme[20595]: 5bbf4c14b7ec5dcd8f278bb792c3e136   189670 
19990730181041.165  MCIDAS 000  LWTOA3 193 DIALPROD=U1 99211 181034
Jul 30 18:31:12 notifyme[20595]: 431dd441a80a769a9ea82121b0174e17   222280 
19990730181619.572  MCIDAS 000  LWTOA3 172 DIALPROD=UB 99211 181615
Jul 30 18:31:12 notifyme[20595]: ce99e130ad4ec064d1b085e036d4a8e6  1318123 
19990730181635.352  MCIDAS 000  LWTOA3 132 DIALPROD=U5 99211 181617
Jul 30 18:31:12 notifyme[20595]: efd22261be0332bcc7771c5e81c0cd27  2305635 
19990730181712.707  MCIDAS 000  LWTOA3 122 DIALPROD=U9 99211 181644

This means that either:

o you are not requesting the data from them

or

o they are denying you

So, the questions for you are:

o on what machine(s) are you not getting the data (i.e. Linux or OS/2)

o are you sure that are still requesting the data; if yes, and if on
  your OS/2 machine then look in Text Window 4 and see if there are
  error messages every five minutes telling you that your feed request
  has been denied

Don logged onto your machine and took a quick look.  The fact that you
were getting HRS data from sunset.meteor.wisc.edu but not MCIDAS did
not make any sense given that there were no RECLASS messages when you
first make the request for MCIDAS products.  So, Don stopped the LDM
and then waited to see if any MCIDAS products would come in; one did.

Don then noticed that the time on your machine appears to be off by
one hour.  This is most likely the cause of your difficulties.  What
you need to do is:

o logon as root
o select the system administration icon from the control-panel GUI
  that will popup
o select date and time from near the bottom of the list on the left
  hand side of the GUI
o set the time
o verify that your time is now correct

Our theory is that your clock has been slowly drifting since Don help
you set it up.  What really needs to be done is to get the person
that will be helping you with Linux (reference below) to setup NTP
for you so that your clock will stay correct (at least while connected
to the net).

>On another issue...I have found someone to help me with our linux problems
>and he and I will be working together over the next few weeks to try to
>iron out some of the problems I mentioned to you last week.   I'll keep you
>informed and will probably have some questions along the way.

OK, sounds good.

Tom