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

Hermes features are not available for non-GW nonlocalized events #1130

Open
griffin-h opened this issue Dec 3, 2024 · 0 comments
Open

Hermes features are not available for non-GW nonlocalized events #1130

griffin-h opened this issue Dec 3, 2024 · 0 comments
Labels
bug Something isn't working User Issue Raised by a user

Comments

@griffin-h
Copy link
Contributor

Describe the bug
We would like to use the tom_nonlocalizedevents app to ingest alerts from other types of nonlocalized events. In this case, I give an example of an x-ray transient from the Einstein Probe: EP241201a. I understand that not all the page templates are set up to handle non-GW events (e.g., the parameters at the top and the GraceDB images); this is not the subject of the current issue. However, one of the best features of tom_nonlocalizedevents is its integration with Hermes to display related GCN circulars. This does not currently seem to work for non-GW events, but I am not sure if the issue is with tom_nonlocalizedevents or with Hermes itself.

To Reproduce
Steps to reproduce the behavior:

  1. Create a nonlocalized event that is not a gravitational wave, e.g., EP241201a.
  2. From the nonlocalized event list, click on that event name to go to its detail page.
  3. See that no Hermes messages are listed in the table on the detail page.
  4. Back on the nonlocalized event list, click on the Hermes link.
  5. See the error message on Hermes that this nonlocalized event does not exist

Expected behavior
As for GW events, I would expect these events to have Hermes messages listed on their detail pages. For this particular event, I see three related GCN circulars in Hermes. I confirmed that the eventId field is being parsed correctly in the "extra keypairs" section.

Screenshots
image
image
image
image

Desktop (please complete the following information):

  • OS: macOS Sequoia 15.1.1
  • Browser: Firefox 133.0
  • Python Version: 3.10.12

Additional context
For the time being, I'm using event_type=UNKNOWN for these x-ray transients, as the only other choices are GRB, GW, or neutrino. This is probably not causing the problem, but I mention it for debugging purposes.

@griffin-h griffin-h added the bug Something isn't working label Dec 3, 2024
@github-project-automation github-project-automation bot moved this to Triage in TOM Toolkit Dec 3, 2024
@jchate6 jchate6 added the User Issue Raised by a user label Dec 3, 2024
@jchate6 jchate6 moved this from Triage to Backlog in TOM Toolkit Jan 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working User Issue Raised by a user
Projects
Status: Backlog
Development

No branches or pull requests

2 participants