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

Instacrash with fluid.umap~ (minimum @numneighbours?) #331

Open
rconstanzo opened this issue Aug 24, 2022 · 0 comments
Open

Instacrash with fluid.umap~ (minimum @numneighbours?) #331

rconstanzo opened this issue Aug 24, 2022 · 0 comments

Comments

@rconstanzo
Copy link

I imagine this relates to another bug report, but it looks like that got moved/closed. I think having to do with the minimum amount of @numneighbours. In this use case I'm using fluid.datasetquery~ to proccess a dataset, so I don't know how many (or few) matches I will get. So without building a bunch of scaffolding before UMAP, it's pretty dangerous.

It's 100% reproducible on version 1.0.4+sha.9b29419.core.sha.60e1a77

I'm on Max 8.3.1 on OSX 10.14.6

Steps to reproduce:
load crashing_dataset.json into fluid.dataset~
send fittransform starter to fluid.umap~

Screenshot 2022-08-24 at 5 15 15 pm

crashStuff.zip

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