Skip to content

MNT: assess if value user checks should happen for all daq operations #208

@tangkong

Description

@tangkong

Raised during review of #203

          the check is only in restartdaq as people who start the DAQ may modify the configuration database and we wanted to make sure that some beamline scientists umask did not make the DAQ unusable for the next person on shift. This is not a problem for the new daq as far as I can see.

We should think about where we need these checks, but to roll this our before SC beam this may need to end up as a item for future review (like argpase versus getopt)

Originally posted by @silkenelson in #203 (comment)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions