Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • 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 81
    • Issues 81
    • 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
  • #169

Closed
Open
Created Mar 24, 2021 by Laurent Petre@lpetreOwner

How to store the non-tracking data scans and/or the local readout data?

Summary

At the moment, there is no facility to store the output from the different xDAQ applications. This is starting to be an issue with the implementation of the non-tracking data scans. It will be even more the case with the implementation of the local readout.

A notable specificity is that the output files will be split following the xDAQ applications (i.e. one application per back-end board). This could be prevented with a centralized application gathering the data from all applications.

The first possibility that comes to my mind is to create a directory per xDAQ application per run (request the run the the RunInfo database like the CSC?). Any function could drop its files in the previously mentioned directory.

What is the expected correct behavior?

Where and how to store the information is clearly defined. A generic implementation is provided.

Assignee
Assign to
Time tracking