Skip to content
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

Num_queries hard coded #39

Open
anirudh-chakravarthy opened this issue May 18, 2021 · 2 comments
Open

Num_queries hard coded #39

anirudh-chakravarthy opened this issue May 18, 2021 · 2 comments

Comments

@anirudh-chakravarthy
Copy link

anirudh-chakravarthy commented May 18, 2021

Hi,

Thank you for sharing your work! I'm trying to replicate results on a 12 GB GPU by reducing the num_frames and num_queries parameters. However, I came across the following error:

outputs_seg_masks = outputs_seg_masks.reshape(1,360,outputs_seg_masks.size(-2),outputs_seg_masks.size(-1))
RuntimeError: shape '[1, 360, 75, 76]' is invalid for input of size 1710000

I pinpointed the issue to Line 126, where I think 360 should be replaced with self.vistr.num_queries. Could you correct this in your release?

Also, can you explain what 24 denotes in Line 115?

Thanks!

@elvindp
Copy link

elvindp commented Aug 17, 2021

Hi,

Thank you for sharing your work! I'm trying to replicate results on a 12 GB GPU by reducing the num_frames and num_queries parameters. However, I came across the following error:

outputs_seg_masks = outputs_seg_masks.reshape(1,360,outputs_seg_masks.size(-2),outputs_seg_masks.size(-1))
RuntimeError: shape '[1, 360, 75, 76]' is invalid for input of size 1710000

I pinpointed the issue to Line 126, where I think 360 should be replaced with self.vistr.num_queries. Could you correct this in your release?

Also, can you explain what 24 denotes in Line 115?

Thanks!

could you get any results, after correct the hardcode?
I keep got wrong prediction class and bbox results.
Appreciate it if you can help me.
Thx

@Epiphqny
Copy link
Owner

@anirudh-chakravarthy Thanks very much for your advice! But as there has been a long time and I have no extra time to review the code now, I will correct it in the future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants