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

Strange and unreliable feedback when target min == max #28

Closed
helgoboss opened this issue Sep 9, 2020 · 0 comments
Closed

Strange and unreliable feedback when target min == max #28

helgoboss opened this issue Sep 9, 2020 · 0 comments
Labels
bug Something isn't working
Milestone

Comments

@helgoboss
Copy link
Owner

helgoboss commented Sep 9, 2020

Strange because of strange normalization behavior if value == target min == target max (it returned min in that case, but it would make more sense to return 1.0).

Unreliable because of numerical inaccuracies when querying actual parameter FX values (they can deviate from the requested value, e.g. you request 0.2 and get 0.19999999423128). Usually that's not an issue but if target min == target max we have don't have a range of values anymore but just one particular value - and then it's an issue for getting the right feedback value.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant