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 must fill out the Problem Registration Kind

earlier than submitting the answer. Please discuss with the Pointers tab for extra info.

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

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 appropriate with the calls for of safety-critical area robotics functions. NASA is trying to develop the Area ROS repository with new greater constancy demonstration environments and extra capabilities.

Should you can present a helpful addition to Area ROS, you may 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 neighborhood of contributors and enhance the performance and value 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 strong framework for area robotics functions the place ROS 2 functions might be reused with little to no modification, enabling the area neighborhood to make the most of the innovation of the ROS neighborhood.

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 price of recent area robotics missions. Whereas Area ROS can be utilized by anybody working inside the area neighborhood, NASA is especially excited by additions to Area ROS that may influence future missions. For instance, enhancements to Area ROS will assist pace 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 current demos, a Curiosity Mars Rover demo and an ISS Robotic Arm (SSRMS) demo. Nonetheless, the Gazebo

simulator environments during which they’re positioned are very primary 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 could possibly be improved embrace:Making current demo or environments extra correct (examples: incorporating public supply knowledge)Making demos look extra sensible (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 at the very least 18 years outdated.   Could compete as an Particular person, Workforce, or Entity; nevertheless, the prize can be awarded in entire to the submitter (Workforce Lead).   The Workforce Lead have to be eligible to obtain fee underneath the legal guidelines of america; U.S. federal sanctions prohibit participation from sure nations. (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 total guidelines, together with Eligibility Necessities underneath the Pointers Tab

Solvers could submit a couple of resolution nevertheless the options have to be substantively totally different.Solely full submissions can be eligible for judging and prizes. Submissions should embrace full: Registration Kind, Submission Kind, 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 model information/neighborhood requirements. Every resolution ought to embrace a proof or demonstration of how the answer would possibly apply to future NASA missions. 

Area ROS Contribution Guidelines 

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

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

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

Commits

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

Pull Requests

All adjustments are integrated by way of pull requests (even adjustments by the core workforce).

All PR merges introduce a separate merge commit (i.e., git merge –no-ff), that closes the difficulty that the PR addresses, in addition to some other points which can be fastened as a aspect impact, or that may 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 difficulty.

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

All PRs have to be permitted by a maintainer. When the writer of the PR is likely one of the maintainers, a special maintainer should approve the PR.

All PRs should move the checks for the repository they’re being dedicated to.

The commit historical past have to be clear. Contributors and maintainers are advisable to rebase and squash as wanted previous to accepting a PR and merging the adjustments, in order that the commits current introduce the change onto the HEAD in an comprehensible method (slightly than describing all of the intermediate steps taken till the ultimate resolution was found).

ROS 2 Contributing Pointers

To contribute to the Area ROS and ROS 2 initiatives please discuss with the ROS 2 contributing tips (see: https://docs.ros.org/en/rolling/The-ROS2-Venture/Contributing.html

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

Area ROS Web site: https://area.ros.org/ROS Web site: https://www.ros.org/Area ROS documentation. Consists of details about Area ROS together with tutorials, how-to guides, and demos: https://space-ros.github.io/docs/rolling/index.htmlArea ROS contribution tips. All submissions should comply with the contribution guidelines: https://github.com/space-ros/space-ros/blob/most important/CONTRIBUTING.mdROS 2 Venture Documentation. This contains model information, neighborhood requirements, and technical details about ROS 2: https://docs.ros.org/en/rolling/The-ROS2-Venture/Contributing/Code-Type-Language-Variations.htmlArea ROS Demos: https://github.com/space-ros/docker/tree/most important/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