Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • C cmsgemos
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 100
    • Issues 100
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 14
    • Merge requests 14
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • cmsgemonline
  • gem-daq
  • cmsgemos
  • Issues
  • #52

Closed
Open
Created May 01, 2020 by Laurent Petre@lpetreOwner

Hardware state after transitions is not clearly defined

Summary

The state of the VFAT and event builder after the "Halt" transition are not set to a non running state. We need to establish and document if this is the desired behavior, possibly based on the official RCMS function manager documentation.

The fix can be applied before or after the migration to the new architecture. In any case this work will have to be conducted.

Steps to reproduce

  1. Start a normal data-taking run
  2. Click on the "Halt" button in GEMSupervisor
  3. Look at the DAQ_ENABLE register and CFG_RUN registers

What is the expected correct behavior?

The status of the hardware should be clearly defined after each FSM transition.

Environment

  • Version used: a9c84a4c with !22 (merged) and !14 (merged)
  • Operation System: cc7 on gem904daq04
Edited May 18, 2020 by Laurent Petre
Assignee
Assign to
Time tracking