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

Address how the model is dealing with floating point imprecision #2

Open
mkote opened this issue Jul 2, 2024 · 0 comments
Open

Address how the model is dealing with floating point imprecision #2

mkote opened this issue Jul 2, 2024 · 0 comments

Comments

@mkote
Copy link

mkote commented Jul 2, 2024

The current model is implemented using the double datatype for arithmetic operations. However, this means that it is affected by the inherent imprecision of floating point arithmetic operations. In other words, the series of summations and multiplications will likely yield an imprecise final rating. This could be a potential problem for teams with very close ratings. Further, since this model is used to calculate the official valve rankings, it becomes hard to port the code to other languages, since floating point imprecision is not consistent across programming languages.

What are your thoughts on this?

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