Differences between revisions 56 and 84 (spanning 28 versions)
Revision 56 as of 2021-12-03 22:44:52
Size: 2611
Comment:
Revision 84 as of 2025-07-22 15:29:54
Size: 5469
Comment:
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
 * LIGO-Virgo Alert System (LVAlert) [[https://git.ligo.org/lscsoft/igwn-alert|igwn-alert]]  * LIGO-Virgo Alert System (LVAlert) [[https://git.ligo.org/lscsoft/igwn-alert|igwn-alert(old repo)]]  [[https://git.ligo.org/computing/igwn-alert/client|igwn-alert(git)]]
Line 6: Line 6:
  * The API are compatible with Python 3.   * The API are compatible with Python 3
 * Retirement of existing LVAlert service targeted for ~April 2022.
  * In O4, we will use igwn-alert.
Line 9: Line 11:
 * The latest version is 0.1.1 (2021/11/19)  * The latest version is 0.7.0 (2025/07/22)
Line 11: Line 13:
pip install igwn-alert conda install igwn-alert==0.7.0
Line 13: Line 15:
Line 17: Line 20:
usage: igwn-alert [-h] [-g GROUP] [-l {critical,error,warning,info,debug}] [-n NETRC] [-s SERVER] [-u USERNAME] {listen,subscriptions,topics,unsubscribe,send} ... usage: igwn-alert [-h] [--no-auth] [-g GROUP] [-c CONSUMER_GROUP] [-j] [-l {critical,error,warning,info,debug}] [-n NETRC] [-p PORT] [-r] [-s SERVER]
                  [-t LISTEN_RETRIES
] [-u USERNAME] [-w RETRY_WAIT] [-V]
                 
{listen,subscriptions,topics,unsubscribe,send} ...
Line 28: Line 33:
optional arguments: options:
Line 30: Line 35:
  --no-auth If set, disable authentication.
Line 32: Line 38:
  -c CONSUMER_GROUP, --consumer-group CONSUMER_GROUP
                        Consumer group ID to use for consuming messages across sessions
  -j, --jsonpp Output pretty print json
Line 36: Line 45:
  -p PORT, --port PORT igwn-alert server port
  -r, --retry-on-fatal reconnect listener on fatal exceptions
Line 38: Line 49:
  -t LISTEN_RETRIES, --listen_retries LISTEN_RETRIES
                        fatal reconnect retry attempts
Line 40: Line 53:
  -w RETRY_WAIT, --retry_wait RETRY_WAIT
                        fatal reconnect retry attempts
  -V, --version show program's version number and exit
Line 43: Line 59:
== Setting in advance == == Setting in advance on web ==
Line 47: Line 63:
   * After log-in [[https://my.hop.scimma.org/|https://my.hop.scimma.org/]], by clicking {{{Hopskotch}}} and {{{Create new credentials}}}, the password for your account will be shown just once.
Line 49: Line 65:
== Usage ==
== Adding Authentication in local ==
 * Run the {{{hop}}} command and enter the username and the password.
  * Empty Hostname is fine.
 {{{
hop auth add
 }}}
 * Once you entered, the authentification credential is stored in {{{~/.config/hop/auth.toml}}} .

 * Note that in the authentification credential is connected to conda environment. You can see the environment name in {{{~/.config/hop/auth.toml}}}.
  * If you make new conda environment, you should run

  {{{
hop auth add --force
  }}}

== Usage in local ==
 * Initially, no topic (you can consider channel) is registered to your account.
  * From [[https://my.hop.scimma.org/|https://my.hop.scimma.org/]], please add channel (they call `Add permission`).

 * This doesn't show anything.

 {{{
% igwn-alert topics
Topics for group gracedb associated with the current credential:
 }}}

== Receive alert from MDC (Mock Data Challenge) analysis ==
 * Follow [[https://o4-dqr.docs.ligo.org/o4-dqr-configuration/#setting-up-igwn-alert-to-test-taskmanager|instruction by Joe]].

 * If you set up properly, check the topics which you are subscribing.
 {{{
% igwn-alert --group gracedb-playground topics
Topics for group gracedb-playground associated with the current credential:
mdc_superevent
cbc_pycbc

 }}}

 * Launch the igwn-alert
 {{{
% igwn-alert --g gracedb-playground listen
 }}}

 * To see the MDC alert on gracedb (2022/02/09), visit [[https://gracedb-playground.ligo.org/latest/?query=mdc&query_type=S|gracedb-playground]] (Require log-in).
Line 54: Line 114:
 * [[https://lscsoft.docs.ligo.org/igwn-alert/|igwn-alert document]]
 * [[https://git.ligo.org/lscsoft/igwn-alert|git repo, igwn-alert]]
 * [[KAGRA/Subgroups/DET/LVAlert_python2 |LVAlert instruction for python2]]
 * [[https://lscsoft.docs.ligo.org/igwn-alert/|igwn-alert, documentation outlining API]]
 * [[https://lscsoft.docs.ligo.org/igwn-alert/guide.html|igwn-alert, user guide for how to get started]]

 * [[KAGRA/Subgroups/DET/LVAlert_python2 |LVAlert instruction for python2 (out of date)]]
Line 59: Line 120:

 * [[https://git.ligo.org/emfollow/userguide|LIGO/Virgo Public Alerts User Guide (not igwn-alert)]]

Introduction

  • LIGO-Virgo Alert System (LVAlert) igwn-alert(old repo) igwn-alert(git)

    • The International Gravitational Wave Network Alert System (igwn-alert) is a notification service built on the Apache Kafka protocol and the pubsub extension.
    • It is a higher-level modification of SCIMMA's hop-client to streamline receiving and responding to alerts from GraceDB.
    • This package replaces the legacy LIGO LVAlert XMPP-based alert system.
    • The API are compatible with Python 3
  • Retirement of existing LVAlert service targeted for ~April 2022.
    • In O4, we will use igwn-alert.

Install

  • The latest version is 0.7.0 (2025/07/22)
    conda install igwn-alert==0.7.0
  • help
    % igwn-alert -h
    usage: igwn-alert [-h] [--no-auth] [-g GROUP] [-c CONSUMER_GROUP] [-j] [-l {critical,error,warning,info,debug}] [-n NETRC] [-p PORT] [-r] [-s SERVER]
                      [-t LISTEN_RETRIES] [-u USERNAME] [-w RETRY_WAIT] [-V]
                      {listen,subscriptions,topics,unsubscribe,send} ...
    
    positional arguments:
      {listen,subscriptions,topics,unsubscribe,send}
                            sub-command help
        listen              Listen for igwn-alert messages and print them to stdout.
        subscriptions       List your subscriptions
        topics              List available pubsub topics
        unsubscribe         Unsubscribe from one or more topics
        send                publish contents of a file to a pubsub topic
    
    options:
      -h, --help            show this help message and exit
      --no-auth             If set, disable authentication.
      -g GROUP, --group GROUP
                            GraceDB group name (e.g., gracedb, gracedb-playground)
      -c CONSUMER_GROUP, --consumer-group CONSUMER_GROUP
                            Consumer group ID to use for consuming messages across sessions
      -j, --jsonpp          Output pretty print json
      -l {critical,error,warning,info,debug}, --log {critical,error,warning,info,debug}
                            Log level
      -n NETRC, --netrc NETRC
                            netrc file (default: read from NETRC environment variable or ~/.netrc)
      -p PORT, --port PORT  igwn-alert server port
      -r, --retry-on-fatal  reconnect listener on fatal exceptions
      -s SERVER, --server SERVER
                            igwn-alert server hostname
      -t LISTEN_RETRIES, --listen_retries LISTEN_RETRIES
                            fatal reconnect retry attempts
      -u USERNAME, --username USERNAME
                            User name (default: look up in auth.toml or .netrc)
      -w RETRY_WAIT, --retry_wait RETRY_WAIT
                            fatal reconnect retry attempts
      -V, --version         show program's version number and exit

Setting in advance on web

  • The authentification between the client and the server is managed by SciMMA.
  • The first step is to make a SCiMMa account by visiting https://my.hop.scimma.org/.

    • At this time, access to igwn-alert is limited to LIGO, Virgo, or KAGRA members.
  • After log-in https://my.hop.scimma.org/, by clicking Hopskotch and Create new credentials, the password for your account will be shown just once.

Adding Authentication in local

  • Run the hop command and enter the username and the password.

    • Empty Hostname is fine.
    hop auth add
  • Once you entered, the authentification credential is stored in ~/.config/hop/auth.toml .

  • Note that in the authentification credential is connected to conda environment. You can see the environment name in ~/.config/hop/auth.toml.

    • If you make new conda environment, you should run
      hop auth add --force

Usage in local

  • Initially, no topic (you can consider channel) is registered to your account.
  • This doesn't show anything.
    % igwn-alert topics
    Topics for group gracedb associated with the current credential:

Receive alert from MDC (Mock Data Challenge) analysis

  • Follow instruction by Joe.

  • If you set up properly, check the topics which you are subscribing.
    % igwn-alert --group gracedb-playground topics
    Topics for group gracedb-playground associated with the current credential:
    mdc_superevent
    cbc_pycbc
  • Launch the igwn-alert
    % igwn-alert --g gracedb-playground listen
  • To see the MDC alert on gracedb (2022/02/09), visit gracedb-playground (Require log-in).

KAGRA/Subgroups/DET/LVAlert (last edited 2025-07-22 15:29:54 by HirotakaYuzurihara)