Generative Bionics Robot Models
This repository includes model for robots created by Generative Bionics.
The models contained in this package are:
| Robot Name | URI |
|---|---|
| GENE.01 1.0 | package://gb_robot_models/robots/gene01_0/model.urdf |
To simplify the use of the provided models in all tools, the provided models have been simplified and all closed loop mechanism in the robot are represented by their serial equivalent. Contact Generative Bionics (including gb-robot-models in the request text) if for your use case you need a model with a representation of the closed loop mechanisms or more information.
Package installation from source
If the gb-robot-models is not available in your preferred package manager or distribution channel, you can also install it from source.
Install via pip/uv
The gb-robot-models is a regular Python package, so it can be installed from source with the following command:
python -m pip install "git+https://github.com/gbionics/gb-robot-models.git"
or
uv add "git+https://github.com/gbionics/gb-robot-models.git"
Instal via CMake
The gb-robot-models is a regular CMake package, so it can be installed from source with the following command:
git clone https://github.com/gbionics/gb-robot-models
cd gb-robot-models
cmake -Bbuild -S. -DCMAKE_INSTALL_PREFIX=<desired_install_prefix>
Install via CMake in a colcon/ROS 2 workspace
As gb-robot-models is a regular CMake package equipped with a package.xml, so it can be built as part of regular colcon/ROS 2 workspace, for example on Linux:
mkdir -p ~/gb_robot_models_ws/src
cd ~/gb_robot_models_ws
git clone https://github.com/gbionics/gb-robot-models src/gb-robot-models
colcon build
Use directly from source repo
To use the models directly from the source repo, just add the repository folder to the AMENT_PREFIX_PATH environment variable, for example on Linux:
git clone https://github.com/gbionics/gb-robot-models
export AMENT_PREFIX_PATH=${AMENT_PREFIX_PATH}:$(pwd)/gb-robot-models
Model retrieval
Regardless of how you installed the package, the models can easily be found in Python via resolve-robotics-uri-py:
absolute_path = resolve_robotics_uri_py.resolve_robotics_uri("package://gb_robot_models/robots/gene01_0/model.urdf")
or in C++ via resolve-robotics-uri-cpp:
std::optional<std::string> absolute_path = ResolveRoboticsURICpp::resolveRoboticsURI("package://gb_robot_models/robots/gene01_0/model.urdf")
or using your favorite resource retrieval system for package:// URIs, like ROS's ament_index_cpp or ament_index_py, the files installed in gb-robot-models are installed in a way that they can be found by ROS resource retriever. If you are experiencing problem on this, please open an issue.
License
This repository is licensed under the Creative Commons Attribution-NonCommercial 4.0 International (CC-BY-NC-4.0) license. See the LICENSE file for the full license text.
Contact Generative Bionics (including gb-robot-models in the request text) if for your use case you need a model with a different license.
Metadata
Release files for gb-robot-models 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| gb_robot_models-0.1.0.tar.gz | 7.9 MB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| gb_robot_models-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 15.5 MB
Release files / gb_robot_models-0.1.0.tar.gz
| Download URL | gb_robot_models-0.1.0.tar.gz |
|---|---|
| Size | 7.9 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9f4e4e2514eebb54f650a9b27f633bd69a17b3ac222a0ee1ae82ea987a83a051
|
|
BLAKE2b-256 checksum How to use checksums |
d28a1c2382bc5f42df5983082bc5ba2c9774d364943a3d632bfe2f877e80cdea
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 17, 2026.
Transparency logRelease files / gb_robot_models-0.1.0-py3-none-any.whl
| Download URL | gb_robot_models-0.1.0-py3-none-any.whl |
|---|---|
| Size | 7.6 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a51dd5dac9ed861c39cb0f055facd95312e864e058c5ed5672a6bfbd3da94b7e
|
|
BLAKE2b-256 checksum How to use checksums |
e7ad16ea2cb1114e1a090bb7663613c5b316503f635d37f617412dc683e03e90
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 17, 2026.
Transparency logSecurity for gb-robot-models 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for gb_robot_models-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 17, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.