Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
N
ndscope
  • 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
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • CDS
  • ndscope
  • Issues
  • #150

Closed
Open
Opened Jul 07, 2020 by Gautam Venugopalan@gautam.venugopalanContributor

Channels switched on startup

Sometimes, the channels plotted and the window titles/legends get mixed up, so while I think I'm looking at one signal, it is in fact a different one (e.g. plot legend might say C1:LSC-CARM_B_IN1 is being plotted whereas the signal is actually C1:LSC-DARM_B_IN1). Often, the signal characteristics are different enough that one can clearly identify that there is a problem, but sometimes, several painful hours can be lost before realizing that this is happening.

I've personally only observed this when starting up from a yaml file, I'll make a note if I ever happen to see it when launching with the channel list as the command line argument. I haven't seen any clues as to what could be the underlying cause, will update if I do.

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: cds/ndscope#150