Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PQACT question and minor documentation error #130

Open
corepuncher opened this issue Apr 18, 2024 · 0 comments
Open

PQACT question and minor documentation error #130

corepuncher opened this issue Apr 18, 2024 · 0 comments

Comments

@corepuncher
Copy link

corepuncher commented Apr 18, 2024

  1. Should be PQACT, not PQCAT (although CAT would be easier to type)

https://docs.unidata.ucar.edu/ldm/man/pqcat.html

  1. 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"

and pqact.text includes:

WMO     /p(TOR|SVR|FFW|SVS|FFS|FRW|SMW|MWS)
        PIPE    -flush -close -strip    /home/ldm/warn/decodeWarnings.php

So wondering if there are any additional flags or configurations to speed up getting the warnings.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant