llama listen lvalert
¶
Listen for new LVAlerts from GraceDB containing GW triggers. This is LIGO/Virgo’s internal infrastructure for distributing notifications about updates to all gravitational wave (GW) triggers.
usage: llama listen lvalert [-h] [-l LOGFILE]
[-v {debug,info,warning,error,critical,none}]
[-r RUNDIR] [--err-alert] [-n [NODES [NODES ...]]]
[-s SERVER]
[--list-nodes [{lvalert.cgca.uwm.edu,lvalert-playground.cgca.uwm.edu}]]
Named Arguments¶
- -r, --rundir
Change the run directory (i.e. where new LLAMA triggers are saved by the GCN handler) to this directory. Creates the directory if it does not already exist. (default: /root/.local/share/llama/current_run/)
Default: “/root/.local/share/llama/current_run/”
- --err-alert
Alert maintainers to unhandled exceptions.
- -n, --nodes
The LVAlert nodes to subscribe to. Make sure to subscribe to all the searches you are interested in. (default: {‘cbc_mbtaonline’, ‘cbc_lowmass’, ‘stc-testnode’, ‘burst_cwb’, ‘test_superevent’, ‘cbc_pycbc’, ‘cbc_gstlal’, ‘superevent’, ‘cbc_spiir’})
Default: (‘cbc_mbtaonline’, ‘cbc_lowmass’, ‘stc-testnode’, ‘burst_cwb’, ‘test_superevent’, ‘cbc_pycbc’, ‘cbc_gstlal’, ‘superevent’, ‘cbc_spiir’)
- -s, --server
The server to subscribe to. (default: lvalert.cgca.uwm.edu)
Default: “lvalert.cgca.uwm.edu”
- --list-nodes
Possible choices: lvalert.cgca.uwm.edu, lvalert-playground.cgca.uwm.edu
Print available LVAlert nodes for the given server and exit. (default: lvalert.cgca.uwm.edu)
logging settings¶
- -l, --logfile
File where logs should be written. By default, all logging produced by
llama run
goes to both an archival logfile shared by all instances of the process as well as STDERR. The archival logfile can be overridden with this argument. If you specify/dev/null
or a path that resolves to the same, logfile output will be suppressed automatically. Logs written to the logfile are always at maximum verbosity, i.e. DEBUG. (default: /root/.local/share/llama/logs/lvalert.log)Default: “/root/.local/share/llama/logs/lvalert.log”
- -v, --verbosity
Possible choices: debug, info, warning, error, critical, none
Set the verbosity level at which to log to STDOUT; the
--logfile
will ALWAYS receive maximum verbosity logs (unless it is completely supressed by writing to /dev/null). Available choices correspond to logging severity levels from thelogging
library, with the addition ofnone
if you want to completely suppress logging to standard out. (default: debug)Default: “debug”