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

20030129: profiler data

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: 20030129: profiler data
  • Date: Wed, 29 Jan 2003 15:39:19 -0700
>From: "Paul L. Sirvatka" <address@hidden>
>Organization: COD
>Keywords: 200301291659.h0TGx0618184 ldm-mcidas McIDAS FSL wind profiler

Hi Paul,

>IS there something up with the profiler data?

Not that I know of.

>We stopped getting our MD
>files made so I suspected that something is corrupted. Quite frankly I am
>not sure how I would find that out or why it happens or what to do if it
>did. However, when I pointed to UNIDATA's ADDE server for ptsrc data I
>came up with no data also.

I just pointed at adde.ucar.edu for RTPTSRC and was able to list and
plot current hourly summary profiler data for every station I tried.
I did see that Platville, CO had no 6-minute data, but Slater, IA did
have data.  I also verfied that I can get the profiler data from
Gilbert's ADDE server, weather2.admin.niu.edu.

>Any ideas?

I would have to look at log files, see if the profiler MD files existed
but were corrupted, etc. before I could come up with any theory.  What
does the log output from the profiler decoder, proftomd, look like
on your system?

Tom