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

Boundary problem in range node #1337

Closed
kazuhitoyokoi opened this issue Jul 11, 2017 · 0 comments · Fixed by #1338
Closed

Boundary problem in range node #1337

kazuhitoyokoi opened this issue Jul 11, 2017 · 0 comments · Fixed by #1338

Comments

@kazuhitoyokoi
Copy link
Member

kazuhitoyokoi commented Jul 11, 2017

Current range node doesn't use same conditions for all boundary values. I think that the following conditions should be applied for all boundary values.

  • Minimum boundary condition: Minimum value and more than minimum value
  • Maximum boundary condition: Less than maximum value

But in some cases, range node uses the following conditions.

  • Minimum boundary condition: More than minimum value
  • Maximum boundary condition: Less than maximum value and maximum value

For example, a user selects "Scale and wrap within the target range" as Action in the property of range node. After that, the user sets 0-10 as input values and 0-360 as output values.

rangeproperty

The following graph is output when range node processes values between -30 and 30 as input.

range

As the graph result, range node uses incorrect boundary conditions (red circle) when input values are between -30 and -10.

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