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.
I've made one change in two files:
pathfinding-subnodes.lppathfinding-functions.lpA brief history
I tried testing these encodings on the benchmark environments and was surprised when they didn't work, since the encodings look fine and also work on the example environment.
I made the edits shown above and still was not able to get a satisfiable solution.
I tested it on
envs/lp/test.lpwithh=25and it did not work but then withh=40it did work.I returned to
benchmarks/environments/Test_00/Level_3.lpand made a temporary modification to comment out all but the first train. Withh=200it was unsatisfiable. I counted exactly how many steps would be needed (26) and seth=26and got a solution. A solution existed also forh=27andh=28, but not forh=25(unsurprisingly). Solutions still existed ath=50andh=100but not ath=200.I restored
benchmarks/environments/Test_00/Level_3.lpto have all seven trains and tried different values forh. 60, 70, and 90 failed, buth=100produced a result. Without the changes above, the result is unsatisfiable.