NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
Steve, I added -flush to the FILE action, and both GFS grib2 and GEMPAK grid files are being created. Thanks for your help with this. Before: FILE data/grib/gfs/\1/gfs.t\1z.pgrbf\2.grib2 After FILE -flush -log data/grib/gfs/\1/gfs.t\1z.pgrbf\2.grib2 Regards, Evan Lowery Evan, If the PIPE action above is working but the FILE action isn't, then I suggest adding either a "-flush" or a "-close" option to the FILE action. For more information, see <http://www.unidata.ucar.edu/software/ldm/ldm-current/basics/pqact.conf.html >. Regards, Steve Emmerson Good afternoon, Lately we've been noticing that the GFS grib2 files coming in over the LDM don't always completely download (partial or missing files). Yet, the GFS GEMPAK grid files always completely download. Our pqact is setup to both download the raw grib2 files and create GEMPAK grid files (see pqact.conf / ldmd.conf entries below) pqact.conf #GFS GRIB2 FILES (00Z) CONDUIT gfs.t(..)z.pgrbf([0-9]+).grib2 FILE data/grib/gfs/\1/gfs.t\1z.pgrbf\2.grib2 #GFS GEMPAK FILE (00Z) CONDUIT gfs.t(..)z.pgrbf([0-9]+).grib2 PIPE decoders/dcgrib2 -d data/gempak/logs/dcgrib2_CONDUITgfs.log -e GEMTBL=/data/gempak/gempak/tables data/grid/gfs/\1/gfs.t\1z.pgrbf\2.gem ldmd.conf exec "pqact -f CONDUIT etc/pqact.conf" REQUEST CONDUIT "gfs\.t00z.pgrbf.*" PRIMARY REQUEST CONDUIT "gfs\.t00z.pgrbf.*" SECONDARY I've read several support requests dealing with CONDUIT latency. One possible solution would be to split the CONDUIT feed into several streams as noted in (http://www.unidata.ucar.edu/support/help/MailArchives/idd/msg04397.html ). request CONDUIT "MT.gfs_CY.(00|12).*[05]$" idd.cise-nsf.gov PRIMARY request CONDUIT "MT.gfs_CY.(00|12).*[16]$" idd.cise-nsf.gov PRIMARY request CONDUIT "MT.gfs_CY.(00|12).*[27]$" idd.cise-nsf.gov PRIMARY request CONDUIT "MT.gfs_CY.(00|12).*[38]$" idd.cise-nsf.gov PRIMARY request CONDUIT "MT.gfs_CY.(00|12).*[49]$" idd.cise-nsf.gov PRIMARY My question is, when splitting a CONDUIT feed into several streams, how would we have to change our pqact.conf entries? Would the following syntax be correct? Before: CONDUIT gfs.t(..)z.pgrbf([0-9]+).grib2 FILE data/grib/gfs/\1/gfs.t\1z.pgrbf\2.grib2 After: CONDUIT[05]$ gfs.t(..)z.pgrbf([0-9]+).grib2 FILE data/grib/gfs/\1/gfs.t\1z.pgrbf\2.grib2 Before: CONDUIT gfs.t(..)z.pgrbf([0-9]+).grib2 PIPE decoders/dcgrib2 -d data/gempak/logs/dcgrib2_CONDUITgfs.log -e GEMTBL=/data/gempak/gempak/tables data/grid/gfs/\1/gfs.t\1z.pgrbf\2.gem After: CONDUIT[16]$ gfs.t(..)z.pgrbf([0-9]+).grib2 PIPE decoders/dcgrib2 -d data/gempak/logs/dcgrib2_CONDUITgfs.log -e GEMTBL=/data/gempak/gempak/tables data/grid/gfs/\1/gfs.t\1z.pgrbf\2.gem Thanks in advance for your help, Evan Lowery
ldm-users archives: