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 5
    • Merge requests 5
  • 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
  • #750

Closed
Open
Created Feb 13, 2023 by snuverink_j@snuverink_jDeveloper

Trimcoil implementation bug

Summary

In #276 (closed) and !53 (merged) a trim coil range in the azimuthal direction was introduced. However, this was not properly tested and it contained a bug, that was discovered by @zhang_h. This was partly fixed in #736 (closed) / !598 (merged), but not completely tested.

What is the current bug behavior?

The trim coils do not work anymore without PHIMIN and PHIMAX specified.

What is the expected correct behavior?

Trim coils working as normal.

Possible fixes

The bug was introduced in 77c975dc, especially the default value of PHIMAX was not specified (77c975dc) and the TrimCoil::setAzimuth method was not so well implemented (77c975dc).

Assignee
Assign to
2023.1
Milestone
2023.1
Assign milestone
Time tracking