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

Call cons! in objcons! for unconstrained #463

Merged
merged 1 commit into from
May 24, 2024
Merged

Call cons! in objcons! for unconstrained #463

merged 1 commit into from
May 24, 2024

Conversation

tmigot
Copy link
Member

@tmigot tmigot commented May 24, 2024

This unifies the behavior with objcons. Otherwise, we have the strange behavior of having neval_cons(nlp) = 0 after calling objcons!.

This unifies the behavior with `objcons`
Copy link
Contributor

Package name latest stable
ADNLPModels.jl
AmplNLReader.jl
CUTEst.jl
CaNNOLeS.jl
DCISolver.jl
FletcherPenaltySolver.jl
JSOSolvers.jl
LLSModels.jl
NLPModelsIpopt.jl
NLPModelsJuMP.jl
NLPModelsModifiers.jl
NLPModelsTest.jl
PDENLPModels.jl
Percival.jl
QuadraticModels.jl
SolverBenchmark.jl
SolverCore.jl
SolverTest.jl
SolverTools.jl

@tmigot tmigot merged commit cca1290 into main May 24, 2024
54 checks passed
@tmigot tmigot deleted the unifiy-objcons branch May 24, 2024 21:30
@dpo
Copy link
Member

dpo commented May 31, 2024

This seems completely illogical to me. Of course I expect neval_cons = 0 on an unconstrained problem. An algorithm for unconstrained optimization that attempts to evaluate the constraints has a serious existential problem.

@tmigot
Copy link
Member Author

tmigot commented Jun 1, 2024

This was unifying the behavior of the API, I make a new issue to discuss this.

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 this pull request may close these issues.

2 participants