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 100
    • Issues 100
    • 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
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • lscsoft
  • gracedb
  • Issues
  • #154

Closed
Open
Created May 14, 2019 by Brandon Piotrzkowski@brandon.piotrzkowskiContributor

GRB Parameters not parsed correctly

Description of problem

An issue in Sentry has popped where trigger_duration for Fermi GRBs is missing: https://sentry.io/organizations/ligo-caltech/issues/998630013/?environment=production&query=is%3Aunresolved

Also for subthreshold Fermi GRBS trigger_duration and trigger_id is missing example: https://gracedb-playground.ligo.org/events/E22136/view/

Suggested solutions

--> We need to add more fields within populateGrbEventFromVOEventFile to handle these different events

Edited May 14, 2019 by Brandon Piotrzkowski
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None