Skip to content

Conversation

HaoZeke
Copy link
Contributor

@HaoZeke HaoZeke commented Oct 22, 2023

Do not attempt to review until #19255 is in. :)

Reference issue

Closes #15707 eventually.

What does this implement/fix?

Basically passes callback information in the same way as the rest of linprog.

Additional information

Draft until its ready. Might need more changes here as well. Depends on #19255.

HaoZeke and others added 30 commits October 14, 2023 12:49
Still needs a wrapper around Highs()
Co-authored-by: mckib2 <mckib2@users.noreply.github.com>
With fixes as suggested

Co-authored-by: rgommers <rgommers@users.noreply.github.com>
Co-authored-by: rgommers <rgommers@users.noreply.github.com>
... outside of scipy at any rate
Remain 100% backwards compatible
@lucascolley lucascolley added enhancement A new feature or improvement scipy.optimize labels Dec 21, 2023
@lucascolley lucascolley added this to the 1.14.0 milestone Mar 12, 2024
@lucascolley lucascolley changed the title ENH: Use callbacks for highs in linprog ENH: optimize.linprog: use callbacks for highs May 18, 2024
@h-vetinari
Copy link
Member

@HaoZeke, any update here? It's probably getting a bit tight to get this into 1.14...

@rgommers rgommers modified the milestones: 1.14.0, 1.15.0 May 27, 2024
@HaoZeke
Copy link
Contributor Author

HaoZeke commented May 28, 2024

@HaoZeke, any update here? It's probably getting a bit tight to get this into 1.14...

Thanks for the ping, @h-vetinari. Also, I'm sorry, but this needs some work since the underlying PR got reverted (and is being reworked a bit upstream). I'll be ready with the previous (highs update PR) this weekend but I see from the release schedule (and the fact that reviews will be needed) that none of these will be in before rc2 at the earliest.

@lucascolley
Copy link
Member

I assume this won't be making it in this week... feel free to prove me wrong!

@lucascolley lucascolley modified the milestones: 1.15.0, 1.16.0 Nov 30, 2024
@h-vetinari
Copy link
Member

@HaoZeke, are you still planning to update this PR? :)

@HaoZeke
Copy link
Contributor Author

HaoZeke commented Dec 28, 2024

@HaoZeke, are you still planning to update this PR? :)

Probably not in the near future, I've a bit of personal work coming up and am traveling as well. I'd revise the ETA on this to be at least a couple of months. I'm also happy for anyone else to take over, it should be straightforward exposing the actual callbacks to highs, but since they now run at different times than the older variant there needs to be a lot of documentation for scipy users.

@tylerjereddy
Copy link
Contributor

@HaoZeke I'm guessing this will probably not make it into the 1.16.0 release, which we're planning to branch for "soon" (may be delayed beyond the weekend, but probably not much beyond that)

@tylerjereddy tylerjereddy modified the milestones: 1.16.0, 1.17.0 May 14, 2025
@HaoZeke
Copy link
Contributor Author

HaoZeke commented May 19, 2025

Sorry, but this is a bit on the backburner for me at the moment, moving to a new position. I will try to get back in time for the next release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement A new feature or improvement scipy.optimize
Projects
None yet
Development

Successfully merging this pull request may close these issues.

DEP: remove deprecated linprog-methods
5 participants