NASA Challenge_[@minahilrz]_[JAXA RACS2 Bridge Demo] (Closes space-ros#26)

[MinahilRaza]

Closes: Issue #26

Submission Title: JAXA RACS2 Bridge Demo

• Challenge Name: NASA Space ROS Sim Summer Sprint Challenge
• Team Lead Freelancer Username: minahilrz

This PR features an integration of the RACS2 (ROS and cFS System 2) Bridge by Japan Aerospace Exploration Agency (JAXA) with SpaceROS. This bridge provides a way to bridge message communication between Robot Operating System 2 (ROS2) nodes and core flight executives (cFE). cFE is a core component of NASA-supplied spacecraft software, Core Flight System (CFS).

This demo includes:

• • jaxa_comm_spaceros: A ROS2 package for communication over the bridge. This ROS2 package allows spawning listener nodes to receive messages over the RACS2 Bridge.
• racs2_msg: A ROS2 package containing message definitions for communication between ROS2 and cFS.
• cFS_app_examples: Example apps for cFS.
• Dockerfiles: to support docker based development and reproducibility.
• Scripts: to build and run the demo

This demo builds two docker container which communicate with each other as shown in the architecture diagram below:

Moreover, the demo can be used with the space robots demo as explained in the examples.

[MinahilRaza]

In the CI workflow definition, the build.sh file is run from the root folder of the repo. Wouldn't it make sense to first cd to the subfolder containing build.sh and execute it from there (similar to how the docker repo runs it)?

[Bckempa]

In the CI workflow definition, the build.sh file is run from the root folder of the repo. Wouldn't it make sense to first cd to the subfolder containing build.sh and execute it from there (similar to how the docker repo runs it)?

@mkhansenbot this seems to be a question about #37, care to take a look?

[mkhansenbot]

@MinahilRaza - I just changed the build workflow to cd into the folder first, then rebased your branch

[MinahilRaza]

Thanks for the help!

[ivanperez-keera]

@MinahilRaza Thanks again for submitting this.

The JAXA team submitted and merged a solution for this. Is there something from your PR that might still make sense to merge? Perhaps something that could be improved about their solution based on what you submitted?