Gazebo | Ignition | Community
Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Problem after adding properties to SDF description of collision objects

Hello!

I'm facing a small problem with properties I added to the SDF description for collision objects. The parsing of the modified SDF file as well as querying the added properties does not cause any warnings or errors, and works as intended.

However, the visual description of a model definition fails to get parsed correctly if my added properties are present in a model definition. A temporary workaround is to move the visual SDF description in front of the collision SDF description: If I do that, there's no problem with parsing the SDF file.

To summarize, an example model definition including my added properties: http://pastebin.com/BCiCXniq

Without my new properties, the model file is parsed correctly.

Since the mentioned workaround (swapping the order of "visual" and "collision") is not causing any issues, I'm currently out of ideas for what could cause this problem, and what I could do to fix this another way than manually swapping the order of "visual" and "collision" descriptions in each model I'd like to add my new properties to, and I'd appreciate any hints or tips.

Thank you very much!

With best regards, Fabian Aichele

click to hide/show revision 2
gz sdf --print <path_to_model>/model.sdf; no error messages

Problem after adding properties to SDF description of collision objects

Hello!

I'm facing a small problem with properties I added to the SDF description for collision objects. The parsing of the modified SDF file as well as querying the added properties does not cause any warnings or errors, and works as intended.

However, the visual description of a model definition fails to get parsed correctly if my added properties are present in a model definition. A temporary workaround is to move the visual SDF description in front of the collision SDF description: If I do that, there's no problem with parsing the SDF file.

To summarize, an example model definition including my added properties: http://pastebin.com/BCiCXniq

Without my new properties, the model file is parsed correctly.

Since the mentioned workaround (swapping the order of "visual" and "collision") is not causing any issues, I'm currently out of ideas for what could cause this problem, and what I could do to fix this another way than manually swapping the order of "visual" and "collision" descriptions in each model I'd like to add my new properties to, and I'd appreciate any hints or tips.

UPDATE: I used the gz command line utility to check if there are parsing errors with the added tags. There were no error or warning messages with the new SDF properties I added, however I could reproduce the issue with swapped order of "visual" and "collision" tag groups. Output of gz sdf --print path_to_model/model.sdf http://pastebin.com/eEVxF7ad I have no plausible explanation why the presence of new SDF properties in the "collision" tag group might cause the "visual" tag group to miss.

Thank you very much!

With best regards, Fabian AicheleAichele

Problem after adding properties to SDF description of collision objects

Hello!

I'm facing a small problem with properties I added to the SDF description for collision objects. The parsing of the modified SDF file as well as querying the added properties does not cause any warnings or errors, and works as intended.

However, the visual description of a model definition fails to get parsed correctly if my added properties are present in a model definition. A temporary workaround is to move the visual SDF description in front of the collision SDF description: If I do that, there's no problem with parsing the SDF file.

To summarize, an example model definition including my added properties: http://pastebin.com/BCiCXniq

Without my new properties, the model file is parsed correctly.

Since the mentioned workaround (swapping the order of "visual" and "collision") is not causing any issues, I'm currently out of ideas for what could cause this problem, and what I could do to fix this another way than manually swapping the order of "visual" and "collision" descriptions in each model I'd like to add my new properties to, and I'd appreciate any hints or tips.

UPDATE: I used the gz command line utility to check if there are parsing errors with the added tags. tags, as suggested by scpeters (thank you for the tip). There were no error or warning messages with the new SDF properties I added, however I could reproduce the issue with swapped order of "visual" and "collision" tag groups. Output of gz sdf --print path_to_model/model.sdf http://pastebin.com/eEVxF7ad I have no plausible explanation why the presence of new SDF properties in the "collision" tag group might cause the "visual" tag group to miss.

Thank you very much!

With best regards, Fabian Aichele

Problem after adding properties to SDF description of collision objects

Hello!

I'm facing a small problem with properties I added to the SDF description for collision objects. The parsing of the modified SDF file as well as querying the added properties does not cause any warnings or errors, and works as intended.

However, the visual description of a model definition fails to get parsed correctly if my added properties are present in a model definition. A temporary workaround is to move the visual SDF description in front of the collision SDF description: If I do that, there's no problem with parsing the SDF file.

To summarize, an example model definition including my added properties: http://pastebin.com/BCiCXniq

Without my new properties, the model file is parsed correctly.

Since the mentioned workaround (swapping the order of "visual" and "collision") is not causing any issues, I'm currently out of ideas for what could cause this problem, and what I could do to fix this another way than manually swapping the order of "visual" and "collision" descriptions in each model I'd like to add my new properties to, and I'd appreciate any hints or tips.

UPDATE: I used the gz command line utility to check if there are parsing errors with the added tags, as suggested by scpeters (thank you for the tip). There were no error or warning messages with the new SDF properties I added, however I could reproduce the issue with swapped order of "visual" and "collision" tag groups. groups.

Output of gz sdf --print path_to_model/model.sdf http://pastebin.com/eEVxF7ad

I have no plausible explanation why the presence of new SDF properties in the "collision" tag group might cause the "visual" tag group to miss.

Thank you very much!

With best regards, Fabian Aichele