-
Notifications
You must be signed in to change notification settings - Fork 3
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
Crash Report #92
Comments
Thanks the the details! I have not reproduced that first one yet. Vicente conjectures it may be different sized images sneaking into the same batch. For the second |
@Erotemic Can you share the dataset that triggered the first runtime error |
As for the second error this seems to be about our Vue component passing the wrong dimension to the umap property. For the first error I am still investigating this |
@Erotemic I spent sometime trying to reproduce this but I could not, could you share the steps and dataset used to reproduce this? On another topic we do group images by its pixel size, this is important for batching (an considerable performance improvement technique). However, we do not consider the image color bits meaning that if you have images with different color density this could occur, is this is the case with the dataset. If that is the case the solution in the code will be trivial (convert all images to RGB before passing to the model). |
Not sure exactly what happend, but I was attempting to explore a small dataset and I got this traceback:
On a clean run with a 3D UMAP embedding I was able to click around and look at several images, but some gave me an error saying
JS Error => error: Uncaught TypeError: Cannot read properties of undefined (reading 'getPointSequenceIndex')
. With 2D UMap it didn't seem to cause a problem. Traceback is:The text was updated successfully, but these errors were encountered: