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.
>From: "Pandya, Rajul E." <address@hidden> >Organization: West Chester University >Keywords: 200008221228.e7MCSSN28075 ldm-mcidas Unidata-Wisconsin Rajul, >Thanks for the suggestion. I tried changing my ldmd.conf file from >request UNIDATA ".*" navierldm.meteo.psu.edu >to >request WMO ".*" navierldm.meteo.psu.edu >request MCIDAS "^pnga2area Q." navierldm.meteo.psu.edu Hmm... Another site feeding from Penn State is using: request MCIDAS "^pnga2area Q[01]" navier.meteo.psu.edu Did Penn State change the name of their machine? A 'nslookup' on navier.meteo.psu.edu gives the expected results: Non-authoritative answer: Name: navier.meteo.psu.edu Address: 128.118.28.2 but the same on navierldm.meteo.psu.edu hangs. >and did ldmadmin stop then start. I let it run for about half an hour and >got WMO data, but no satellite data. I switched it back and got satellite >data right away. Did I do something wrong? Your request line looks fine except for the specification of navierldm.meteo... >My pqact file is all pnga2area commands. OK. The entries in pqact.conf are just for processing products out of the LDM's queue. They really don't have anything to do with the ldmd.conf request entries. What happens when you change to use of navier.meteo.psu.edu in your request line? Tom