Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
  • Sign in
G
gracedb
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
    • Cycle Analytics
    • Insights
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
    • Locked Files
  • Issues 91
    • Issues 91
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 1
    • Merge Requests 1
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Security & Compliance
    • Security & Compliance
    • Dependency List
  • Packages
    • Packages
    • Container Registry
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • lscsoft
  • gracedb
  • Issues
  • #34

Closed
Open
Opened Aug 20, 2018 by Tanner Prestegard@tanner.prestegard
  • Report abuse
  • New issue
Report abuse New issue

Some improvements to the performance summary

Started by Branson, August 18, 2015. Copied from redmine (https://bugs.ligo.org/redmine/issues/2382)

From Erik:

Hi again,

The performance summary is nice. You might want to qualify "status" with "status", or whatever is the appropriate word for that... Maybe once there, it will be helpful to have the actual string corresponding the the "status". BTW, any reason for picking the 3-day stride for these statistics? If such stride is a parameter to the script that populates that page, you might want to keep a few strides run in parallel... say, a day, week, since the beginning of the run?

Thanks, --Erik

Edited Aug 20, 2018 by Tanner Prestegard

Related issues

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
4
Labels
enhancement long-term rework suggestion
Assign labels
  • View project labels
Reference: lscsoft/gracedb#34