-
Notifications
You must be signed in to change notification settings - Fork 205
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mip_improving_solution_save not saving on each improvement #1857
Comments
How agonizing! I'll copy this to #1856 |
Just an FYI, this isn't via Highspy, this is via Pulp using HiGHS_CMD which writes out the LP and then calls the HiGHS executable. I admit I haven't tested calling the executable via the command line with an options file to test it yet. But I guess if something wonky might be going on that would tell me. I'll test it out tomorrow and let you know. edit: I have used Pulp with Highspy a few times using the source repo build but for some reason, that I don't quite recall, I preferred calling with the HiGHS_CMD. |
Well, color me embarrassed. 😊 I went to test out the improved file writing from the terminal and noted the same issue but then noticed that the file timestamp updated... it is appending, so when I looked at the objective in the first line it looked like it didn't update. Grepping the file showed all of the improved solutions. Grepping the improved solution file being used via Pulp -> HiGHS_CMD shows it is updating (appending). Mark it up to ignorance. |
Hello!
Consider the following options being passed to HiGHS:
I can see that they are being accepted because a
highs_improved_solution
file was created and saved the first of the improved solutions.That was ~6.5hrs ago. Since then over a dozen improvements have taken place yet none of them got saved. Much to my dismay because I just hit ctrl-c to copy something but my focus was on my terminal 🤦♂️ The real sad part was that I had realized this was taking place and the ctrl-c I used was to copy the options pasted above for this ticket. Anyhow, after getting down to a gap of 1.72% and 75.01% explored in those 6.5hrs I really would like to have seen the last incumbent.
The text was updated successfully, but these errors were encountered: