BNMR: Run numbering: Difference between revisions

From DaqWiki
Jump to navigation Jump to search
en>Suz
mNo edit summary
No edit summary
 
(11 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{Pagelinks}}
{{Pagelinks}}
<div style="column-count:3;-moz-column-count:3;-webkit-column-count:3">
 
* [[BNMR]]
* [[BNMR: Midas Host#Environment Variables|Environment variables]]
* [[BNMR: Experimental Modes|Experimental Modes]]
* [[BNMR: Getting Started|Getting Started]]
* [[BNMR#Nomenclature|Nomenclature]]
</div>
== Introduction ==
== Introduction ==
{{bnmqr|join=and}} experiments use the MUSR run number scheme, whereby "Real" runs are assigned a run number in a certain [[#Run Number Ranges|range]] depending on the beamline. All "Test" runs have a run number selected from the test run number [[#Run Number Ranges|range]] (independent of beamline).  
{{bnmqr|join=and}} experiments use the MUSR run number scheme, whereby runs are designated as "'''Real'''" or "'''Test'''" according to their run number. Data is always logged (saved to disk). '''Real''' runs are assigned a run number in a certain [[#Run Number Ranges|range]] depending on the beamline. All "'''Test'''" runs have a run number selected from the test run number [[#Run Number Ranges|range]] (independent of beamline).
[[#Automatic selection of the run number]] (the default) must be enabled for the {{bnmqr|join=and}} experiments.


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: 40000 - 44499 inclusive
* BNQR: 45000 - 49999 inclusive
* Test: 30000 - 30499 inclusive


== Run Number Ranges ==
The minimum run numbers for a given experiment is defined in the ODB at {{Odbpath|path=/RealOrTest/Base real}} and {{Odbpath|path=/RealOrTest/Base test}}.
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 ==
== User selects test or real run ==
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]].
Prior to starting a run, the user can switch the run type on the [[BNMR: Custom Status page|status page]] or [[BNMR: Custom Settings page|settings page]] to choosing either <code>Test data</code> or <code>Real data</code> from a <code>select</code> element. The <code>select</code> box is connected to the [[BNMR:_Mode_changer#Changing_between_real_and_test_runs|mode changer]] via JRPC, which handles changing the run number appropriately.
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]].


== Prevent User from editing run number ==
== User prevented 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  
By default, the MIDAS system allows the user to edit the run number at the begin-of-run. MIDAS provides a way of  
[https://midas.triumf.ca/MidasWiki/index.php/Edit-on-start_Parameters#Prevent_the_run_number_being_edited_at_Run_Start preventing editing of the run number].
[https://midas.triumf.ca/MidasWiki/index.php/Edit-on-start_Parameters#Prevent_the_run_number_being_edited_at_Run_Start preventing editing of the run number].
Line 31: Line 24:
  Edit run number                n
  Edit run number                n


== Choosing the next run number ==
The [[BNMR:_Mode_changer|mode changer]] determines the next valid run number by examining the files in the
[[BNMR: Data Logging#Saved data files|saved file directory]]. It finds the file with the highest run number, limiting itself to only real/test run numbers as appropriate. It then sets the run number to one more than that.


This system is simple and robust, avoids gaps in the run numbering, and allows for an easily implementation of changing between real/test runs while a run is already in progress. All these features are highly desired by users.
The mode changer runs these checks at the start of each run and whenever the user changes between real/test modes.


[[Category: Run Numbering]]
[[Category:BNMR]] [[Category: Run Numbering]]

Latest revision as of 13:07, 28 April 2022

Introduction

bnmr and bnqr experiments use the MUSR run number scheme, whereby runs are designated as "Real" or "Test" according to their run number. Data is always logged (saved to disk). 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). #Automatic selection of the run number (the default) must be enabled for the bnmr and bnqr experiments.

Run number ranges

The following run number ranges have been assigned:

  • BNMR: 40000 - 44499 inclusive
  • BNQR: 45000 - 49999 inclusive
  • Test: 30000 - 30499 inclusive

The minimum run numbers for a given experiment is defined in the ODB at /RealOrTest/Base real and /RealOrTest/Base test.

User selects test or real run

Prior to starting a run, the user can switch the run type on the status page or settings page to choosing either Test data or Real data from a select element. The select box is connected to the mode changer via JRPC, which handles changing the run number appropriately.

User prevented 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

Choosing the next run number

The mode changer determines the next valid run number by examining the files in the saved file directory. It finds the file with the highest run number, limiting itself to only real/test run numbers as appropriate. It then sets the run number to one more than that.

This system is simple and robust, avoids gaps in the run numbering, and allows for an easily implementation of changing between real/test runs while a run is already in progress. All these features are highly desired by users.

The mode changer runs these checks at the start of each run and whenever the user changes between real/test modes.