Skip to content
GitLab
Projects Groups Topics 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
    • Contributor statistics
    • Graph
    • Compare revisions
  • 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
  • #70
Closed
Open
Issue created Jul 18, 2019 by Lily Romano@nrr004Owner1 of 3 checklist items completed1/3 checklist items

Split Supersaturation validation

Q: If the ss changes from scan_up to scan_down, what it the true_super_sat? The value during scan_up?

  • If change is in scan_up, invalidate
  • If change is in scan_down, no action
  • If the user validates a scan where the ss changes, the displayed ss should become the true_super_sat instead of ', '.join(map(str, np.unique(curr_scan.processed_super_sats)))
Edited Jul 23, 2019 by Lily Romano
Assignee
Assign to
Time tracking