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.
Patrick, No. There are no grid #201 grids in the CONDUIT feed.There are only legacy 00Z MRF grid #002 (2.5 degree global) MRF grids in CONDUIT.
There is the distinct possibility that if your queue isn't large enough,you could have a problem in processing all the data before it gets overwritten in your queue if you didn't take the increased data volume
into account in your queue and pqact configuration before adding CONDUIT. Your HRS latency shows the hit in latency starting today: http://www.unidata.ucar.edu/cgi-bin/rtstats/iddstats_nc?HDS+unidata3.bgsu.edu The peak volume your weather3 host saw today was 2.8GB per hour: http://www.unidata.ucar.edu/cgi-bin/rtstats/rtstats_summary_volume?unidata3.bgsu.edu+GRAPH Check the size of your ldm product queue, and if you have any problems with the ability of your pqact processes to keep pace, consider using the separate pqact entry configurations that are generated from $NAWIPS/ldm/etc/gen_pqact.csh Steve Chiswell Unidata User Support On Wed, 2005-10-12 at 13:39, Patrick L. Francis wrote:
I just initiated conduit for the first time.. and some of my mrf_201 scripts have stopped functioning... is it possible there is more than one mrf_201 grid from more than one source that is different? ... i.e. would overwrite the exact filenames without having the same variables?
gembud archives: