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 Elmer, re: > Apparently I am still doing something wrong. I set up the ldmd.conf > entry as > request FNEXRAD "^rad/NEXRCOMP/1km/n0r_*" idd.cise-nsf.gov I think that this request line is the culprit. In order to match, the '*' would have to be '.*'. Your regular expression is asking for all products whose headers begin with '^rad/NEXRCOMP/1km/n0r_' AND are followed by multiple '-'; this is not what you want. Also, it is unnecessary to specify the '.*' to match the rest of the header since that is the default for regular expression matching. I would change the request to: request FNEXRAD "^rad/NEXRCOMP/1km/n0r_" idd.cise-nsf.gov and then stop and restart your LDM: ldmadmin restart > ( I notice > that your example didn't have " " around the productid but the others I > have that are running do). The quotes around the regular expression pattern are not needed _IF_ the pattern does not contain any spaces (so it reads as a single string of characters/numbers/etc.). > running notifyme -vxl- -f FNEXRAD returns > Jul 26 12:44:32 notifyme[922]: Starting Up: localhost: > 20070726124432.953 TS_ENDT {{FNEXRAD, ".*"}} > Jul 26 12:44:32 notifyme[922]: Connected to upstream LDM-5 > NOTIFYME(localhost) returns OK > Jul 26 12:44:32 notifyme[922]: NOTIFYME(localhost): OK > which is consistent with results from feeds that are know to be > working, so that much looks good. Yes, but were any products listed? > the pqact.conf entry is > FNEXRAD ^rad/NEXRCOMP/(...)/(...)_(........)_(....) > FILE -close /data/radar/\1/\2/\2_\3_\4 > the space between FNEXRAD and ^ is a tab, as is the spaces before and > after FILE and between -close and /, this looks like it should work but > it doesn't. Your pattern looks OK (assuming that tabs are used were needed). > Any ideas? I think that the problem is your request line. > I have also tried the pqact.conf entry as > FNEXRAD ^rad/NEXRCOMP/(...)/(...)_(........)_(....) > FILE -close /data/radar/\1 > with the same no result. You could change the request line to ".*" just to convince yourself that your pqact.conf action is OK. I believe, however, that as soon as you remove the '*' from the request, things will work as desired. 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: BJE-199821 Department: Support IDD Priority: Normal Status: Closed