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

Determine VOTAN role in ingest of GCN Classic notices #2747

Open
jracusin opened this issue Dec 3, 2024 · 3 comments
Open

Determine VOTAN role in ingest of GCN Classic notices #2747

jracusin opened this issue Dec 3, 2024 · 3 comments
Assignees
Labels
classic Issues related to GCN Classic migration

Comments

@jracusin
Copy link
Contributor

jracusin commented Dec 3, 2024

Description

Study how VOTANs are used in GCN Classic and determine if decommissioning will break functionality.

Acceptance criteria

  • determine if VOTAN decommissioning will break notice ingest for LVC or other missions
  • if so, retire GCN Classic notice types or ingest VOEvent via Kafka
@jracusin jracusin added the enhancement New feature or request label Dec 3, 2024
@jracusin jracusin added this to the Decomission VTP milestone Dec 3, 2024
@jracusin jracusin self-assigned this Dec 3, 2024
@jracusin jracusin added classic Issues related to GCN Classic migration and removed enhancement New feature or request labels Dec 3, 2024
@jracusin
Copy link
Contributor Author

From Teresa: "LVC and AMON ingest VOEvent data via the lvc_receiver and amon_reciever programs. No missions ingest data directly into the VOTANS. (LVC voevent data is passed through GCN but is not processed at all. AMON voevent data is unpacked, placed in the 160 byte socket buffer, sent to gromain and unpacked."

@jracusin
Copy link
Contributor Author

We reached out to LVK and asked if they were okay with us no longer distributing VOEvent over VTP after O4, and they are. Need to reach out to AMON.

@jracusin
Copy link
Contributor Author

VOEvent will still be distributed via GCN Classic over Kafka.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
classic Issues related to GCN Classic migration
Projects
None yet
Development

No branches or pull requests

1 participant