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

About scene.step() #15

Open
duckinchina opened this issue Jul 29, 2024 · 2 comments
Open

About scene.step() #15

duckinchina opened this issue Jul 29, 2024 · 2 comments
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@duckinchina
Copy link

duckinchina commented Jul 29, 2024

"I found that in YARR.yarr.utils.video_utils.py, there is a scene.step() in NeRFTaskRocorder which updates the scene multiple times in a for loop. However, this causes the ball objects to roll on the table. I suspect that this is due to the high frequency of scene updates, amplifying the effect of certain random forces in the scene. However, if I comment out scene.step(), the images of the nerf camera view won't update, although the data can be generated without error. Is there any good solution to this?"

@duckinchina
Copy link
Author

Is there a way to use 50 cameras to capture nerf data instead of having one camera update 50 times for each time step, which would cause the physical engine to exert greater force on the objects, especially on objects with insufficient friction like spheres?

@GuanxingLu
Copy link
Owner

Sorry for the late reply. I am also searching for an acceptable way to capture multi-view images...

@GuanxingLu GuanxingLu added enhancement New feature or request help wanted Extra attention is needed labels Aug 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants