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 Heather, re: > You are right: there are remnants of SSEC mcidas on our old decoder! This would explain a lot! re: > Yes, feel free to log onto the npingest machine and poke around at my > settings. It would be beneficial to us to know if something is wrong. > Let me know what you find! I did login, and I did make a couple of changes: - changed the gateway in /etc/sysconfig/static-routes to be the IP of your eth1 interface This was as per my system administrator when we were setting up a new NOAAPort ingest machine here in Unidata yesterday. I made the routing change active by: <as 'root'> route add -net 224.0.0.0 netmask 240.0.0.0 gw 192.168.0.10 eth1 route del -net 224.0.0.0 netmask 240.0.0.0 gw 192.168.0.1 eth netstat -rn Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 10.2.15.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth1 224.0.0.0 192.168.0.10 240.0.0.0 UG 0 0 0 eth1 0.0.0.0 10.2.15.1 0.0.0.0 UG 0 0 0 eth0 - changed your LDM queue size from 2G to 8G This will help in rejecting duplicate products coming across the NOAAPort broadcast. We have been seeing lots of duplicated products lately especially in the NGRID datastream (which comes from the nwstg2 channel of NOAAPort). Our interpretation of the large number of duplicates is that WFOs are requesting retransmits of the data because they did not receive them correctly (but this is just a theory on our part; it has not (yet) been proven to be fact). - stopped and restarted your LDM <as 'ldm'> - changed the LDM queue size in ~ldm/etc/registry.xml ldmadmin stop && ldmadmin delqueue && ldmadmin mkqueue && ldmadmin start re: > My plan is to monitor the system for a week: record C/N and sig strength > at intervals throughout the day, and record the number of Gaps in our feed > before we call our satellite guy out. This is a good plan! I wrote a Tcl script that records a number of things off of our S300Ns and gets the position of the satellite providing the NOAAPort broadcast once per minute. I can install this for you on npingest if you like. I am also working on a Python script that will plot relevant things (signal vs time, signal vs sat_lat, signal vs sat_lon, sat_lat vs sat_lon, C/N vs time, etc.). My goal is to incorporate #Gaps/minute into this log so that we can plot #Gaps vs C/N, etc. This should give us a enough information to know when the satellite setup needs servicing. 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: CKA-730646 Department: Support McIDAS Priority: Normal Status: Closed