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

KDT Closest Edges MK2 - variable output #4143

Closed
Durman opened this issue Jun 4, 2021 · 2 comments · Fixed by #4635
Closed

KDT Closest Edges MK2 - variable output #4143

Durman opened this issue Jun 4, 2021 · 2 comments · Fixed by #4635
Labels

Comments

@Durman
Copy link
Collaborator

Durman commented Jun 4, 2021

With dependencies the node returns one result and witohut them another.

I believe that with the same input output of the node should be persistent.

I'm not sure how this should be fixed. What is difference between nodes which rely on the behaviour without dependencies and nodes relay on the behaviour with dependencies? How they can be distinguished?

@Durman Durman added the bug 🐛 label Jun 4, 2021
@vicdoval
Copy link
Collaborator

vicdoval commented Jun 4, 2021

If you have scipy it offers different modes if you don't it offers only the 'Complete' mode which relies in mathutils kdt.

Maybe it would be enough if the default mode would be 'Complete' so the output does not change when you install the dependecies

@Durman
Copy link
Collaborator Author

Durman commented Jun 4, 2021

When you installed SciPy and created a node tree with the node and then after some time when you open the tree again you see that out put of the tree is strange because you don't remember that in the tree there is one node which was created when SciPy library was available and because the node does not make any hints that if you want to have the same out put you have to install the library.

This is what I mean the node should give persistent output. If the node expects the library to be installed it should make a warning if it's not but not to shift to another output.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants