Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
gwcelery
gwcelery
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 52
    • Issues 52
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 12
    • Merge Requests 12
  • Requirements
    • Requirements
    • List
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • emfollow
  • gwcelerygwcelery
  • Issues
  • #102

Closed
Open
Opened Mar 26, 2019 by Soichiro Morisaki@soichiro.morisakiDeveloper

Automatic PE followup on C01 data

It is better to launch PE runs automatically also on C01 data. One way to do it is to run a task to continuously querying for C01 data (say for 1 month) after triggers being uploaded. Also, it is possible that after PE followup on C00 data it turns out that the ini file setting is not suitable for that event. One possible solution for that is for PE ROTA people to upload better ini files to GraceDB and let GWCelery glob the most updated version of ini file for PE followups on C01 data.

cc: @vivien

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: emfollow/gwcelery#102