[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
20020305: Some missing data today
- Subject: 20020305: Some missing data today
- Date: Mon, 04 Mar 2002 19:20:29 -0700
>From: "Kevin Polston" <address@hidden>
>Organization: NOAA/NWS
>Keywords: 200203050151.g251p7K03671 IDD
Kevin,
So, you are a celebrity (Sunday Parade article on salary comparisons)!
>Well for the most part LDM has been running pretty good. There have been
>a few instances where the radar data would fall behind by maybe 20-30
>minutes but it seemed as if that was corrected fairly quickly. Actually
>with that small exception things have been very timely so that is good.
Sounds positive.
>However.....today I noticed the satellite data stopped coming in around
>mid morning and the surface observations don't seem to be complete - ie,
>there are fewer surface obs showing than what I have normally seen.
The machine that was feeding the NOAAPORT satellite imagery crashed and
burned after a power failure (it wasn't plugged into the UPS as it
should have been). It took until after noon to get it back up.
>I
>susbscribed to the LDM mailing list today but it probably wasn't in time
>to see if there was a problem with the satellite feed.
No, it wasn't. I had to approve the subscription since the domain of
the machine you submitted the request from did not match the domain of
the email address you were subscribing. In cases like this, support
must decide whether or not the signup is legit or not. No biggie, this
happens all of the time.
>I suspect
>something is wrong and I certainly won't bug you all the time about
>missing data....but is it common to go most of the day without data?
No.
>The
>data still seems timely...just missing for the satellite imagery and
>fewer surface obs.
Surface obs were missing near the end of the day because of a situation
related to the machine crash mentioned above. This late day outage was
my fault: I fat fingered an ldmd.conf request line and stopped
ingestion of observational data (sigh).
>One other question about the satellite imagery - if
>I wanted to alter my pqact.conf file to just grab some of the imagery
>and not all of it....can you give me a couple examples of how that
>should look. I want to make sure I enter it properly and not screw it
>up.
You could setup multiple pqact.conf entries, one for each type of image
you want to ingest, instead of one action for all of the images. This
way you can really tailor what you want to file. If you decide you
will never want the images you do not file, then you need to alter your
request line for NIMAGE in ldmd.conf to not request those images. This
will spare you some network bandwidth.
>I also restarted the ingestion of model data and it seems to be working
>very well. But I do have a question. On the RUC files there seems to be
>no CAPE or Helicity grids. I thought that was standard with the RUC.
>Would you know why this is?
I just checked the McIDAS-XCD decoded RUC 18 Z run for today, and do
see CAPE and Helicity grids:
GRDLIST RTGRIDS/RUC.63 PAR=CAPE NUM=ALL
Dataset position 63 Directory Title= ALL 18Z MAPS
PAR LEVEL DAY TIME SRC FHOUR FDAY FTIME GRID PRO
---- --------- ------------ -------- ---- ----- ------------ -------- ----- ----
CAPE SFC 04 MAR 02063 18:00:00 MAPS 0 04 MAR 02063 18:00:00 243 LAMB
CAPE SFC 04 MAR 02063 18:00:00 MAPS 1 04 MAR 02063 19:00:00 369 LAMB
CAPE SFC 04 MAR 02063 18:00:00 MAPS 2 04 MAR 02063 20:00:00 620 LAMB
CAPE SFC 04 MAR 02063 18:00:00 MAPS 3 04 MAR 02063 21:00:00 873 LAMB
CAPE SFC 04 MAR 02063 18:00:00 MAPS 6 05 MAR 02064 00:00:00 1135 LAMB
CAPE SFC 04 MAR 02063 18:00:00 MAPS 9 05 MAR 02064 03:00:00 1401 LAMB
CAPE SFC 04 MAR 02063 18:00:00 MAPS 12 05 MAR 02064 06:00:00 1530 LAMB
CAPE SFC 04 MAR 02063 18:00:00 MAPS 4 04 MAR 02063 22:00:00 1661 LAMB
CAPE SFC 04 MAR 02063 18:00:00 MAPS 5 04 MAR 02063 23:00:00 1784 LAMB
CAPE SFC 04 MAR 02063 19:00:00 MAPS 0 04 MAR 02063 19:00:00 2047 LAMB
CAPE SFC 04 MAR 02063 19:00:00 MAPS 1 04 MAR 02063 20:00:00 2298 LAMB
CAPE SFC 04 MAR 02063 19:00:00 MAPS 2 04 MAR 02063 21:00:00 2423 LAMB
CAPE SFC 04 MAR 02063 19:00:00 MAPS 3 04 MAR 02063 22:00:00 2550 LAMB
CAPE SFC 04 MAR 02063 20:00:00 MAPS 0 04 MAR 02063 20:00:00 2804 LAMB
CAPE SFC 04 MAR 02063 20:00:00 MAPS 1 04 MAR 02063 21:00:00 3058 LAMB
CAPE SFC 04 MAR 02063 20:00:00 MAPS 2 04 MAR 02063 22:00:00 3180 LAMB
CAPE SFC 04 MAR 02063 20:00:00 MAPS 3 04 MAR 02063 23:00:00 3306 LAMB
Number of grids listed = 17
GRDLIST - done
GRDLIST RTGRIDS/RUC.63 PAR=HELI NUM=ALL
Dataset position 63 Directory Title= ALL 18Z MAPS
PAR LEVEL DAY TIME SRC FHOUR FDAY FTIME GRID PRO
---- --------- ------------ -------- ---- ----- ------------ -------- ----- ----
HELI SFC 04 MAR 02063 18:00:00 MAPS 0 04 MAR 02063 18:00:00 244 LAMB
HELI SFC 04 MAR 02063 18:00:00 MAPS 1 04 MAR 02063 19:00:00 370 LAMB
HELI SFC 04 MAR 02063 18:00:00 MAPS 2 04 MAR 02063 20:00:00 619 LAMB
HELI SFC 04 MAR 02063 18:00:00 MAPS 3 04 MAR 02063 21:00:00 872 LAMB
HELI SFC 04 MAR 02063 18:00:00 MAPS 6 05 MAR 02064 00:00:00 1137 LAMB
HELI SFC 04 MAR 02063 18:00:00 MAPS 9 05 MAR 02064 03:00:00 1399 LAMB
HELI SFC 04 MAR 02063 18:00:00 MAPS 12 05 MAR 02064 06:00:00 1531 LAMB
HELI SFC 04 MAR 02063 18:00:00 MAPS 4 04 MAR 02063 22:00:00 1659 LAMB
HELI SFC 04 MAR 02063 18:00:00 MAPS 5 04 MAR 02063 23:00:00 1785 LAMB
HELI SFC 04 MAR 02063 19:00:00 MAPS 0 04 MAR 02063 19:00:00 2048 LAMB
HELI SFC 04 MAR 02063 19:00:00 MAPS 1 04 MAR 02063 20:00:00 2301 LAMB
HELI SFC 04 MAR 02063 19:00:00 MAPS 2 04 MAR 02063 21:00:00 2424 LAMB
HELI SFC 04 MAR 02063 19:00:00 MAPS 3 04 MAR 02063 22:00:00 2549 LAMB
HELI SFC 04 MAR 02063 20:00:00 MAPS 0 04 MAR 02063 20:00:00 2805 LAMB
HELI SFC 04 MAR 02063 20:00:00 MAPS 1 04 MAR 02063 21:00:00 3056 LAMB
HELI SFC 04 MAR 02063 20:00:00 MAPS 2 04 MAR 02063 22:00:00 3181 LAMB
HELI SFC 04 MAR 02063 20:00:00 MAPS 3 04 MAR 02063 23:00:00 3307 LAMB
Number of grids listed = 17
GRDLIST - done
So, yes, the RUC does have CAPE and Helicity grids in it as a matter of
course.
>It is good to have far fewer problems to report or ask questions about.
>I will probably have a few more down the road but hopefully as I become
>an "ldm-master" I can handle them with more confidence.
This is, of course, the goal: hands off ingestion/decoding and hands on
display/analysis.
>Talk to you soon,
Later...
Tom