-
Notifications
You must be signed in to change notification settings - Fork 1
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
the specific value of 𝑀 #4
Comments
I'm having the same problem, what should the exact size of patch_nums be set to? |
Sorry, I did not get a reply from the author, this problem has not been
solved.
xia-zhe ***@***.***> 于2024年4月6日周六 20:17写道:
… I'm having the same problem, what should the exact C be set to?
—
Reply to this email directly, view it on GitHub
<#4 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BG2XMI4M5EFRFUDDJQ6SJM3Y37RVXAVCNFSM6AAAAABEO5ZIMGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANBRGA3DOMBUGI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Hi, Thank you very much for your interest in our work. Firstly, the patch-level features are extracted using CLIP-ViT-B/32, resulting in 49 patches (excluding CLS). This means that we need to select the Top_m patches most relevant to the problem from these 49 patches. In our experiments detailed in the paper, the value of Top_m is set to 20. Thank you again for your attention to our paper. If you have any further questions, please feel free to contact me directly via email. Best, |
Hi, Thank you very much for your interest in our work. Firstly, the patch-level features are extracted using CLIP-ViT-B/32, resulting in 49 patches (excluding CLS). This means that we need to select the Top_m patches most relevant to the problem from these 49 patches. In our experiments detailed in the paper, the value of Top_m is set to 20. Thank you again for your attention to our paper. If you have any further questions, please feel free to contact me directly via email. Best, |
Hello, the article partition each visual frame into 𝑀 patches, could you please tell me the specific value of 𝑀? In the code, feat_script/extract_clip_feat/extract_patch-level_feat.py
img_features = torch.zeros(len(img_list), patch_nums, C) also does not reflect the exact size of patch_nums.
The text was updated successfully, but these errors were encountered: