Lock when running

From MidasWiki
Revision as of 14:21, 21 August 2013 by Suz (talk | contribs) (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. ...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

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 Lock when Running in the /Experiment ODB tree.

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