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.
Doug, > ECMWF and NCAR are still having problems receiving complete NCEP gefs > and TIGGE > forecasts via the CONDUIT feed. Below are some counts recorded at > NCAR over the past > few days. We expect to receive 27896 fields (grib messages) per > forecast cycle. > > 31 product(s) out of 27896 are missing z_tigge_c_kwbc_20061115120000 > All 27896 products are here z_tigge_c_kwbc_20061115180000 > All 27896 products are here z_tigge_c_kwbc_20061116000000 > 11528 product(s) out of 27896 are missing z_tigge_c_kwbc_20061116060000 > All 27896 products are here z_tigge_c_kwbc_20061116120000 > 13 product(s) out of 27896 are missing z_tigge_c_kwbc_20061116180000 > > > Volume should not be causing the problem as 143 GB are > being transferred between ECMWF and NCAR daily, with rarely any > missing forecast fields. > > Here's our current REQUEST structure in ldmd.conf: > > REQUEST CONDUIT "data/nccf/com/gens/.*" idd.unidata.ucar.edu > REQUEST CONDUIT "TIGGE.*" idd.unidata.ucar.edu Just for your edification, the ".*" suffixes in the ERE-s are superfluous: they add nothing. I don't know much about the product-identifiers in the CONDUIT stream. Are the two sets of data-products in the REQUEST entries disjoint? Is "idd.unidata.ucar.edu" the only upstream site from which your LDM receives CONDUIT data? > Also, > How do other CONDUIT users go about refilling missing fields? > It's essential for NCEP's participation in this project that the > TIGGE archive centers receive > a complete set of fields for each available forecast cycle. > > Any help you can provide will be greatly appreciated. > > Regards, > Doug Regards, Steve Emmerson Ticket Details =================== Ticket ID: PID-182040 Department: Support IDD TIGGE Priority: Normal Status: On Hold