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

[AWIPS #YFI-843426]: Re: [comethelp] Re: UCAR AWIPS Simulator Console #9 Issues

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: [AWIPS #YFI-843426]: Re: [comethelp] Re: UCAR AWIPS Simulator Console #9 Issues
  • Date: Wed, 21 Oct 2020 11:19:54 -0500
Hi Tim,

That looks like it was an automated response from Jeff who is out of the 
office, so you can ignore that (it's an issue with our ticket support system).

I don't think we will need the specific product ID from the grib file, we 
should be able to match on the WMO header if there is one, otherwise on the 
filename. It looks like you've added an entry in your ldmd.conf for 
eyewall.rap.ucar.edu which is good. If you know how the data are being sent 
that's great, and we can work with that, otherwise in the mean time I have a 
"notifyme -v -l - -h eyewall.rap.ucar.edu" command running as the awips user on 
your EDEX so when RAL sends something over the LDM we can see exactly what they 
are sending (even if we don't have the pqact.conf set up yet). Then we can use 
that to set up the pqact entry. How often do the data get produced/sent - 
hourly or every 6 hours? 


Thanks,

Tiffany Meyer
AWIPS Lead Software Engineer
UCAR-Unidata

If you're interested, please feel free to fill out a survey about the support 
you receive: https://forms.gle/tKG5SY9YJw4vBRVXA

Ticket Details
===================
Ticket ID: YFI-843426
Department: Support AWIPS
Priority: Normal
Status: Open
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.