Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • Allen Allen
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 182
    • Issues 182
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Jira
    • Jira
  • Merge requests 52
    • Merge requests 52
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • LHCb
  • AllenAllen
  • Issues
  • #310
Closed
Open
Created Mar 25, 2022 by Anton Poluektov@poluektDeveloper

Data from Allen for VELO closing

As discussed at the RTA management meeting, I'm creating this issue to discuss what data the HLT1 needs to provide for VELO closing procedure. Our current understanding is that VELO will need a beam-beam minimum bias line. What rate should we aim for? Who is responsible from the VELO side for providing the configuration?

Tagging @gligorov, @mvesteri, @raaij, @mjohn, @rmohamme, @tszumlak, @njurik. Please feel free to add is I missed anyone.

Assignee
Assign to
Time tracking