Creating multiple top level runners with for loop and using a single applet leads to value error

[dougalmain1]

The code runs a 2D Ramsey scan for multiple transitions. For each transition, a new instance of TopLevelRunner is called. The applet does not seem to be being reset and we get the following message.

The experiment does not stop upon receiving this message and it appears that apart from the applet not displaying correctly, the code runs fine.

[dougalmain1]

The issue with the applet display only appears to happen when the scan axes have different ranges.

[dnadlinger]

@dougalmain24: Do you have a test case to reproduce this? It's fine if it's an internal one, but this would be much easier to debug with a concrete starting point.

[dougalmain24]

Ah yes, I believe this was the coherence time measurements (hoa2_common.measurements.coherence_times) which we run in nightly, where we have a set of 2d phase/duration scans. The first scan runs normally, the applet looks fine (see below).

However, when we run the next scan, which then uses a different duration axis, the applet does not display the data correctly in that the applet seems to use the same duration axis as the first scan (see below)? And we often get points overwriting others (in the applet only, the data and thus the subsequent fitting etc.. itself is fine).

[dougalmain24]

This was a while ago, but I believe this was what the issue was created for. It may well have been user error where I did not use the top level runner correctly.

[dnadlinger]

This is probably related to #387.