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

Questions about overlapping test and real-time prediction #14

Open
cccvision opened this issue Jul 26, 2023 · 1 comment
Open

Questions about overlapping test and real-time prediction #14

cccvision opened this issue Jul 26, 2023 · 1 comment

Comments

@cccvision
Copy link

hi authors, I have some questions about the overlapping test, thanks in advance for your help!

  1. Can this work really run in real-time? In the paper, it is written that ' AGRoL model achieves real-time inference speed' because it 'produces 196 output frames in 35 ms'. However, for online prediction, given one new observation, we only need one prediction (like what AvatarPoser did), 196 outputs seem redundant, how do you make it work for real-time usage?

  2. when I tried to test with overlapping, It shows the following errors:
    python test.py --model_path /path/to/your/model --timestep_respacing ddim5 --support_dir /path/to/your/smpls/dmpls --dataset_path ./dataset/AMASS/ --overlapping_test

Loading dataset...
100%|█████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 536/536 [00:00<00:00, 1072.94it/s]
Creating model and diffusion...
Loading checkpoints from [pretrained_weights/diffmlp.pt]...
Overlapping testing...
0%| | 0/536 [00:00<?, ?it/s]
Traceback (most recent call last):
File "test.py", line 552, in
main()
File "test.py", line 516, in main
output, body_param, head_motion, filename = test_func(
File "test.py", line 269, in overlapping_test
memory_end_index = sparse_splits[step_index][1]
IndexError: index 1 is out of bounds for dimension 0 with size 1

@asanakoy
Copy link
Member

asanakoy commented Aug 3, 2023

Hey. Even if you run prediction with a sliding window of stride 1, then it will require 35 ms per every prediction. Which is ~30 FPS

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