Add routing improvement limits - #85
Open
erickreutz wants to merge 1 commit into
Open
Conversation
Expose native improvement-rate stopping through routing search parameters. Keep the interface independent from solution tracing and preserve existing behavior unless configured.
erickreutz
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
OR-Tools exposes native improvement-rate stopping through
RoutingSearchParameters::improvement_limit_parameters, but the nested parameters are not available in Ruby. This adds a Ruby hash getter and setter for the coefficient and solution-distance fields.The interface mirrors the native parameter names and remains independent from solution tracing. Existing routing search behavior is unchanged unless the parameters are set.