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
  • Issues
  • #468

Closed
Open
Created Feb 17, 2020 by kraus@krausDeveloper

Format of _ElementPositions.sdds files wrong

Summary

The format of the data values in _ElementPositions.sdds is wrong. The numbers are written with std::ios_base::hex instead of std::ios_base::dec.

Steps to reproduce

Run any input file for OPAL-T and check the data in the SDDS file.

What is the current bug behavior?

The data look like this:

&data
        mode=ascii,
        no_row_counts=1
&end
1
OPAL 2.1.0 git rev. #a23b3950ffa3756d157d4e41dc04569663c2eb13
opal-t
0x1.f97b4a2339c0ep+4            0x0p+0          0x0p+0          0x0p+0          0x0p+0          0x0p+0          0x0p+0          0x0p+0          0x0p+0          0x0p+0          0x0p+0          ""
0x1.037cd7b767d82p+5            0x0p+0          0x0p+0          0x0p+0          0x0p+0          0x0p+0          0x0p+0          0x0p+0          0x0p+0          0x0p+0          0x0p+0          ""
0x1.037cd7b767d82p+5            0x0p+0          0x0p+0          0x0p+0          0x0p+0          0x0p+0          0x0p+0          0x0p+0          0x0p+0          0x0p+0          0x1p+0          "D69"

What is the expected correct behavior?

The data should start with lines similar like this:

&data
        mode=ascii,
        no_row_counts=1
&end
1
OPAL 2.1.0 git rev. #a23b3950ffa3756d157d4e41dc04569663c2eb13
opal-t
31.5926000000           0.0000          0.0000          0.0000          0.0000          0.0000          0.0000          0.0000          0.0000          0.0000          0.0000          ""
32.4359583214           0.0000          0.0000          0.0000          0.0000          0.0000          0.0000          0.0000          0.0000          0.0000          0.0000          ""
32.4359583214           0.0000          0.0000          0.0000          0.0000          0.0000          0.0000          0.0000          0.0000          0.0000          1.0000          "D69"
Edited Feb 17, 2020 by kraus
Assignee
Assign to
OPAL 2.4.0
Milestone
OPAL 2.4.0 (Past due)
Assign milestone
Time tracking