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 Sen, Sorry for the slow reply. You sent your question to my personal UCAR email address, and it got lost with in my inbox because of lots of email related to GOES-16 imagery. In the future, it would be better to send the question to: address@hidden as there is more than one Unidata staff who reads those inquiries. re: > I am writing to ask cosmic data via LDM. The top level IDD relays that we run here in UCAR relay the COSMIC netCDF files in the EXP feed type. re: > I searched it and found one > thread about this that you answered the similar question, but I don't > know which site is the upstream site COSMIC. The following top level relays should all have the COSMIC data in the EXP feed: idd.unidata.ucar.edu iddb.unidata.ucar.edu idd.meteo.psu.edu idd.tamu.edu (but this top level relay service will be going away) re: > and also the setting on > pqact.conf. I am trying to get .nc files for WRF data assimilation purpose. Since the EXP feed type contains more than COSMIC data, you will want to restrict your LDM configuration file REQUEST to just ask for the COSMIC data: REQUEST EXP "cosmicrt" <upstream feed host> Of course, there are a number of way to process the data from any datastream, the easiest of which is to FILE the products to disk. Since we are not processing the COSMIC products, I have no ready made pattern-action file action to provide as an example, sorry. But, the simplest thing to do is: - REQUEST the data (see above) - run notifyme -vl logs/cosmic.log -f EXP -p cosmicrt for a day to capture the LDM/IDD Product Ids for the COSMIC data and then craft a pattern-action file action to FILE the data products in the disk hierarchy you want to use. 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: UYW-180327 Department: Support IDD Priority: Normal Status: Closed =================== NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.