Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
G
gracedb
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 99
    • Issues 99
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 1
    • Merge Requests 1
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • lscsoft
  • gracedb
  • Issues
  • #167

Closed
Open
Opened Aug 01, 2019 by Brandon Piotrzkowski@brandon.piotrzkowskiContributor

Add RAVEN fields to VOEvent

Description of feature request

RAVEN is being approved to send alerts, so we need to add some additional fields to the existing VOEvent to properly communicate with astronomers. These fields are described in emfollow/userguide!65 (closed). There are seven additional fields.

External GCN Notice ID, External Alert Type, and External Search are essential and should be required. Time and Sky Position Coincidence FAR, Combined Sky Map, and Time Difference are optional and should be included only if the values are available. Time Coincidence FAR needs to be included if the search field of the external event is GRB or SubGRB, but not if the search is SNEWS since that value won't be calculated in that case. If that isn't possible then Time Coincidence FAR could be made optional in general. Note that if Time and Sky Position Coincidence FAR is available, Time Coincidence FAR will alway be available as well.

I can't see any default values that could be set that wouldn't cause confusion.

Use cases

This template should be used whenever we are creating a VOEvent and EM_COINC is present in the superevent's labels.

Edited Aug 05, 2019 by Tanner Prestegard
To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: lscsoft/gracedb#167