Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • L LILAC
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 55
    • Issues 55
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • LILAC
  • LILAC
  • Issues
  • #2
Closed
Open
Issue created May 31, 2019 by Lily Romano@nrr004Owner

Supersaturation always appears as 0.2

View correct supersaturation on the Scan Information screen. Complications arise from the fact this value is not consistent across the entire scan.

Always appears as 0.2

Connected to issue #13 (closed)

  • The scan checks to see if all values in the scan match the first value. If it doesn't match the first value, then the scan is marked invalid with an error code of 7 scan.Scan.post_align_self_test()
Edited Jun 15, 2019 by Lily Romano
Assignee
Assign to
Time tracking