Bug #24176
Run number on RC GUI flowchart tracks latest absolute run number, not the run number associated with its particular instance
Start date:
03/12/2020
Due date:
% Done:
0%
Estimated time:
Occurs In:
Co-Assignees:
Description
We had a run going (1350) on icarus-evb01 machine using the RC GUI when we brought up a separate run (1351) on icarus-pmt01 in order to verify that we can run separately the TPC and PMT subsystems. Fortunately we were able to get both runs going simultaneously, but it seems that the run number on the icarus-evb01 instance changed from 1350 to 1351. It is maybe worth noting that the data taken by the instance running on icarus-pmt02 is being saved to icarus-evb02.
It would be useful to have the RC GUI track the run it's responsible for, rather than the latest run.