The Unidata Local Data Manager (LDM) system includes network client and server programs designed for event-driven data distribution, and is the fundamental component of the Unidata Internet Data Distribution (IDD) system.
2) Is there any way to prioritize processing (or otherwise speed up) certain products? For example, could a check for tornado warnings be prioritized over other products? If so, where would the configuration lie?
I noticed this on the website:
-i time Polling interval, in seconds. Check for new products in the product queue every time seconds. When pqact is run in the same process group as the programs that insert products into the product queue, a signal informs pqact and all other interested processes in the process group whenever a new product is available, so polling is not necessary in this case. The default interval is 15 seconds. If time is 0, then the process will exit when it hits the end of the product-queue.
That sounds promising, but not sure where to implement. We have plenty of CPU and RAM so hoping to run as fast as humanly possible.
For example in ldmd.conf I have:
EXEC "pqact -f WMO etc/pqact.text"
1) Should be PQACT, not PQCAT (although CAT would be easier to type)
https://docs.unidata.ucar.edu/ldm/man/pqcat.html
2) Is there any way to prioritize processing (or otherwise speed up) certain products? For example, could a check for tornado warnings be prioritized over other products? If so, where would the configuration lie?
I noticed this on the website:
That sounds promising, but not sure where to implement. We have plenty of CPU and RAM so hoping to run as fast as humanly possible.
For example in ldmd.conf I have:
EXEC "pqact -f WMO etc/pqact.text"and pqact.text includes:
So wondering if there are any additional flags or configurations to speed up getting the warnings.