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
We don't have plans at the moment to add DP3 as a tested baseline. However we are open to pull requests to help merge a baseline like that in! DP3 is certainly a nice baseline we would love to have. I can provide guidance on the necessary requirements for new baselines in this repo (e.g. what metrics to report, wandb logs etc.).
I have encountered a problem while trying to use point cloud data as observations to complete the PickCube-v1 task. The point cloud does not capture the target position, which hinders the successful completion of the task.
My question is: How can we ensure that the target position is observed when using point cloud data as observation input (e.g., in the PickCube task)?
What do you mean it is not captured? Do you have an example? Is target position referring to the green goal? If so the target position is part of the observation dict (see obs["extra"])
For example, in the PickCube-v1 task, the original point cloud does not include the target position. For pure point cloud processing algorithms (such as DP3), the amount of point cloud information here is not sufficient to complete the task. However, manually completing the point cloud from the information in obs ['extra '] may be a solution.
But the best way is still to obtain a point cloud of the virtual object (target location, green point in the following figure)
I would like to inquire whether there are plans to develop another diffusion policy method as a baseline, such as the 3D Diffusion Policy (DP3)3D Diffusion Policy (DP3)
The text was updated successfully, but these errors were encountered: