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

Ordering issue in VRPLIB files #118

Closed
N-Wouda opened this issue Mar 16, 2024 · 0 comments · Fixed by #121
Closed

Ordering issue in VRPLIB files #118

N-Wouda opened this issue Mar 16, 2024 · 0 comments · Fixed by #121

Comments

@N-Wouda
Copy link
Member

N-Wouda commented Mar 16, 2024

This:

EDGE_WEIGHT_SECTION
0     1544  1944  1931  1476
1726     0  1992  1427  1593
1965  1975     0  621   1090
2063  1433   647  0     818
1475  1594  1090  828   0
EDGE_WEIGHT_TYPE : EXPLICIT
EDGE_WEIGHT_FORMAT : FULL_MATRIX

has some of the specifications after the edge weight data. This does not currently work, because VRPLIB parses the EDGE_WEIGHT_SECTION the moment it encounters it and assumes all relevant specifications are known by that time. Clearly, here, they are not, and that causes an error. I don't think it should, but if it should, we should definitely clarify that we explicitly assume the specifications come first in the data file.

I ran into this when I was rewriting the GVRP instances yesterday.

@leonlan leonlan linked a pull request Jun 24, 2024 that will close this issue
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 a pull request may close this issue.

1 participant