MIP Worker Refactor

[Opt-Mucca]

No description provided.

[jajhall]

No, this is due to someone running a second Highs instance with threads set to a different value

[Opt-Mucca]

@fwesselm I've updated the branch so the interrupt callback is not flagged when parallelLockActive, and I've made most of HighsMipWorker private (a point you raised in an earlier comment).
I believe this is on track to be merged next week (after I change mip_search_concurrency=0 to default)

[Opt-Mucca]

@jajhall I am getting an error from an assert in the timers when running https://miplib.zib.de/instance_details_lectsched-4-obj.html with mip_search_concurrency=2. Could you look into this? (I will also try and see if I can debug it)

HiGHS/highs/lp_data/HighsInterface.cpp:4346: void HighsSubSolverCallTime::start(HighsInt): Assertion `this->submip_clock_running[thread] < 0' failed.
Signal: SIGABRT (Aborted)

Edit: Would also need threads=8

[jajhall]

@jajhall I am getting an error from an assert in the timers when running https://miplib.zib.de/instance_details_lectsched-4-obj.html with mip_search_concurrency=2. Could you look into this? (I will also try and see if I can debug it)

HiGHS/highs/lp_data/HighsInterface.cpp:4346: void HighsSubSolverCallTime::start(HighsInt): Assertion `this->submip_clock_running[thread] < 0' failed.
Signal: SIGABRT (Aborted)

Edit: Would also need threads=8

The sub-solver profiling has developed since, so I'll try merging my most recent work to see what happens