-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NASA_Challenge_[Barisyaz]_[Ingenuity Flight Simulator] #39
base: main
Are you sure you want to change the base?
NASA_Challenge_[Barisyaz]_[Ingenuity Flight Simulator] #39
Conversation
6631108
to
8d4aa7d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the submission, this looks very cool! However, I need you to follow our contribution guidelines and open a new issue for this demo (using our feature request template). Then update both the PR title and the commit message(s) to refer to that issue #. We require every commit to have an associated issue. Also, I've added a workflow to build the build.sh
files automatically, so this must build successfully using your script.
Thank you for your feedback. I will update the PR based on your comments. I have some questions and suggestions: Feature SeparationI have implemented multiple features in this PR:
Would it make sense to separate these into individual issues and reference them in separate commits? Build Script and Docker ImageRegarding the build script, there's a potential issue with the current workflow. My script relies ‘openrobotics/space_robots_demo’ that comes as an artifact from the docker repo under the space-ros project. To address this, I have two questions:
|
Yes, please use the
There's no current plan to do that. For now, you can copy that folder into your workspace and build it. In fact, can you have your build script do that at build time for now? We plan to port that folder into this repo soon anyway, then we can update the build script. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for adding the build.sh
. This still needs a full review but I'm going to try to run the CI.
Okay I will update it with space-ros docker image. I haven’t pushed anything new yet. Could you also tell me if I should open multiple issues for multiple features or one issue listing multiple features? |
According to @mkhansenbot comment in #39 (comment)
|
8d4aa7d
to
72b8d8e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for your submission, however this doesn't build in our CI, because you're relying on the 'space_robots' docker image, which you're not building. So there are two options:
- build on the space-ros:latest image only, pull in any assets you need from the space-ros/simulation repo
- Implement a multi-stage build where you first build the
space_robots
image then you build yours on top of that
I recommend option 1 if possible, as the space_robots demo will be refactored and moved into this repo later, so it's preferable to remove that dependency if you can
…nd control fix: docker container support
11373e3
to
2310827
Compare
Thanks @mkhansenbot for the update. I updated the dockerfile to be based on space-ros public image and the build script. Workflow should hopefully work now. |
Re-running the build |
source /home/spaceros-user/spaceros/install/setup.sh | ||
source /opt/ros/humble/setup.sh | ||
cd /home/spaceros-user/ingenuity_helicopter | ||
colcon build --packages-select helicopter_flight_control helicopter_flight_simulation ingenuity_description ingenuity_bringup |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please move the colcon build
into the Dockerfile so that we can ensure the build works correctly using CI
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I updated the Dockerfile with the colcon build command. Also adjusted the entrypoint.sh such that it directly start the launch file.
This still needs a full code review
This project simulates the Ingenuity Mars Helicopter using Gazebo and ROS 2 in Space-ROS.
closes #67
Aim of this project is to develop tools to mimic the Martian environment as close as possible. This enables space robots to easily iterate over the development cycles. This is important especially for the aerial vehicles. Because the air is much thinner and the nature events are different. Having this in mind, I develop the Ingenuity Flight Simulator, calculating the lift and drag forces as close to the Martian atmosphere and gravity as possible. This could enable Nasa engineers to develop controllers that can react to the nature events or test flight controllers with sensor noise such as IMU, altimeter or Camera.
landing_e27e4Hjz.mp4
cyclic_Bx2v4jKU.mp4
dust-storm-collective_q6O5PUg9.mp4