EMU: DAE/Run Control/Periods: Count rate of 0 whilst running is confusing

[KathrynBaker]

Issue Description

As a person using EMU to take data I am confused when the system says running and the count rate is 0.0, I would like things to be clearer so that I don't have running time with a 0 count rate.

How & Where?

Seen on EMU, the system was running, but it looks like a run control value was out of range, at least somewhat, and it may have been during the transition from in/out of range that triggered this situation, but it did lead to a count rate of 0.0 whilst running.
User did mention appearance of waiting and then the count rate not recovering. Disabling the run control solved the issue.
Note that this situation seemed to be resolved by taking off the run control, but something in the timing of events, what the UI was showing and what occurred when seems to be incorrect.

Reproducible (Yes/No)?

Untried, but to either verify the situation or deny it, I'd set up a DAE for simulated Muons using periods if possible, set up some run control on a block in simple, and set things to changing quickly in that block and see if I can reproduce it that way.

Additional Information

When this came through as a support call I did recommend asking the data acquisition team as issues with run count like this can be mathematical on their end, however this seems to relate to use of periods as well, so there may be a rare combination of things occurring, leading to an odd race condition.

Acceptance Criteria

• A timebox is set to attempt tp reproduce the error, if in that time the error is reproduced, start a new timebox to locate and resolve the error
• If the error is resolved all is well, if it is not resolved ensure that there is an appropriate comment in the troubleshooting areas of the developers manual that will give this as a scenario to check for.

How to Review

_{Before making a PR...}

• Provide verbose instructions for the reviewer to test that your changes work and fix the issue
• Describe if/how you have implemented testing for this issue
• Provide screenshots of the feature to help the reviewer if relevant

_{If not applicable, write "Not applicable"}

...

_{To the reviewer: Make sure to update submodules!}

[KathrynBaker]

DSG has been contacted, awaiting reponse from correct person to see if this is solvable, it may be a "feature" of run control and periods that will need considering.
Looks to be hardware side, and nothing that we can do directly, so will close this ticket as we have work arounds.