We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
This might not be a problem if all points are always moved into the positive domain. but if not points that are mirrored sometimes collide.
1. Original: ([0.89963308, 0.30712294, 0.81770174]) Mirrored: ([-0.89963308, 0.30712294, 0.81770174]) 2. Original: ([0.76068334, 0.49337516, 0.68670659]) Mirrored: ([-0.76068334, 0.49337516, 0.68670659]) 3. Original: ([0.38544234, 0.94407035, 0.39409715]) Mirrored: ([-0.38544234, 0.94407035, 0.39409715]) ... and so on.
anyway, this might lead to some issued if the points are not all put in the positive domain.
The text was updated successfully, but these errors were encountered:
thanks for letting me know. I will look into this in next week.
Sorry, something went wrong.
we just added that to the top of the hash function, should be relatively fast and solves the issue as far as i tested it
# move all vertices to positive space arr -= np.min(arr, axis=0)
No branches or pull requests
This might not be a problem if all points are always moved into the positive domain. but if not points that are mirrored sometimes collide.
anyway, this might lead to some issued if the points are not all put in the positive domain.
The text was updated successfully, but these errors were encountered: