Feature Request: Add support for omni-directional ground mobile platforms

Open
  • Is something wrong?
#27 1 comment 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
cpp
Domain
backend

Research direction

Explore the existing vehicle model implementations and physics simulation code to understand how to add a holonomic movement model. The issue suggests supporting omni-directional platforms via a /cmd_vel ROS interface and providing documentation for custom vehicle models. Done looks like a working omni-directional vehicle option and a tutorial for users to add their own platforms.

Written by the indexing model from the issue text.

Description

enhancement new-model

Feature Request: Add support for omni-directional ground mobile platforms

Overview:

I suggest adding support for omni-directional ground mobile platforms (e.g., holonomic vehicles, robotic dogs like Go2) .

Smaller Details:

This could include:
A new vehicle model or physics simulation for holonomic movement, e.g., via a /cmd_vel ros API.
A tutorial or documentation on how to replace the default vehicle model with a custom omni-directional platform.

Nature of Request:
  • Addition

Why would this feature be useful?

In the field of visual language navigation of outdoor ground unmanned systems, there is a great need for sensor support tools like AirSim to train and test in various scenarios of UE. Commonly used ground unmanned platforms include omnidirectional wheeled cars, mechanical dogs Go2, etc. Can some support for omnidirectional mobile platforms be provided? Or tutorial support for quickly replacing the underlying model? If possible, it will be of great help to the development of visual language navigation.

Dominant language
C++
Stars
890
Forks
170
Avg merge
17h 15m
Merged PRs (30d)
8

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from iamaisim/ProjectAirSim

All issues in iamaisim/ProjectAirSim

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.