Changing the scale of the robot

Ouverte
#363 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
35/100
Type d'issue
Bug
Clarté
À clarifier
Activité
À l'abandon
Stack technique
csharp, docker, unity
Domaine
ar-vr-xr, robotics

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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

Langage dominant
C#
Étoiles
2.6k
Forks
473
Métriques de merge des PR
Aucune PR mergée en 30 j

Préparer son environnement

  • Aucun Dockerfile ni fichier Docker Compose
  • Propose un modèle de pull request
  • Aucun guide de contribution

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de Unity-Technologies/Unity-Robotics-Hub

Toutes les issues de Unity-Technologies/Unity-Robotics-Hub

Issues similaires

Plus d'issues C#

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.