-
Notifications
You must be signed in to change notification settings - Fork 63
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
DataPreparation understanding #16
Comments
|
Hi, Thanks for you answer, just to clarify:
674 571 274 0
687 632 314 0
706 632 313 0
707 639 336 0
710 639 329 0
716 639 328 0
718 0 294 0
718 639 332 0
720 639 335 0
724 639 330 0
724 639 331 0
729 550 163 0
735 550 164 0 |
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, first off, congratulations on your work. The use of event data for this is fascinating.
I'm trying to reproduce your work using simulated data and I have a couple of question
What is the FPS you recommend for frame interpolation? As you use a B=5, would it be a safe bet to assume 5 extra frames, between every 2 frames?
Am I understanding this correct? for calendar.h5, data looks like this:
where the shape of each individual voxel tensor is [B, H, W].
So in order to replicate this, should I use
events_to_voxel_torch
on the Event data of each real frame, individually? (When I say real frame, I mean, the original frame plus all the interpolated frames between t and t+1)Thank you
The text was updated successfully, but these errors were encountered: