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

question about the I3D feature #33

Closed
JJBOY opened this issue Jun 19, 2020 · 2 comments
Closed

question about the I3D feature #33

JJBOY opened this issue Jun 19, 2020 · 2 comments

Comments

@JJBOY
Copy link

JJBOY commented Jun 19, 2020

In your paper, it says "We first uniformly divide each input video into 64-frame segments. We then use a two-stream Inflated 3D ConvNet (I3D) model pre-trained on Kinetics [5] to extract the segment features."
However, in your code

interval = 8
clip_length = 64
start_unit = int(min(ft_num - 1, np.floor(float(start_ind + off) / interval)))
end_unit = int(min(ft_num - 2, np.ceil(float(end_ind - clip_length) / interval)))

I guess minusing 64 means you do not use the last few frames not divisible by 64, but why should interval=8?
Is it means that you divide each input video into 8-frame?

By the way? Could you offer the I3D feature on ActivityNet? It's so time-comsuming to extrat.

@Alvin-Zeng
Copy link
Owner

  1. "do not use the last few frames not divisible by 64" --- correct
  2. We extract features in using sliding windows and the stride is set to 8.
  3. We have uploaded the I3D Anet features, please find them in README.md

@JJBOY
Copy link
Author

JJBOY commented Jul 4, 2020

Thanks very much for your reply and your feature!

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

2 participants