You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[NASA Space ROS Sim Summer Sprint Challenge 2024]: Open 3D Engine Meets Space ROS: A Case Study on Efficacy, Setup Complexity, and Challenges for Space Rover Simulation Using a Physics-Based 3D Game Engine
#181
Open
Mechazo11 opened this issue
Sep 8, 2024
· 0 comments
This issue is related to the submission to NASA Space ROS Sim Summer Sprint Challenge 2024.
Team lead Freelancer username: azmyin12
Submission Title: Integrating O3DE with Space ROS for an Accurate Physics Simulation of the Curiosity Rover: A Case Study
Note to judges: I was unsure how to categorize my submission since it simultaneously brings in a new simulator engine, new assets and a new demo environment altogether. Therefore, I opted to the route of creating a new image based on a customized Dockerfile from space_robot image. Please note about 70 - 80 Gb of free space is require and the computer needs to have an NVIDIA GPU.
Motivation
At ROSCon2023, Robotec.ai demonstrated a large warehouse fullfilment demo (short-version here) containing multiple AMRs, Cobots and human collaborators working together in a photo realistic simulation. This was achieved using the Open 3D Engine, an open-source, Apache 2.0 licensed, modular game engine that utilizes NVIDIA's open-source, Apached 2.0 licensed, PhysX 5.1 physics engine paired with the open-sourced Atom renderer. More details can be found here.
Space rovers like the Curiosity Rover, are very expensive scientific equipment that must go through extensive testing in NASA JPL's Mars Yard. These tests include endurance tests for suspensions, wheels, and mobility on uneven and unknown terrains. Additionally these rovers needs to perform critical tasks such as autonomous driving, object manipulation, path-planning in the absence of human teleportation due to the Earth-Mars communication lag.
Objective
Given the favorable nature of Open 3D Engine's licensing, rapidly developing ROS 2 support and a need for robust, accurate, scalable versatile simulator that incorporates well-understood physics libraries, my submission to this contest is a docker image whose primary purpose is to serve as a test vessel for a case study on the effectiveness, setup complexity, asset generation requirements, and challenges of using Open 3D Engine for space robotics applications, specifically a mobile manipulators like the Curiosity rover.
This image demonstrates the native integration of O3DE with the Space ROS stack by showcasing a new testing environment inspired by the Mars Yard. The picture below shows the environment with the Curiosity rover and several new assets (still a work in progress, will be finalized before September 11th Deadline).
Note the high-fidelity rendering and accurate simulation of wheel-obstacle-suspension interactions. Numerous scenarios can already be envisioned in the test environment i.e. image Curiosity rover transporting a small scientific cargo (little ROSBot) back to its twin, MAGGIE, in building 336 by maneuvering around various obstacles and environmental hazards.
My hope is that this study and demo will highlight the various advantages, benefits, and challenges in using a full 3D game engine for robotics simulations. I would like to conclude by expressing my gratitude to NASA and the Space ROS team for hosting this challenge.
Deliverables
My submission will include
A new docker image that integrates O3DE with Space-ROS via ROS 2 Gem.
A complete O3DE project called RobotSim that comes with two new new asset Gems, NasaCuriosityRoverGem and MarsYardGem.
Instructions on running the demo.
A short report detailing my experience with O3DE, its usefulness to NASA and major challenges that needs to be addressed.
[if time permits] build instructions for native build in the host Ubuntu machine.
The text was updated successfully, but these errors were encountered:
Mechazo11
changed the title
[NASA Space ROS Sim Summer Sprint Challenge 2024]: Integrating Open 3D Engine with Space ROS for an Accurate Physics Simulation of the Curiosity Rover: A Case Study
[NASA Space ROS Sim Summer Sprint Challenge 2024]: Open 3D Engine Meets Space ROS: A Case Study on Efficacy, Setup Complexity, and Challenges for Space Rover Simulation Using a Physics-Based 3D Game Engine
Sep 8, 2024
Mechazo11
added a commit
to Mechazo11/space-ros-docker
that referenced
this issue
Sep 9, 2024
PR to solve space-ros#181 by Azmyin Md. Kamal.
Part of submission to the NASA Space ROS Sim Summer Sprint Challenge 2024.
Freelancer id: azmyin12
Description:
Integrates Open 3D Engine natively with Space ROS via the ROS 2 Gem and showcases
photorealistic, physics-defined simulation of Curiosity rover in a new test environment
inpsired by the NASA JPL's Mars Yard testing ground
Description
This issue is related to the submission to NASA Space ROS Sim Summer Sprint Challenge 2024.
Team lead Freelancer username: azmyin12
Submission Title: Integrating O3DE with Space ROS for an Accurate Physics Simulation of the Curiosity Rover: A Case Study
Related PR: #183
Note to judges: I was unsure how to categorize my submission since it simultaneously brings in a new simulator engine, new assets and a new demo environment altogether. Therefore, I opted to the route of creating a new image based on a customized Dockerfile from
space_robot
image. Please note about 70 - 80 Gb of free space is require and the computer needs to have an NVIDIA GPU.Motivation
At ROSCon2023, Robotec.ai demonstrated a large warehouse fullfilment demo (short-version here) containing multiple AMRs, Cobots and human collaborators working together in a photo realistic simulation. This was achieved using the Open 3D Engine, an open-source, Apache 2.0 licensed, modular game engine that utilizes NVIDIA's open-source, Apached 2.0 licensed, PhysX 5.1 physics engine paired with the open-sourced Atom renderer. More details can be found here.
Space rovers like the Curiosity Rover, are very expensive scientific equipment that must go through extensive testing in NASA JPL's Mars Yard. These tests include endurance tests for suspensions, wheels, and mobility on uneven and unknown terrains. Additionally these rovers needs to perform critical tasks such as autonomous driving, object manipulation, path-planning in the absence of human teleportation due to the Earth-Mars communication lag.
Objective
Given the favorable nature of Open 3D Engine's licensing, rapidly developing ROS 2 support and a need for robust, accurate, scalable versatile simulator that incorporates well-understood physics libraries, my submission to this contest is a docker image whose primary purpose is to serve as a test vessel for a case study on the effectiveness, setup complexity, asset generation requirements, and challenges of using Open 3D Engine for space robotics applications, specifically a mobile manipulators like the Curiosity rover.
This image demonstrates the native integration of O3DE with the Space ROS stack by showcasing a new testing environment inspired by the Mars Yard. The picture below shows the environment with the Curiosity rover and several new assets (still a work in progress, will be finalized before September 11th Deadline).
Note the high-fidelity rendering and accurate simulation of wheel-obstacle-suspension interactions. Numerous scenarios can already be envisioned in the test environment i.e. image Curiosity rover transporting a small scientific cargo (little ROSBot) back to its twin, MAGGIE, in building 336 by maneuvering around various obstacles and environmental hazards.
My hope is that this study and demo will highlight the various advantages, benefits, and challenges in using a full 3D game engine for robotics simulations. I would like to conclude by expressing my gratitude to NASA and the Space ROS team for hosting this challenge.
Deliverables
My submission will include
RobotSim
that comes with two new new asset Gems,NasaCuriosityRoverGem
andMarsYardGem
.The text was updated successfully, but these errors were encountered: