Lock when running: Difference between revisions

From MidasWiki
Jump to navigation Jump to search
(Created page with "Often it is desirable that various experimental ODB parameters should not to be changed when a run is in progress, i.e. that they are set to a "read-only" mode while running. ...")
 
(The midas documentation has moved to https://midas.triumf.ca/docs/)
 
Line 1: Line 1:
Often it is desirable that various experimental ODB parameters should not to be changed when a run is in progress, i.e. that they are set to a "read-only" mode while running. This can be done by creating logical links to these ODB keys in the optional subtree <span style="color: purple;">''Lock when Running''</span> in the [[/Experiment ODB tree]].
The midas documentation has moved. See [https://midas.triumf.ca/docs/develop/features/core_system/odb/configuring/#lock-when-running Lock when running] on the ODB: configuring page for the new documentation about locking ODB keys while a run is in progress.
 
In the [[odbedit]] example below, all the parameters under the declared subtree will be switched to read-only, thus preventing any modification of these parameters during the run.
 
  [local]/>create key "/Experiment/Lock when running"
  [local]/>cd "/Experiment/Lock when running"
  [local]/>ln "/Experiment/Run parameters" "Run parameter"
  [local]/>ln "/Logger/Write Data" "Write Data?"
 
In the following example, the user attempts to change one of the read-only parameters:
 
[local:bnmr:R]/>set "/Logger/Write Data" y
Write access not allowed

Latest revision as of 22:00, 30 October 2026

The midas documentation has moved. See Lock when running on the ODB: configuring page for the new documentation about locking ODB keys while a run is in progress.

Retrieved from "https://daq00.triumf.ca/MidasWiki/index.php?title=Lock_when_running&oldid=3740"