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 Tim, re: > Hello, my name is Timothy "Connor" Nelson. I am a student at South Dakota > School of Mines and Technology. Currently, our school has an LDM set up for > Gempak; however, I need to set one up on a separate computer for field > research that a research team would be using. OK. re: > I am not the one operating > the other LDM at the University. This other one needs to be left alone and > not changed. The most efficient way (meaning the way to minimize network bandwidth use) is for one LDM at an institution to relay data to the other LDM(s). In order to do this, the ~ldm/etc/ldmd.conf file for the original machine would need to be edited to add appropriate ALLOW(s) for the other machine(s) it would relay data to. This assumes, of course, that the LDM to act as a relay has the data that the other machines want/need. re: > I'm not sure if we are qualified for IDD, You are. re: > but if we are, > here's the information for upstream data feeds required. Again, I am > setting up a separate LDM from the one our school is currently using. Thus, > we would have multiple LDM's for different computers and different projects: > ... > So, for this project (A10) here's the information: > > Site: South Dakota School of Mines and Technology > LDM Administrator: Timothy "Connor" Nelson > Phone: 740-505-1902 > email: address@hidden > hostname: MI-RM201A-03L What we need is the fully-qualified hostname and IP address of your machine. The other thing that is needed is forward (name to IP) and reverse (IP to name) DNS to be setup for your machine. When both forward and reverse DNS are available for an '.edu' machine, one is assured that feed REQUESTs to most upstream hosts will be honored/work. re: > feedtypes: FNEXRAD, WSI, NEXRAD3, NEXRAD2, NXRDSRC Comments: - the feeds of interest are not being REQUESTed by the existing SDSMT machine running the LDM, unidata.sdstate.edu This means that that your new machine would REQUEST the feeds directly from upstream feed host(s). - WSI is a proprietary point-to-point feed from WSI corporation. The WSI feed is not relayed in the Unidata IDD. - NXRDSRC is used exclusively at NCDC, it is not part of the IDD Please be aware that the remaining feeds you have indicated that you want are quite voluminous. Here is a snapshot of the feeds available in the IDD and their respective volumes: Data Volume Summary for shemp.unidata.ucar.edu Maximum hourly volume 30945.209 M bytes/hour Average hourly volume 20895.266 M bytes/hour Average products per hour 366853 prods/hour Feed Average Maximum Products (M byte/hour) (M byte/hour) number/hour NEXRAD2 7242.151 [ 34.659%] 8911.836 82024.646 CONDUIT 4246.638 [ 20.323%] 8809.083 80659.562 NEXRAD3 2292.715 [ 10.972%] 2726.845 107527.625 EXP 1723.898 [ 8.250%] 3763.579 7015.917 NGRID 1573.718 [ 7.531%] 3384.791 21996.458 FSL2 1436.051 [ 6.873%] 1609.331 1684.917 FNMOC 1102.307 [ 5.275%] 6452.797 2941.354 HDS 355.341 [ 1.701%] 616.127 18025.729 SPARE 284.263 [ 1.360%] 1728.201 10.333 NIMAGE 206.857 [ 0.990%] 405.009 219.958 FNEXRAD 122.984 [ 0.589%] 148.102 106.250 GEM 103.601 [ 0.496%] 666.644 965.000 UNIWISC 66.769 [ 0.320%] 129.483 46.146 NOTHER 53.723 [ 0.257%] 368.726 1065.208 IDS|DDPLUS 53.363 [ 0.255%] 65.480 42186.125 PCWS 18.225 [ 0.087%] 23.542 23.250 LIGHTNING 11.969 [ 0.057%] 26.679 353.021 DIFAX 0.586 [ 0.003%] 2.786 0.917 GPS 0.108 [ 0.001%] 1.345 1.042 Question: - do you have enough network bandwidth to get all of the feeds that you desire: NEXRAD2 7242.151 [ 34.659%] 8911.836 82024.646 NEXRAD3 2292.715 [ 10.972%] 2726.845 107527.625 FNEXRAD 122.984 [ 0.589%] 148.102 106.250 The reason that I ask is I seem to recall that there were bandwidth issues in the past at SDSMT. Please send us the fully qualified hostname and IP address of your new machine so that we can verifiy that DNS has been correctly setup for it. 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: WMT-338636 Department: Support IDD Priority: Normal Status: Closed