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
  • #101

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

Copy frame files to run directory before starting PE

Since low-latency frame files are temporary, it is better to copy them to the run directory and make sure that those files are not removed between the time when GWCelery queries data files and the time when it starts PE. However, current lalinference_pipe does not take path to frame files as inputs. For example, when it reads the state vector, it searches for data with gwdatafind from input frame types instead of using input paths to frame types.

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#101