google-deepmind / google-deepmind/dm_control

Exported XML loses meshdir and relative mesh paths

Abierto
#523 1 comentario 2 reacciones 0 asignados Ver en GitHub
Lenguaje dominante
Python
Estrellas
4.7k
Forks
764
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

I'm using PyMJCF to load a robot model from an XML file and build a MuJoCo scene. When I export the composed scene back to an XML string using `scene_model.to_xml_string()`, I've run into an issue with the file paths.

### The Problem

The exported XML file is missing the directive. Meanwhile, all the mesh file paths, which were originally relative to that directory, are now missing their path prefixes.

For example, a mesh defined like `file="my_robot/meshes/part1.stl"` becomes `file="part1.stl"` in the exported file.

### Code Snippet

Here is the line of code I'm using for the export:

```Python
final_xml_string = scene_model.to_xml_string()
```

### What I've Found

I found a related issue (#454) that suggests using mjcf.export_with_assets(...) as a potential solution for managing assets.

### My Questions

1. Is there a direct method in PyMJCF to preserve the meshdir compiler attribute and the corresponding relative file paths when exporting a model to an XML string?

2. Separately, my main goal is to visualize the composed scene. I know `dm_control.viewer` can be used for simulations. Does the viewer also support loading and visualizing a custom MJCF scene like the one I'm building?

Thanks for your help!

Guía de contribución

Abrir la guía de contribución

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.