Skip to content
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

Feature: start values for optimization problem #32

Open
stelmo opened this issue Apr 28, 2024 · 5 comments · May be fixed by #72
Open

Feature: start values for optimization problem #32

stelmo opened this issue Apr 28, 2024 · 5 comments · May be fixed by #72

Comments

@stelmo
Copy link
Member

stelmo commented Apr 28, 2024

Sometimes it would be nice to help the solver by supplying the first guess manually

@exaexa
Copy link
Member

exaexa commented Apr 28, 2024

what's the underlying JuMP API?

@exaexa
Copy link
Member

exaexa commented Apr 28, 2024

(btw again this might be better directly in CTs)

@stelmo
Copy link
Member Author

stelmo commented Apr 28, 2024

In JuMP you just do something like set_start_value(variable_ref, number). See here: https://jump.dev/JuMP.jl/stable/manual/variables/#Start-values. Yep, might be better in CTs to be more general

@exaexa
Copy link
Member

exaexa commented Sep 19, 2024

edit here: not in CTs, CTs don't know anything about jump :D

exaexa added a commit that referenced this issue Sep 20, 2024
@exaexa
Copy link
Member

exaexa commented Sep 20, 2024

@stelmo btw is there a good usecase for this? So that I can write a test or so.

@exaexa exaexa linked a pull request Sep 20, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants