mirror of https://github.com/m-labs/artiq.git
7955b63b00
Previously, a significant risk of losing experimental results would be associated with long-running experiments, as any stray exceptions while run()ing the experiment – for instance, due to infrequent network glitches or hardware reliability issue – would cause no HDF5 file to be written. This was especially troublesome as long experiments would suffer from a higher probability of unanticipated failures, while at the same time being more costly to re-take in terms of wall-clock time. Unanticipated uncaught exceptions like that were enough of an issue that several Oxford codebases had come up with their own half-baked mitigation strategies, from swallowing all exceptions in run() by convention, to always broadcasting all results to uniquely named datasets such that the partial results could be recovered and written to HDF5 by manually run recovery experiments. This commit addresses the problem at its source, changing the worker behaviour such that an HDF5 file is always written as soon as run() starts. |
||
|---|---|---|
| .. | ||
| applets | ||
| browser | ||
| compiler | ||
| coredevice | ||
| dashboard | ||
| examples | ||
| firmware | ||
| frontend | ||
| gateware | ||
| gui | ||
| language | ||
| master | ||
| sim | ||
| test | ||
| wavesynth | ||
| __init__.py | ||
| _version.py | ||
| appdirs.py | ||
| build_soc.py | ||
| experiment.py | ||
| remoting.py | ||
| tools.py | ||