-
Notifications
You must be signed in to change notification settings - Fork 74
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
Edge weight integer #14
Comments
I'm not sure why this is, but you could use an integer representation of your decimal to get around it. If your decimal weight is 1.05 you could use 105 as the weight, or 1050 if you want another decimal place of precision, etc. |
I made the following modifications and it seems to work: georgewhewell@548f314 ymmv |
Thanks a lot @georgewhewell 😄 Might be worth creating a pull request. |
Addressed in #19 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
I want to do path finding between multiple vertexes. I'm adding edges but my current weight values are decimal. The library returns the following message:
I understand that integers are faster and don't have rounding errors. What is the reason that weights must be an integer?
ps: thanks for the lib :-)
The text was updated successfully, but these errors were encountered: