Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
S src
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 62
    • Issues 62
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 4
    • Merge requests 4
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Code Review
    • Issue
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • OPAL
  • src
  • Issues
  • #457

Closed
Open
Created Jan 30, 2020 by snuverink_j@snuverink_jDeveloper

Dipoles in Opal-T to support quadrupole component field gradients

The following discussion from !269 (merged) should be addressed:

  • @snuverink_j started a discussion: (+3 comments)

    The commenting out was introduced by @kraus in 595b4b83 .. perhaps he can comment. Note that the class at that time was called Bend : https://gitlab.psi.ch/OPAL/src/blob/595b4b83818596b5f7a72e086cbbda4325f70aa8/src/Classic/AbsBeamline/Bend.cpp

  • @kraus The dipoles in Opal-T used to support field gradients in version 1.6 and before. When I rewrote Opal-T I disabled it to speed up the development. However it was my intention to re-enable it (but didn't happen). I still think that we should support the quadruple component.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking