SegNext icon indicating copy to clipboard operation
SegNext copied to clipboard

SegNext require many clicks when I run demo on DAVIS test image

Open Z-MU-Z opened this issue 1 year ago • 5 comments

00013.jpg the checkpoint is vitb_sa2_cocolvis_hq44k_epoch_0.pth

img_v3_02es_40bc3336-9de3-4bb6-a065-fc927442f0ag

I compare with simpleclick, which only require a few clicks

img_v3_02es_4a0a579f-cf8f-465d-b8e9-5433c31674ag

another case 00340.jpg

image img_v3_02es_9ebdb6b0-38a1-41d2-a1b7-d26bee727b1g

Z-MU-Z avatar Sep 19 '24 09:09 Z-MU-Z

Thank you for pointing that out. As we demonstrated in Table 1, SimpleClick actually outperforms SegNext in terms of NoC95 and NoF95. Since SegNext is still in the research stage and requires further refinement, it may not be the best choice for real-world applications.

qinliuliuqin avatar Sep 19 '24 14:09 qinliuliuqin

Thanks for your reply. BTW, is this demo support box input?

Z-MU-Z avatar Sep 21 '24 06:09 Z-MU-Z

This demo is derived from RITM and currently supports only points. I'm developing a more general GUI for diverse prompts, which will be released in a follow-up.

qinliuliuqin avatar Sep 21 '24 13:09 qinliuliuqin

Hello, are you saying that your current demo program can only implement the "point" prompt type? But I noticed that the paper involves the collaboration of multiple prompt types—does the code you provided cover this part?

lmr2706 avatar Sep 04 '25 08:09 lmr2706

@lmr2706 Hi, please refer to https://github.com/uncbiag/SegNext/issues/12.

qinliuliuqin avatar Sep 04 '25 17:09 qinliuliuqin