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.
Hi Brian, re: > Hello, I am getting my LDM running, and things seem to be working > well overall. Very good. > However I am looking for the national radar mosaics in the FNEXRAD feed > and I am not seeing them. So far I am just dumping all the products into > one file. I am looking for the string "radar_mosaic_national" or the string > "grib" and not finding it. (This is based on searching on the Unidata web > site and viewing old email responses.) The best way to start diagnosing a problem/situation is to use the LDM 'notifyme' facility. Here are two examples: <as 'ldm' on your LDM machine> notifyme -vl- -f FNEXRAD -o 10000 notifyme -vl- -f FNEXRAD -o 10000 -h your_upstream_feed_hosts_name The first invocation will list out information on all FNEXRAD products your LDM has received in the past 10000 seconds. The second invocation will list out information on all FNEXRAD products that your_upstream_feed_hosts_name feed site has received in the past 10000 seconds. The first 'notifyme' invocation run on your machine should result in a listing that looks something like: % notifyme -vl- -f FNEXRAD -o 10000 Mar 31 17:41:02 notifyme[3842] NOTE: Starting Up: localhost: 20090331145422.545 TS_ENDT {{FNEXRAD, ".*"}} Mar 31 17:41:02 notifyme[3842] NOTE: LDM-5 desired product-class: 20090331145422.545 TS_ENDT {{FNEXRAD, ".*"}} Mar 31 17:41:02 notifyme[3842] INFO: Resolving localhost to 127.0.0.1 took 0.000402 seconds Mar 31 17:41:02 notifyme[3842] NOTE: NOTIFYME(localhost): OK Mar 31 17:41:03 notifyme[3842] INFO: 1450346 20090331172500.112 FNEXRAD 000 rad/NEXRCOMP/1km/n0r_20090331_1723 Mar 31 17:41:03 notifyme[3842] INFO: 88651 20090331172506.742 FNEXRAD 000 rad/NEXRCOMP/2km/n1p_20090331_1722 Mar 31 17:41:03 notifyme[3842] INFO: 47698 20090331172600.293 FNEXRAD 000 rad/NEXRCOMP/4km/ntp_20090331_1724 Mar 31 17:41:03 notifyme[3842] INFO: 3051548 20090331172808.776 FNEXRAD 000 radar_mosaic_nathr !grib2/unidata/UPC_25/#000/200903311727F000/N0R/0 - NONE! 000000 The 1 km national N0R composite image is the product with ID: rad/NEXRCOMP/1km/n0r_20090331_1723 > My reason for subscribing to the FNEXRAD feed is to get the mosaics in grib > format. Are these still provided? The 1 km national N0R composite in GRIB2 format is the product with ID: radar_mosaic_nathr !grib2/unidata/UPC_25/#000/200903311727F000/N0R/0 - NONE! 000000 > Perhaps the frequency of these products is low -- I have only looked at about > a half hour of product stream so far... No, I don't think so. I would guess that the problem is that your pattern-action file action for FILEing the composite in GRIB2 format is incorrect or lacking. Side comment: 'notifyme' is a _VERY_ handy utility to use for a variety of purposes including (but not limited to): % notifyme -vl- -f FNEXRAD -o 10000 -p radar_mosaic_nathr Mar 31 17:51:44 notifyme[7278] NOTE: Starting Up: localhost: 20090331150504.941 TS_ENDT {{FNEXRAD, "radar_mosaic_nathr"}} Mar 31 17:51:44 notifyme[7278] NOTE: LDM-5 desired product-class: 20090331150504.941 TS_ENDT {{FNEXRAD, "radar_mosaic_nathr"}} Mar 31 17:51:44 notifyme[7278] INFO: Resolving localhost to 127.0.0.1 took 0.00045 seconds Mar 31 17:51:44 notifyme[7278] NOTE: NOTIFYME(localhost): OK Mar 31 17:51:45 notifyme[7278] INFO: 3040396 20090331174010.388 FNEXRAD 000 radar_mosaic_nathr !grib2/unidata/UPC_255/#000/200903311739F000/N0R/0 - NONE! 000000 Mar 31 17:51:46 notifyme[7278] INFO: 3035600 20090331174409.841 FNEXRAD 000 radar_mosaic_nathr !grib2/unidata/UPC_255/#000/200903311743F000/N0R/0 - NONE! 000000 Mar 31 17:51:46 notifyme[7278] INFO: 3032484 20090331174808.702 FNEXRAD 000 radar_mosaic_nathr !grib2/unidata/UPC_255/#000/200903311746F000/N0R/0 - NONE! 000000 ^CMar 31 17:51:48 notifyme[7278] NOTE: exiting - figuring out what data your machine is receiving - figuring out what data your upstream machine(s) is(are) receiving - learning about product IDs for the products you are receiving - testing regular expression patterns that can be used in ldmd.conf request lines and pattern-action file actions An example of the last item is: Cheers, Tom -- **************************************************************************** Unidata User Support UCAR Unidata Program (303) 497-8642 P.O. Box 3000 address@hidden Boulder, CO 80307 ---------------------------------------------------------------------------- Unidata HomePage http://www.unidata.ucar.edu **************************************************************************** Ticket Details =================== Ticket ID: OLV-956032 Department: Support IDD Priority: Normal Status: Closed