You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"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?"
The text was updated successfully, but these errors were encountered:
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?
"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?"
The text was updated successfully, but these errors were encountered: