Skip to content
GitLab
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 95
    • Issues 95
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 15
    • Merge requests 15
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • cmsgemonline
  • gem-daq
  • cmsgemos
  • Merge requests
  • !296

Implement automatic DAQ power on

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged Laurent Petre requested to merge feature/automatic-power-on into main Oct 26, 2022
  • Overview 0
  • Commits 5
  • Pipelines 1
  • Changes 9

Description

This MR aims at adding a new feature to automatically power the front-end LV via DIM commands to the DCS. When the feature is enabled, all OptoHyrbids known in the layout tree are sent an ON DIM command at configuration.

Note that, in order to maintain a minimal configuration time, the simultaneous DIM commands have been re-enabled (after careful synthetic tests) and the power-on sequence is performed in the background of the back-end board recovery.

A few additional bug fixes related to the build system, CI, and example recovery procedure are included.

Related Issue

How Has This Been Tested?

Deployed in production in CMS and working like a charm. No crashes due to the simultaneous DIM commands are observed.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.
Edited Nov 01, 2022 by Laurent Petre
Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: feature/automatic-power-on