URDF Compose is a package for dynamically composing urdfs in Python.
Often, robotics codebases will need to be written to deal with a whole host of combinations of hardware. For instance, say a codebase deals with robots that are built of a robot arm and a gripper. And say the system is built to deal with have 2 types of robot arms, and 5 types of grippers. In order to do this, one needs a different URDF for each of the 10 possible combinations. Traditionally, this would likely be done either by creating a seperate URDF by hand for each combination, or by creating a seperate XACRO for each one.
This package provides another solution by allowing one to dynamically compose urdfs using Python code. That way, one only need to create a urdf per component, and doesn't have to do exponentially more work with more components.
Install urdf-compose: pip install urdf-compose
It is also recommended to install check-urdf.
For Ubuntu: sudo apt-get install liburdfdom-tools
For Mac: brew install urdfdom
Other Operating Systems: https://command-not-found.com/check_urdf
If you can't install check-urdf, you must disable it in urdf compose using globally_disable_check_urdf
The first step to use URDF Compose is to mark the input and output links on the URDFs of the components that will make up your robot. Simply stick “INPUT:” or “OUTPUT:” at the start of the names of the links you want to mark. Note that upper case means its the default link–if you need multiple inputs or outputs, use lower cases. You can find the examples here.
Once you have your urdfs, the protocol for connecting them is very simple.
from urdf_compose import ExplicitURDFObj, sequence
urdf1 = ExplicitURDFObj(PATH_TO_SOME_URDF1)
urdf2 = ExplicitURDFObj(PATH_TO_SOME_URDF2)
very_simple_connected_urdf = sequence(urdf1, urdf2)The above example will connect an output link on urdf1 to an input link on urdf2.
You can also use branch if you want to connect many urdfs to the same base urdf. So if you have three urdfs you could connect them with sequence that would connect the third urdf to the second urdf, and the second urdf to the first urdf. Or you could use branch, which would connect both the second and third urdf to the first urdf:
from urdf_compose import ExplicitURDFObj, sequence
urdf3 = ExplicitURDFObj(PATH_TO_SOME_URDF3)
triple_sequence = sequence(urdf1, [urdf2, urdf3])
triple_branch = branch(urdf1, [urdf2, urdf3])You can then use the output of sequence or branch just like any other urdf. So one could do:
big_sequence = sequence(triple_sequence, triple_branch)The following example shows how you can connect urdf2 to urdf1, but rather than using the default output link on urdf1, you want to use a link "output:some_other_output":
from urdf_compose import URDFConn
non_default_connected_urdf = sequence(urdf1, (urdf2, URDFConn("some_other_output")))If you wanted to also specify a different input link to use on urdf2, in this example "input:some_other_input"), you would do:
from urdf_compose import URDFConn
non_default_connected_urdf = sequence(urdf1, (urdf2, URDFConn("some_other_output", "some_other_input")))Dealing with URDFs is a pain. A major benefit of moving the composition of urdfs to code is it allows better and more systematic error checking.
Firstly, when you instantiate an ExplicitURDFObj, it will immediately run check_urdf on the given file. check_urdf is provided by urdf dom tools, and will give a very helpful debugging message if for whatever reason your URDF isn’t valid. Automatically checking the component urdfs provides a major source of robustness, as finding issues in the much larger final composed urdf is much harder.
Both sequence and branch may return a URDFComposeError instead of a new urdf object. The error means that, usually because there were no correctly marked links, it couldn’t combine the urdfs it was given. The URDFComposeError like most errors has a message, but it also has a save_to method. This takes a directory to write the two urdfs that couldn’t be connected to. Without being able to see the offending urdfs, that themselves are likely composed and hence don’t exist somewhere else, any issues at the connection step would be opaque.
Note that if sequence or branch are passed a URDFComposeError, rather than performing the operation, it will simply return the exception. This allows you to pass the output of a sequence or branch call to another, so you only have to handle the error once you want to actually use the urdf.
When you want to save a urdf to a file, you should first handle the error. Say you want to save the big_sequence we defined earlier, you can:
from urdf_compose import write_and_check_urdf, raise_if_compose_error
# Note: if you don’t want to get the debugging info, you can simply not pass the directory argument to `raise_if_compose_error`
big_sequence = raise_if_compose_error(big_sequence, SAVE_DIRECTORY)
write_and_check_urdf(big_sequence, SAVE_DIRECTORY / SAVE_FILE_NAME)Here, the second argument to raise_if_compose_error will be used as the directory for URDFComposeError.save_to if the value is an error and not a urdf. And finally, write_and_check_urdf will call check_urdf one more time.
During composition, urdf compose has to rename links and joints if there are name collisions between two urdfs. It also needs to rename input and output links when they are connected to show that they can't be used anymore.
So that you don't have to think about what this naming scheme is, the ComposedURDFObj returned by sequence and branch has a ComposedURDFNameMap which allows you to look up what the new name of a link or joint is.
The following example shows how you can determine the new name of some link "A" from urdf2 is in the very_simple_connected_urdf urdf
name_map = very_simple_connected_urdf.name_map
collapsed_name_map = name_map.collapse({urdf2})
new_name = collapsed_name_map.lookup(urdf2, "A")The following example illustrates how to use this package to create a urdf of a number of rods connected in a chain.
In order to combine the urdfs, each component urdf needs links to represent "inputs" and "outputs". Simply put, "inputs" are spots on the component where it can connect to the rest of the urdf, and "outputs" are where other urdfs can be connected to it.
Below is a urdf we can use for creating this chain of rods:
<?xml version="1.0" encoding="utf-8"?>
<robot name="rod">
<link name="INPUT-rod">
<inertial>
<origin xyz="0 0 0" rpy="0 0 0" />
<mass value="1.0" />
<inertia ixx="1E-04" ixy="0" ixz="0" iyy="1E-04" iyz="0" izz="1E-05" />
</inertial>
</link>
<link name="OUTPUT-rod"/>
<joint name="joint" type="fixed">
<origin xyz="0 0 0.05" rpy="0 0 0" />
<parent link="INPUT-rod" />
<child link="OUTPUT-rod" />
<axis xyz="0 0 0" />
</joint>
</robot>Notice the names of input and output links start with "INPUT" and "OUTPUT" respectivelly. This indicates that they are the default input and output links. If they were lowercase, it would indicate they are inputs and outputs, but you would need to explictly indicate what input or otuput you want to use.
Let's look at basic code for creating a new urdf composed of two rods:
from urdf_compose import ExplicitURDFObj, sequence, raise_if_compose_error
ROD_PATH = ...
ROD_PAIR_PATH = ...
# Create an object referencing the original file, and checks the urdf to make sure its valid
extender_urdf = ExplicitURDFObj(ROD_PATH)
# Basic construct for making a sequence of n urdfs, each connected to the previous
# raise_if_compose_error is required rather than raising automatically, so that you specify a
# directory to output debugging info. Debugging why your urdf compose isn't working may be
# difficult, so this is an important step to make it easier
composed_urdf = raise_if_compose_error(
sequence(extender_urdf, extender_urdf), ROD_PAIR_PATH
)
write_and_check_urdf(composed_urdf, ROD_PAIR_PATH) # Checks the urdf is valid, and writes the urdf to the fileYou can see this example in examples/simple_chain/make_chain.py. It will output a urdf with:
- both of the extender urdfs
- appropriate links and joints renamed as to prevent name collisions
- a dummy joint (fixed, with 0 origin and axis), that connects the two urdfs.
As a result of these requirments, the output becomes very hard for a human to read. Nonehteless, let's take a look at it:
<?xml version='1.0' encoding='UTF-8'?>
<robot name="vgc10_link">
<link name="INPUT-link">
<inertial>
<origin xyz="-1.14523654741374E-09 -2.79672501268441E-08 0.0228788479998501" rpy="0 0 0" />
<mass value="0.00550575237578726" />
<inertia ixx="1.33005016450342E-06" ixy="-5.64140714952826E-13" ixz="2.57434879543699E-14" iyy="1.33986100736006E-06" iyz="2.43974888325099E-13" izz="1.66618922257867E-07" />
</inertial>
</link>
<link name="CONNECTED:OUTPUT-link"><inertial>
<origin xyz="0 0 0" rpy="0 0 0" />
<mass value="0" />
<inertia ixx="0" ixy="0" ixz="0" iyy="0" iyz="0" izz="0" />
</inertial></link>
<joint name="joint" type="fixed">
<origin xyz="0 0 0.05" rpy="0 0 0" />
<parent link="INPUT-link" />
<child link="CONNECTED:OUTPUT-link" />
<axis xyz="0 0 0" />
</joint>
<joint name="GENERATED_CONNECTION" type="fixed">
<origin xyz="0 0 0" rpy="0 0 0" />
<parent link="CONNECTED:OUTPUT-link" />
<child link="CONNECTED:INPUT-link" />
<axis xyz="0 0 0" />
</joint><link name="CONNECTED:INPUT-link">
<inertial>
<origin xyz="-1.14523654741374E-09 -2.79672501268441E-08 0.0228788479998501" rpy="0 0 0" />
<mass value="0.00550575237578726" />
<inertia ixx="1.33005016450342E-06" ixy="-5.64140714952826E-13" ixz="2.57434879543699E-14" iyy="1.33986100736006E-06" iyz="2.43974888325099E-13" izz="1.66618922257867E-07" />
</inertial>
</link>
<link name="OUTPUT-link"><inertial>
<origin xyz="0 0 0" rpy="0 0 0" />
<mass value="0" />
<inertia ixx="0" ixy="0" ixz="0" iyy="0" iyz="0" izz="0" />
</inertial></link>
<joint name="joint(1)" type="fixed">
<origin xyz="0 0 0.05" rpy="0 0 0" />
<parent link="CONNECTED:INPUT-link" />
<child link="OUTPUT-link" />
<axis xyz="0 0 0" />
</joint>
</robot>Notice the:
GENERATED_CONNECTIONjoint- The used output and input links get the literal
CONNECTEDappended to the start of its name
With these renames, one might want to know the new name of a link or joint. The following example shows how to find what "joint" in the second of the urdfs gets renamed to:
extender_urdf1 = ExplicitURDFObj(ROD_PATH)
extender_urdf2 = ExplicitURDFObj(ROD_PATH) # Note: we have two seperate objects. Reasoning is explained later.
# Here we don't pass a directory to save debugging output to. It is recommended to pass it, but if for whatever reason you desire not to, it is not necessary.
composed_urdf = raise_if_compose_error(sequence(extender_urdf1, extender_urdf2))
name_map = composed_urdf.name_map.collapse({extender_urdf2}) # Get an object that allows us to lookup new names for the given urdfs
print(name_map.lookup(extender_urdf2, "joint")) # prints "joint(1)"Note that we have to create this object out of seperate urdf objects, even though they are from the same file. If we didn't, the name map wouldn't be able to distinguish between the first and second urdf. To illustrate this, we have the following example:
extender_urdf = ExplicitURDFObj(ROD_PATH)
composed_urdf = raise_if_compose_error(sequence(extender_urdf, extender_urdf))
name_map = composed_urdf.name_map.collapse_safe({extender_urdf2}) # Using "collapse_safe" so that it returns the error
print(name_map) # prints a "RepeatedURDFError" objectThe following example illustrates how we can create a composed urdf where one component has two outputs.
We now introduce the following urdf, that is like the original rod, except it has an extra output half way down the rod, faced sideways:
<?xml version="1.0" encoding="utf-8"?>
<robot name="v_rod">
<link name="INPUT-rod">
<inertial>
<origin xyz="0 0 0" rpy="0 0 0" />
<mass value="1.0" />
<inertia ixx="1E-04" ixy="0" ixz="0" iyy="1E-04" iyz="0" izz="1E-05" />
</inertial>
</link>
<link name="OUTPUT-straight_output"/>
<link name="output-sideways_output"/>
<joint name="joint_straight" type="fixed">
<origin xyz="0 0 0.05" rpy="0 0 0" />
<parent link="INPUT-rod" />
<child link="OUTPUT-straight_output" />
<axis xyz="0 0 0" />
</joint>
<joint name="joint_sideways" type="fixed">
<origin xyz="0 0.05 0.025" rpy="0 0 1.57" />
<parent link="INPUT-rod" />
<child link="output-sideways_output" />
<axis xyz="0 0 0" />
</joint>
</robot>The following code shows how we can connect this urdf to two other rods:
V_ROD_PATH = ...
rod_urdf1 = ExplicitURDFObj(ROD_PATH)
rod_urdf2 = ExplicitURDFObj(ROD_PATH)
v_rod_urdf = ExplicitURDFObj(V_ROD_PATH)
simple_branched_chain = branch(
v_rod_urdf,
[
rod_urdf1,
# Note that we have to specify which output the second rod is using, b/c
# it is not connected to the default output
(rod_urdf2, URDFConn("sideways_output"))
]
)In addition, we can combine a branch and a sequence in order to attach a rod to the input of the v rod.
BRANCHED_CHAIN_OUTPUT = ...
rod_urdf3 = ExplicitURDFObj(ROD_PATH)
full_chain = raise_if_compose_error(
sequence(
rod_urdf3,
simple_branched_chain
)
)
write_and_check_urdf(full_chain, BRANCHED_CHAIN_OUTPUT)Note that in the above example, from a typing perspective, simple_branched_chain may be a URDFComposeError. If it is, the sequence function will immediatly return that error. This pattern allows you to only call raise_if_compose_error when you actually need the urdf at the end.