Changing the scale of the robot
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 35/100
调研方向
Reproduce the issue in Unity 2020.3.32f1 by scaling the robot or its parent, planning a trajectory with MoveIt, and executing it in the stated ROS and Docker environment. Compare execution at the scaled size with a 1:1 setup, including trajectories containing multiple poses. Done means scaled execution reaches each requested pose with behavior matching the unscaled setup.
由索引模型根据 Issue 内容生成。
描述
Hello everybody.
Describe the bug
I have been using the content of this repo in combination with an Hololens for a few time. Lately I tried to scale the whole holographic experience in order to have a clearer view of the robot moving near a small object.
Moving the robot and the object under a parent object and scaling the parent object, when the trajectory calculated with moveit is returned, the robot behaves in a strange way, moving near the target position and then slowing down to almost being still and reaching the position after many seconds. Also, when more than one pose is requested to moveit, the robot is not able to reach the first pose and moves to the second (or last) one.
To Reproduce
Steps to reproduce the behavior:
- Scale the robot (or the parent)
- Plan a trajectory with moveit
- Execute the returned trajectories
- See abnormal behaviour
Console logs / stack traces
Nothing
Expected behavior
I would expect no difference in respect to the scale 1:1
Environment (please complete the following information, where applicable):
- Unity Version: 2020.3.32f1
- Unity machine OS + version: Windows 10
- ROS machine OS + version: Ubuntu 18.04, ROS Noetic
- ROS–Unity communication: Docker
- Branch or version: e.g. v0.6.0
I think I'm missing something with the physics of the joints due to the change of scale, but I'd appreciate some help to investigate the reason, I think that scaling the experience in a mixed reality context might be a frequent use case.
Thanks,
Jacopo
- 主要语言
- C#
- 星标
- 2.6k
- 派生
- 473
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
Unity-Technologies/Unity-Robotics-Hub 的其他 Issue
-
难度 3/5 1-2 天 新手友好度 35/100
-
ROS2,Action未关闭
难度 4/5 3-5 天 新手友好度 25/100
-
难度 1/5 1 小时以内 新手友好度 20/100
-
难度 5/5 一周以上 新手友好度 15/100
-
难度 4/5 3-5 天 新手友好度 25/100
Unity-Technologies/Unity-Robotics-Hub#433 · 1 条评论 ·
查看 Unity-Technologies/Unity-Robotics-Hub 的全部 Issue
相似的 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 3 天内回复
-
bug python
难度 1/5 1 小时以内 新手友好度 88/100
ilia-sokolov/OfficeAgent.NET#89 ·
维护者通常 13 天内回复
-
documentation
难度 2/5 1-3 小时 新手友好度 82/100
juandresrodca/AdminForge#66 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 70/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
umbraco/Umbraco.Automate#612 ·
维护者通常 1 天内回复