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 Paul and Brice, re: you should be able to feed FNMOC data now > And there was much rejoicing! :-) > I set up a request for the FNMOC feedset and we are seeing products. Excellent. > Tom, can you direct me to documentation with the file descriptions? I > can probably figure it out but would be easier if it's documented somewhere. Here are some web references that should help (last URLs in a chain are the operative ones): Unidata HomePage http://www.unidata.ucar.edu Data http://www.unidata.ucar.edu/data Real Time Model Data - FNMOC http://www.unidata.ucar.edu/data/fnmoc_data_2.html How to get this data? http://www.unidata.ucar.edu/data/fnmoc_data_3.html Data via the LDM http://www.unidata.ucar.edu/software/ldm/ldm-current/basics/feedtypes/index.html NOGAPS and COAMP model output from FNMOC http://www.unidata.ucar.edu/software/ldm/ldm-current/basics/feedtypes/nogaps_coamps.html Ancillary Data Description http://www.usgodae.org/ re: > Paul, thanks for running that. I've been swamped over here and the pit seems > to be getting deeper. I know the feeling :-) > Tom, the last part of your email on this subject was a > list of IP's that you would like to have access into our system. The > firewall does not currently block incoming 388 traffic; that is left to the > LDM config. OK. Just so you know: I am still unable to do a 'ldmping' or 'notifyme' to what I think is your LDM machine, xxx.xxx.xxx.xxx. > So Paul, that is something that you will need to update on your > side unless you want me to do it. Also, I haven't looked into the rtstats > set up, but again that would be in the configuration file. Tom, I imagine > that the reason that ldmping and notifyme would work when you tried was that > the requestor was not in the ldmd.conf. So we should be able to set all of > that up at the same time. Paul, let me know what you need. Paul: you should should be able to see if my 'ldmping' to xxx.xxx.xxx.xxx from yakov.unidata.ucar.edu was denied by the LDM. If you see a Denying message, it will mean that the LDM configuration file, ~ldm/etc/ldmd.conf, will need to be modified to ALLOW us to REQUEST data. If you do _not_ see such a Denying log message, and assuming that your LDM logging is actually working (may seem silly, but I spend way too much time getting folks to correctly setup syslogd logging for LDM use), it would mean that there is likely some sort of firewall block of the packets coming from my machine to yours. 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: ICA-648762 Department: Support IDD Priority: Normal Status: Closed