-
Notifications
You must be signed in to change notification settings - Fork 97
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
Deleting instance fatal error in sleap multi view #2008
Comments
Hi @bmidler, Apologies for the delay. I am attempting to recreate the issue, but am having trouble. Are you able to provide the error message you are getting in the terminal? Additionally, are you able to provide us with a troubleshooting dataset? This would include just the slp file (no videos needed) with predictions on at least one frame (which we can then try adding to an instance group to see what is happening). If you feel comfortable providing that, please upload to this form. Thanks, |
Hi @bmidler, I tried to exactly recreate what you did in the video you sent over - thanks for that. But, I am still having trouble using my own dataset (I've sent you a video recording of my recreation failure on slack). It would be very helpful to me if you could send me the slp file (no videos needed - thus it'd be relatively small data to be sent). I need the slp file to have a prediction on the current frame (lmk which frame please). From there, I will investigate the slp using the sleap API to lookout for anything obviously strange. I will also use the vscode debugger to run the GUI, add the instance to an instance group, delete prediction, and figure out why the error we see is just the You can upload the slp to this form. Thanks, |
Hi, I've been working with sleap multi-view (the latest version of this branch) and have observed and reproduced the following bug:
When I do this, the instance is not deleted, and when I go to save the project an error message is thrown and, critically, the project file has been deleted.
The text was updated successfully, but these errors were encountered: