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 61
    • Issues 61
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 3
    • Merge requests 3
  • 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
  • Merge requests
  • !158

Closed
Created Jul 27, 2019 by kraus@krausDeveloper
  • Report abuse
Report abuse

Improve ElementPositionWriter

  • Overview 0
  • Commits 10
  • Changes 25

The current implementation of the computation of the data for the ElementPositionWriter and fix a problem with the existing implementation: currently the rows are written as if all elements in a "sector" start and and simultaneously, see the following example

      0.11569476         0     0     0     0     0     0     0     0     1     1 "WEDGE1, MDEGD1"
      0.11931035         0     0     0     0     0     0     0     0     1     1 "WEDGE1, MDEGD1"
      0.11931035         0     0     0     0     0     0     0     0     1     1 ""
      0.11931035         0     0     0     0     0     0     0     0     1     1 ""
      0.11931035         0     0     0     0     0     0     0     0     1     1 "MDEGD1, DEGD1"
      0.12111484         0     0     0     0     0     0     0     0     1     1 "MDEGD1, DEGD1"

The correct output should be

0.115694755         0       0       0       0       0       0       0       0       1       1       "MDEGD1, WEDGE1"
0.1193103499        0       0       0       0       0       0       0       0       1       1       "MDEGD1, WEDGE1"
0.1193103499        0       0       0       0       0       0       0       0       1       0       "MDEGD1"
0.1193103499        0       0       0       0       0       0       0       0       1       0       "MDEGD1"
0.1193103499        0       0       0       0       0       0       0       0       1       1       "MDEGD1, DEGD1"
0.121114842         0       0       0       0       0       0       0       0       1       1       "MDEGD1, DEGD1"

The columns in these two extracts are position, different multipole magnets (dipole to decapole and everything above), solenoids, rfcavities, monitors and others (such as degraders). Ignore the different formatting but notice the second last column (others) in the two rows with "" (first extract from old implementation) which should be 0 instead of 1.

Assignee
Assign to
Reviewer
Request review from
None
Milestone
None
Assign milestone
Time tracking
Source branch: SDDSWriterLossDataSink