-
Notifications
You must be signed in to change notification settings - Fork 100
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
Found multiple skeletons after running inference #2025
Comments
Hi @Desvino ! Apologies for the delay! I tried the steps that you mentioned, but I'm not able to replicate this error. Here's what I did:
Could you please let me know if you added any skeletons (used the Thanks, Divya |
Hi @gitttt-1234 ! Thanks, |
Hi @Desvino, Thank you for getting back! Sorry, I'm still not able to replicate the error at my side. Let's try to isolate where the duplicate skeletons are created. Could you please confirm if you were able to see multiple skeletons right after running inference with an existing model (in the Thanks, Divya |
Hi @gitttt-1234 ! I have checked that I found multiple skeletons right after running inference with an existing mode, without any other steps. And I have uploaded the files you mentioned. Desvino |
Hi @Desvino! Thank you for sending the data, I was able to replicate the issue. Thanks @roomrys for your detailed analysis here.
Thanks, Divya |
Hi @gitttt-1234 ! Best regards, |
Hi! Thanks for your help!
Bug description
We first encountered this bug when we tried to use relabelled instances to run training.
When performing a single animal project, it turned to
But it could run when we restarted Sleap.
However, when performing a multiple animal top-down project, it turned to
In this case, it couldn't run when we restarted Sleap.
I think it is a similar issue to #713 and #1090.
When we tried methods you provided in #713 , we found that there were 3 skeletons in our project. These 3 skeletons were totally the same. After deleting the other skeletons, we could run training.
So I think multiple skeletons appeared as followed:
We want to know how can we avoid this bug.Thank you very much!
Your personal set up
The text was updated successfully, but these errors were encountered: