NASA Area ROS Sim Summer season Dash Problem – sUAS Information

Assist make the Area Robotic Working System (ROS) extra strong and help NASA’s plan for future missions by including to the repository.

Solvers have to fill out the Problem Registration Type

earlier than submitting the answer. Please seek advice from the Pointers tab for extra data.

We’re internet hosting a webinar on August 7 @ 2:00 PM ET. Be sure to register right here to listen to straight from NASA, Area ROS, and Freelancer group! 

Extra particulars concerning the webinar is offered within the Updates tab.

Area ROS

is an open-source software program framework, derived from ROS 2

, which was created to be suitable with the calls for of safety-critical area robotics purposes. NASA is seeking to develop the Area ROS repository with new greater constancy demonstration environments and extra capabilities.

In the event you can present a helpful addition to Area ROS, you would be eligible for a share of the $30,000 US prize purse.

The Area ROS undertaking began with a joint settlement between the non-public area business and NASA (see: https://space-ros.github.io/docs/rolling/Introduction.html

). Area ROS is meant to be an open, community-driven effort. Via this Problem, NASA hopes to develop the group of contributors and enhance the performance and usefulness of Area ROS.

Utilizing the ROS 2 Humble distribution as a basis, Area ROS is designed to be platform impartial, moveable, and undertaking impartial. Area ROS is turning into a sturdy framework for area robotics purposes the place ROS 2 purposes may be reused with little to no modification, enabling the area group to make the most of the innovation of the ROS group.

Constructing out Area ROS capabilities can shorten the time for growth of novel area robotics capabilities, allow reuse of capabilities between missions, and decrease the life-cycle value of recent area robotics missions. Whereas Area ROS can be utilized by anybody working inside the area group, NASA is especially involved in additions to Area ROS that may affect future missions. For instance, enhancements to Area ROS will assist velocity testing and growth of the brand new robotic applied sciences wanted for NASA’s future Lunar missions as a part of its Artemis program.

Area ROS presently has two present demos, a Curiosity Mars Rover demo and an ISS Robotic Arm (SSRMS) demo. Nonetheless, the Gazebo

simulator environments through which they’re positioned are very fundamental and the capabilities these demos present are minimal. Increasing these demos to incorporate greater constancy environments would higher present the ideas and advantages of utilizing the Area ROS.Some examples of how the Area ROS might be improved embrace:Making present demo or environments extra correct (examples: incorporating public supply knowledge)Making demos look extra reasonable (examples: including higher lighting or mannequin constancy)Serving to robots carry out duties higher (examples: conducting scientific experiments or useful resource allocation)Including new, related demos or environmentsAdding new options, capabilities, integrations, or interfaces

Have to be a minimum of 18 years outdated.   Might compete as an Particular person, Staff, or Entity; nevertheless, the prize will likely be awarded in complete to the submitter (Staff Lead).   The Staff Lead should be eligible to obtain fee underneath the legal guidelines of the USA; U.S. federal sanctions prohibit participation from sure international locations. (see: https://ofac.treasury.gov/sanctions-programs-and-country-information).Options should originate from both the U.S. or a chosen nation (see definition of designated nation at https://www.acquisition.gov/far/part-25#FAR_25_003).

See the complete guidelines, together with Eligibility Necessities underneath the Pointers Tab

Solvers might submit multiple answer nevertheless the options should be substantively totally different.Solely full submissions will likely be eligible for judging and prizes. Submissions should embrace full: Registration Type, Submission Type, Visuals (screenshots or video), and code submission to the Area ROS Repository.All options should conform to the Area ROS contribution guidelines.All options should conform to the ROS fashion information/group requirements. Every answer ought to embrace an evidence or demonstration of how the answer may apply to future NASA missions. 

Area ROS Contribution Guidelines 

https://github.com/space-ros/space-ros/blob/essential/CONTRIBUTING.md

The next subsections deal with learn how to contribute to the Area ROS undertaking.

All Solvers ought to observe these guidelines when submitting contributions to the Area ROS. These guidelines have been designed to simplify the method of creating compliance with necessities of area software program.

Commits

All commits should reference the problem they deal with. A consequence of that is that no commits may be made until there’s a corresponding problem for them.Word: for this competitors, reference “NASA Area ROS Sim Summer season Dash Problem” as the problem. 

Pull Requests

All modifications are integrated by way of pull requests (even modifications by the core group).

All PR merges introduce a separate merge commit (i.e., git merge –no-ff), that closes the problem that the PR addresses, in addition to every other points which are mounted as a facet impact, or that may now not be reproduced after the change. The commit makes use of the syntax “Closes#”, “Repair#” or a command supported by github to mechanically shut the problem.

There’ll be a choice for PRs to deal with just one problem at a time, however we’ll be versatile particularly for circumstances through which a repair addresses a number of associated points on the identical time (see level above).

All PRs should be accepted by a maintainer. When the writer of the PR is likely one of the maintainers, a unique maintainer should approve the PR.

All PRs should go the exams for the repository they’re being dedicated to.

The commit historical past should be clear. Contributors and maintainers are beneficial to rebase and squash as wanted previous to accepting a PR and merging the modifications, in order that the commits current learn how to introduce the change onto the HEAD in an comprehensible approach (reasonably than describing all of the intermediate steps taken till the ultimate answer was found).

ROS 2 Contributing Pointers

To contribute to the Area ROS and ROS 2 tasks please seek advice from the ROS 2 contributing pointers (see: https://docs.ros.org/en/rolling/The-ROS2-Mission/Contributing.html

)Developer Informationhttps://docs.ros.org/en/rolling/The-ROS2-Mission/Contributing/Developer-Information.html

Area ROS Web site: https://area.ros.org/ROS Web site: https://www.ros.org/Area ROS documentation. Contains details about Area ROS together with tutorials, how-to guides, and demos: https://space-ros.github.io/docs/rolling/index.htmlArea ROS contribution pointers. All submissions should observe the contribution guidelines: https://github.com/space-ros/space-ros/blob/essential/CONTRIBUTING.mdROS 2 Mission Documentation. This contains fashion information, group requirements, and technical details about ROS 2: https://docs.ros.org/en/rolling/The-ROS2-Mission/Contributing/Code-Model-Language-Variations.htmlArea ROS Demos: https://github.com/space-ros/docker/tree/essential/space_robotsNASA Moon to Mars Structure Definition Doc: https://www.nasa.gov/wp-content/uploads/2024/01/rev-a-acr23-esdmd-001-m2madd.pdfNASA Artemis Missions: https://www.nasa.gov/humans-in-space/artemis/

Q&A Tracker

 – hyperlink