Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Isaac Sim backend

Abierto
  • ¿Algo no está bien?
#903 1 comentario 1 reacción 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
python
Área
backend, robotics

Línea de trabajo

Start with the backend protocol changes in #676 and the backend registry work in #902, then read the URDF loading path and Isaac Sim 6.2's SimulationApp and URDF importer documentation. The issue defines the first milestone around a desktop scene, URDF-backed robots, per-instance joint state, and a screencast; testing strategy, Python version support, restart behavior, and expanded URDF handling still need decisions. The linked prerequisite and request for a named contributor make this a poor first issue.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

enhancement

Part of #886. For @alexermolovich — please comment here so you can be assigned.

Scope (milestone 1)

  • backend="isaacsim" starts Isaac Sim via SimulationApp, with a basic scene (camera, lighting)
  • add(robot) for URDF-backed robots, converted to USD with Isaac's URDF importer
  • add() returns a handle that owns its own q, so several instances of one model work
  • Desktop only, Isaac Sim 6.2, optional isaacsim extra with a lazy import; import roboticstoolbox must still work without it

Target

A URDF Panda from robot_descriptions:

panda.plot(panda.qr, backend="isaacsim")
traj = rtb.jtraj(panda.qz, panda.qr, 50)
panda.plot(traj.q, backend="isaacsim", dt=0.05)

A screencast in Discussions → Show & Tell.

Out of scope for now

Notebooks, teach, ellipsoids, ETS/DH robots, physics-driven step.

Open questions (to settle before the PR is reviewed)

  1. Testing. Isaac Sim needs a GPU and isn't open licensed, so it can't run in CI. What's testable without it (mocked SimulationApp, joint-mapping logic), and what's the manual checklist for the rest?
  2. Dispatch. Blocked by #902 (backend registry). Register the backend there as isaacsim. Once #902 is merged, you can also develop and test outside the RTB tree with register_backend("isaacsim", ...).
  3. Expanded URDF. Keeping the expanded XML (Xacro args, patches) changes RTB's URDF loading. Please do that as a separate, small PR first.
  4. Python versions. Isaac Sim targets 3.12, while RTB supports 3.10–3.14. The extra should install only where Isaac Sim does.
  5. restart(). If Isaac Sim can't restart in-process, raise a clear error and say so in the docs, rather than half-supporting it.

Process

  • One backend per PR. Open a draft PR early.
  • Follow #676 (protocol changes) and avoid relying on Gripper details (#884).
  • Say in the PR if an AI assistant helped (AGENTS.md).
  • If there's been no activity for about four weeks, the backend goes back to "available" in #886.

Generated by Claude Code

Lenguaje dominante
C++
Estrellas
3.6k
Forks
645
Merge medio
1 d 8 h
PR fusionados (30 d)
145

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de petercorke/robotics-toolbox-python

Todos los issues de petercorke/robotics-toolbox-python

Issues similares

Más issues de C++

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.