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.

Sign up for GitHub

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

Jump to bottom

Do not always solve child nodes to optimality #8

Open
hlefebvr opened this issue Oct 25, 2023 · 0 comments
Open

Do not always solve child nodes to optimality #8

hlefebvr opened this issue Oct 25, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@hlefebvr
Copy link
Owner

hlefebvr commented Oct 25, 2023 •
edited
Loading

Is your feature request related to a problem? Please describe.
Currently, all nodes are solved to optimality when they are created. Yet, this is not necessary for correctness. We only need to solve the node optimally if it is selected for branching.

Describe the solution you'd like
Nodes should be solved partially according to some criterion (?) and solved only when needed.

Describe alternatives you've considered
.

Additional context
.
@hlefebvr hlefebvr added the enhancement New feature or request label Oct 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@hlefebvr