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.
Nancy, http://www.unidata.ucar.edu/projects/idd/status/idd/mcidasTopo.html If this is where you are looking, I can see your problem.... These are the old pqbinstats, and there are many issues with them. Hence the demand for the rtstats.. Please see: http://www.unidata.ucar.edu/staff/chiz/rtstats/ For the latest and greatest...to be "seen" here the rtstats line I provided must be in your ldmd.conf..and then re-start the ldm.. Thank you, -Jeff ____________________________ _____________________ Jeff Weber address@hidden Unidata Support PH:303-497-8676 COMET Case Study Library FX:303-497-8690 University Corp for Atmospheric Research 3300 Mitchell Ln http://www.unidata.ucar.edu/staff/jweber Boulder,Co 80307-3000 ________________________________________ ______________________ On Mon, 24 Mar 2003, Nancy Selover wrote: > Jeff, > I am running LDM 6.0.2 and it seems to be working fine, and I think I am > getting all the data, but when I go to the Unidata webpage to check the > latencies between nimbus (my current feed site) and mothra (my server), I > see it says no report for McIdas (I am getting the current satellite data), > and it looks pretty bad for the other products, but I am getting them. Why > would McIdas say "no report" when I have reports for the other products? I > have the crontab running "dostats" at 35 minutes after the hour. Does your > program need to know I am feeding from nimbus now, instead of thelma? > Anyway, I think I'm doing okay, but your stats indicate otherwise. Is > there something else I forgot to do when I brought up the new LDM version? > > Also, I appreciate your looking into the "busy" process for me. I found I > couldn't run Gempak on this machine even when "busy" had been killed. It > still said I had insufficient memory. > > Thanks, > Nancy > address@hidden >