Changing the scale of the robot

Offen
#363 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
35/100
Issue-Typ
Bug
Klarheit
Muss geklärt werden
Aktivitätsstatus
Veraltet
Tech-Stack
csharp, docker, unity
Bereich
ar-vr-xr, robotics

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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:

  1. Scale the robot (or the parent)
  2. Plan a trajectory with moveit
  3. Execute the returned trajectories
  4. 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

Vorherrschende Sprache
C#
Sterne
2.6k
Forks
473
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Entwicklungsumgebung

  • Kein Dockerfile und keine Docker-Compose-Datei
  • Hat eine Pull-Request-Vorlage
  • Kein Beitragsleitfaden

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus Unity-Technologies/Unity-Robotics-Hub

Alle Issues in Unity-Technologies/Unity-Robotics-Hub

Ähnliche Issues

Weitere Issues zu C#

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.