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 Martha, re: > I have tried to replace all spaces with tabs, and I do use vi and used > your tip of searching on TAB. I just opened the ldmd.conf.txt file that > I'm attaching in wordpad and the TABS are there. OK. I'll take a look later. I had a slight omission in the reply I sent late last night. I meant to say that you were excluding the CONDUIT feed from being processed by pqact.thredds.tasc in the 'exec' line in ~ldm/etc/ldmd.conf: exec "pqact -f ANY-CONDUIT-NNEXRAD-CRAFT /usr/local/ldm/etc/pqact.thredds.tasc What you want is: exec "pqact -f ANY-NNEXRAD-CRAFT /usr/local/ldm/etc/pqact.thredds.tasc or something that approximates this. Remember that after making any changes to ldmd.conf, you must restart your LDM for the changes to take effect. > To recap what we are trying to do that is still not working > > (1) Capture SREF data via pqact.thredds.tasc. It started working with > the pqact file we sent yesterday, but it was filing it with the > incorrect name. We made some changes based on a UNIDATA mail archive > search and we are now waiting for the 15Z data to come in to see if our > changes worked. OK. > Here is what we are doing now to process the SREF: > > NGRID ^[LM]..... KWBL ([0-3][0-9])([0-2][0-9][0-6][0-9]) > FILE > /data/pub/native/grid/NCEP/SREF/(\1:yyyy)(\1:mm)\1\2_sref.grib2 > Does this look like an appropriate syntax based on what you see in the > SREFnotifymefromnoaaport.log file I have attached? Yes, but I will try it out on my own system to make sure (later tonight). > (2) Capture CONDUIT GEFS data via pqact.thredds.tasc. We are having no > luck with this though we do see GEFS data coming in from the notifyme to > the nsf.gov server. Do you see the GEFS data coming into _your_ machine? Try running 'notifyme' and leave it running and logging to a file to make sure that you are receiving the data you want. By the way, the pattern you are using in your ~ldm/etc/ldmd.conf REQUEST line for CONDUIT data: request CONDUIT "(gefs)" idd.cise-nsf.gov can be simplified to: request CONDUIT "gefs" idd.cise-nsf.gov Again, if you change this, you will need to stop and restart your LDM. > See enclosed GEFS.log for what we are observing. > > # CONDUIT Global_1p0deg_Ensemble > CONDUIT /data/nccf/com/gens/prod/gefs\.(........)/(..)/pgrb2a > FILE > /data/pub/native/grid/NCEP/GFS/Global_1p0deg_Ensemble/GFS_Global_1p0deg_ > Ensemble_\2_\100.grib2 > > I think we got this from a previous pqact.thredds.conduit file you sent. Please check the pattern in this pattern-action to make sure that you are actually receiving those products on your own machine: <as 'ldm'> notifyme -vl- -f CONDUIT <- verify that you are actually receiving CONDUIT data notifyme -vl- -f CONDUIT -p /data/nccf/com/gens/prod/gefs <- verify that your pattern matches products being received The other thing you can do to really troubleshoot is: - extract just the CONDUIT action into its own patter-action file - add a new exec line to ldmd.conf that sends CONDUIT data to that single-purpose pattern-action file - stop and restart your LDM 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: WFA-619667 Department: Support IDD Priority: Normal Status: Closed