A stop and restart mechanism for linear codes benchmarking tool

[1861b8a9-77f0-4f35-8431-8514a75b40d1]

This ticket adds a new feature to the benchmarking tool introduced in #20526 which allows the user to interrupt an run (with Ctrl+C) and resume it afterwards by typing Benchmark.run() again. It will resume the run at the exact place it was stopped before. If triggered in verbose mode, the current progress status will be kept (e.g. if stopped at 25%, the first message of the new run in verbose mode will be 25% complete).

Depends on #20526

CC: @johanrosenkilde @ClementPernet

Component: coding theory

Author: David Lucas

Branch/Commit: u/dlucas/stop_and_restart_feature_for_benchmarking @ 20523d0

Issue created by migration from https://trac.sagemath.org/ticket/20684

[1861b8a9-77f0-4f35-8431-8514a75b40d1]

Branch: u/dlucas/stop_and_restart_feature_for_benchmarking

[1861b8a9-77f0-4f35-8431-8514a75b40d1]

comment:2

I pushed the patch, which is now open for review.

David

---

Last 10 new commits:

0dfdbf0	Replaced exception by a return statement in run() on empty benchmarks
7212b33	Added a distinction between decoding_error and decoding_failure, refined decoding_success_rate accordingly
bc29f26	Refined experimental_data method, which now allows request for specific data
a82a477	Fixed syntax errors in documentation
0ab93ec	Changes and fixes to docstrings and doctests
d2d6e26	Improved data selection in experimental_data method
8e363dd	Switched definition of decoding error and decoding failure
fe0b956	Merge branch 't/20601/20601_experimental' into benchmarking_tool
272d251	Update to 7.3b1
20523d0	Added a stop and start mechanism for benchmarks

[1861b8a9-77f0-4f35-8431-8514a75b40d1]

Commit: 20523d0

[fchapoton]

comment:3

You must fill the author Field if you want patchbots to have a look. I did it for you, please check.

[fchapoton]

Author: David Lucas

[johanrosenkilde]

comment:4

This will probably be superseded by the BleacherMark project.