-
Notifications
You must be signed in to change notification settings - Fork 197
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
Question About Automatic Object Prediction in XMem/XMem++ #154
Comments
Hello, thanks for your interest in our project! Unfortunately, they could not. We have a follow-up work DEVA that attempts automatic segmentation. There are also a lot of recent works from other folks that try to automatic this with language interaction, such as https://github.com/magic-research/Sa2VA |
Thank you so much for your quick response! I really appreciate the information. Best, |
Hello, Thank you again for your work on XMem! After trying other methods, I find XMem to be the most suitable for my needs. My goal is to predict masks for a specific domain and object with the highest possible accuracy while minimizing manual interaction. I am wondering if the following approach would be feasible:
The key question is whether it is possible to provide reference frames in this manner. Could you share any insights or advice on this approach? Thank you for your time! |
You can run XMem/XMem++ via propagation as long as there is at least one labeled frame per video. Does this answer your question? |
Thank you for your response! |
Dear authors,
Thank you for your great work on XMem/XMem++! I have a question regarding its capabilities.
Is XMem or XMem++ able to predict a specific type of object without manual interaction? In my research, I aim to generate object-wise segmentation for surgical tools, and I am wondering whether this process can be fully automated. Would fine-tuning the model on surgical tool data help achieve this?
I would really appreciate any insights or recommendations on this.
Thank you for your time!
Best regards,
Lily
The text was updated successfully, but these errors were encountered: