Optimizer's timeout

[bqth29]

PR Description

A timeout option has been added to the optimizer so the simulated bifurcation algorithm can be stopped after a pre-defined time threshold. The optimizer has now 3 different stopping criteria that can be combined or used individually.

New features

• The parameter timeout is available in the optimize, minimize and maximize methods. It represents the number of seconds after which the computation will stop. Set to None, no timeout will be used.
• A progress bar for the computation time can be displayed in the terminal is a timeout is set and if the verbose is set to True
• The progress bars of the optimizer have been improved graphically
• The max_steps parameter can be set to None to indicate that the simulation stopping should not be triggered by a maximum number of iterations in the optimizer
• A check is conducted to ensure at least one stopping criterion is set (among the timeout, the maximum number of steps and the stop-window)

Bug fixes

• A useless spin sampling in the optimizer iterations has been removed resulting in a computation speed up

[codecov[bot]]

Codecov Report

All modified lines are covered by tests :white_check_mark:

Files	Coverage Δ
src/simulated_bifurcation/ising_core.py	100.00% <100.00%> (ø)
...ation/optimizer/simulated_bifurcation_optimizer.py	100.00% <100.00%> (ø)
src/simulated_bifurcation/optimizer/stop_window.py	100.00% <ø> (ø)
...furcation/polynomial/ising_polynomial_interface.py	100.00% <ø> (ø)
src/simulated_bifurcation/simulated_bifurcation.py	100.00% <100.00%> (ø)
tests/test_optimizer.py	100.00% <100.00%> (ø)

:loudspeaker: Thoughts on this report? Let us know!.