Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
bayeswave
bayeswave
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 24
    • Issues 24
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 4
    • Merge Requests 4
  • 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
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • lscsoft
  • bayeswavebayeswave
  • Issues
  • #97

Closed
Open
Created Aug 13, 2020 by James Clark@james-clarkMaintainer

Override datafind server for OSG jobs

bayeswave_pipe has a hardcoded datafind server (datafind.ligo.org:443) whenever the --osg-deploy flag is issued. Make this optional.

For that matter, the --osg-deploy option should probably be deprecated or just cause the datafind server to default to the one above: there aren't really any functional differences in the submit files any more.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None