-
Notifications
You must be signed in to change notification settings - Fork 10
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
TSPTW as a great benchmark tool. #24
Comments
It would definitely be great to do that, but I'm not sure we have time for this. |
If it is great, we should find the time ! ;) |
We are going to try that. Here would be the list of the things we need to develop:
Eventually :
|
Merged
Merged
This was referenced Jul 30, 2020
Merged
This was referenced Aug 3, 2020
Merged
Merged
We could consider it done imo :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It would be great to make it possible to work on the TSPTW as it is one of the problem used by Quentin in his paper.
In addition, even it could be a little time consuming, I think it could be very interesting to try to reproduce his experiment with our solver. Not a perfect reproduction as we are learning inside the solver, but using the same Graph representation as him.
Even if this won't be inside the "unified representation goal" we are trying to achieve, I would see it as a "sanity check", to make sure our performance are good and to prove that learning in the solver is a real breakthrough.
To do it, we should:
PS: the comparison with Quentin can also be done with knapsack or portfolio but in the end, I think we should have the tsptw in our examples
The text was updated successfully, but these errors were encountered: