# Minimum hybrid time

For benchmarking purposes we would like to investigate how much the quality of the solution of the hybrid solver improves given it is given more time to work on the problem. We want to do this by running random generated problem instances for different time limits.

The problem that we face is that the minimum_time_limit, specified here https://docs.dwavesys.com/docs/latest/c_solver_properties.html#minimum-time-limit results already yields the optimal solution to our problems.

Is there a way to set the hybrid_solver.properties['minimum_time_limit'] by hand, so that we can better study the output of the hybrid solver when it has to little time to produce good results? Or alternatively, what would be even better, is to be able to inspect current best solution over time. Although I don't think that is possible

## Comments

David J(Report)Hello,

Unfortunately it is not possible to change the

minimum_time_limit, as this is the minimum amount of time needed to run a given problem on a Hybrid Solver.There also isn't a way to check the current best solution over time.

Victoria G(Report)Hi Robert!

For your research you might consider using the open-source package dwave-hybrid. This package is a framework for building hybrid algorithms, and comes with some initial building blocks to get you started.

You can learn more about the package in our documentation (https://docs.ocean.dwavesys.com/en/stable/docs_hybrid/sdk_index.html) or through our collection of Jupyter notebooks (https://github.com/dwave-examples/hybrid-computing-notebook). These open-source tools allow you to use all of the QPU parameters in your subproblem sampling step (including anneal time, num reads, etc) as well as the timing for the classical components, and so you can manually control exactly how long your algorithm runs for.

Please sign in to leave a comment.