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

False early exits #212

Open
Zannick opened this issue Sep 2, 2024 · 0 comments
Open

False early exits #212

Zannick opened this issue Sep 2, 2024 · 0 comments

Comments

@Zannick
Copy link
Owner

Zannick commented Sep 2, 2024

For instance, with AV2 if I provide no routes as input, the search finishes "after 775 rounds (0 dead-ends), skipped 8+1202 pushes + 0+26 pops", meaning 8 states were over the time limit (set as an unreasonable upper bound and very likely meaning the estimate did not find a valid path), and 1202+26 were duplicates.

It would be nice to have some output to debug from, such as a "best" state that was the farthest reached, or a set of spots reached, etc.

Separately, we could maybe ignore the limit if the estimate is the special value and we have no solutions yet.

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

No branches or pull requests

1 participant