Broser freezing when number of shots is larger than expected

[FlorenceBerterottiere]

If I have recrystallisations (variable numbers of shots) I run into the issue that it is playing the sequence fine, but it cannot display the data live (and the whole browser seems very slow/mostly frozen)

This is on branch fix/recrystallization, could be that my fixes introduced other bugs... to be investigated :)

[aferk]

Some more explanation:
The hardware supports "transitory errors", where individual shots can be re-taken without discarding the datapoint.
Depending on the usercode, the hardware will provide shot_channels with more or less data than the requested number of shots. Generally, it would be good to allow the number of data points per shot channel to be flexible, the user can also decide to feed more data into one channel.

For "transitory errors", this means there would be two (or more) shot channels;

• "good shots" : Data which should be used for the datapoint (i.e. requested n_shots long)
• "bad shots" : Data which should not be used for the datapoint (length undefined)

In case the hardware re-tries shots too often, it will return with an error (timeout).

[aferk]

An HDF file with the correct data would be helpful to reproduce this issue.

[FlorenceBerterottiere]

I tried to find one, but somehow the hdf5 file is just completely empty when I have recrystallisations on!