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
Unresponsive on "Quick Search" stage with simple dataset #187
Comments
Can you try according to this as mentioned in the repo, I think the "features" part should not be the in the same code-line. Sample |
@garrettjoecox, considering the size of the data, you might actually need GPU acceleration. To ensure that it is not stuck, can you try with just the first 1000 rows of the DataFrame? |
According to the docs this is valid, as I only want to train on those two columns
However since I have already stripped everything else from my dataset I don't need to specify them as they are the only columns remaining, so I tried removing the features argument and got the same result. |
I tried with less data, (1000, 100, 50, 10 rows) and it seems to have gotten a bit further, but then the kernel dies every time around 30-40% of the way through this step: |
Thank you for the update @garrettjoecox. My best guess is that it is crashing on one of the models. This problem is most likely data specific. Is it possible for you to email the first 1000 rows of data to support@blobcity.com? Trying it on your data will allow us to diagnose better. |
Hey there, I have a dataset I have stripped down to be pretty bare trying to get this library working
The dataframe has 350,000 rows, I figured maybe the size was causing it to be slow but it's been sitting like this for about 15 minutes now, with "kernel busy"
I'm sort of new to this tech so I'm not even sure how I would go about further debugging, any ideas?
The text was updated successfully, but these errors were encountered: