BNMR: Run numbering: Difference between revisions
en>Suz mNo edit summary |
en>Suz mNo edit summary |
||
| Line 20: | Line 20: | ||
== Automatic selection of the run number == | == Automatic selection of the run number == | ||
The selection of the next run number is done automatically, controlled by the perlscript [[BNMR: Perlscripts#get_next_run_number.pl|get_next_run_number.pl]]. | The selection of the next run number is done automatically, controlled by the perlscript [[BNMR: Perlscripts#get_next_run_number.pl|get_next_run_number.pl]]. | ||
This script is called by [[BNMR: mdarc|mdarc]] which saves the data, and indirectly by the test and real buttons on the [[BNMR: Custom Status page]]. | |||
Without the automatic checking, duplicate runs between I-MUSR and TD-MUSR and holes in the run numbering are inevitable. To preserve the automatic run numbering scheme, | Without the automatic checking, duplicate runs between I-MUSR and TD-MUSR and holes in the run numbering are inevitable. To preserve the automatic run numbering scheme, | ||
users are prevented from [[#Prevent User from editing run number|editing the run number]]. | users are prevented from [[#Prevent User from editing run number|editing the run number]]. | ||
Revision as of 16:57, 29 August 2016
Introduction
bnmr and bnqr experiments use the MUSR run number scheme, whereby "Real" runs are assigned a run number in a certain range depending on the beamline. All "Test" runs have a run number selected from the test run number range (independent of beamline).
This means that the selection of the next run number is controlled by software (see #Automatic selection of the run number).
Run Number Ranges
The following run number ranges have been assigned:
- BNMR
- 40001 - 44499 inclusive
- BNQR
- 45001 - 49999 inclusive
- test
- 30001 - 30499 inclusive
Automatic selection of the run number
The selection of the next run number is done automatically, controlled by the perlscript get_next_run_number.pl. This script is called by mdarc which saves the data, and indirectly by the test and real buttons on the BNMR: Custom Status page.
Without the automatic checking, duplicate runs between I-MUSR and TD-MUSR and holes in the run numbering are inevitable. To preserve the automatic run numbering scheme, users are prevented from editing the run number.
Prevent User from editing run number
By default, the MIDAS system allows the user to edit the run number at the begin-of-run. MIDAS provides a way of preventing editing of the run number. This is implemented in the ODB of both the bnmr and bnqr experiments, e.g.
[local:bnqr:Stopped]/>ls "/experiment/Edit on start/Edit run number" Edit run number n