So the URDF was intended for visualization purposes. Don’t you think acceleration limits to avoid abrupt motion are also part of good visualizations?
If velocity and acceleration limits are part of the URDF, it only makes sense to add jerk as well.
So the URDF was intended for visualization purposes. Don’t you think acceleration limits to avoid abrupt motion are also part of good visualizations?
If velocity and acceleration limits are part of the URDF, it only makes sense to add jerk as well.
I recently created a tool to convert EMF Ecore (EMF Project Redirection) to python classes as well as Json schema: GitHub - hsd-dev/urdf-model. This ecore model is converted from urdf.xsd
The python classes can be populated by parsing URDF file: see here
The generated Json schema is used for GitHub - redhat-developer/yaml-language-server: Language Server for YAML Files, which can be used for schema validation, code completion, etc.
For future, I will be using the ecore meta-model also to update the schema documentation.
Happy to get some comments and feedback.