We are also using OpenEmbedded to create the Linux distribution for the UAV’s operating system. OpenEmbedded creates a manifest file that lists all of the packages installed into the Linux distro and helps navigate how the packages are licensed. This information will help you to determine how elements of your proprietary code can interface with the system.
The DARPA Hackfest event organizers will be providing data samples of the control link as examples.
Specializing around a set frequency should not be considered a large part of the problem. We will release the spectrum information once NASA has provided it.
The specific spectrum allocation for the Hackfest activities will be made known to the Hackfest teams, and then we will partition that spectrum between the teams. Spectrum jamming and interference by other teams is not permitted and not part of the Hackfest mission. The DARPA organizers will monitor the spectrum during flight tests to verify this. Any team caught purposefully interfering with or jamming the systems of another team will be disqualified.
The second reason that DARPA is running the Hackfest is to engage in a community of smart, talented, energetic, and creative people with whom we might not have interacted before or even be aware of. DARPA is excited about expanding technological opportunities and developing new ways of tackling problems by offering catalytic events and projects that will energize the diverse talent pool out there, especially parts of that pool that have yet to work with DARPA.
At the end of the Hackfest, we hope to see new solutions to problems, better use and development of tools that expand the capabilities of everyone, and the buildup of new relationships with parts of the science, engineering, and technology community that we have not interacted with before.
Traditionally, research organizations and companies get DARPA’s attention by responding with a whitepaper to an official request for information (RFI) or by submitting a proposal to newly announced programs. The Hackfest provides a different channel for connection: at the end of the Hackfest, teams will demonstrate their work in a review session with a number of program managers from different technical offices within DARPA. During review session, teams will have the chance to both talk about their ideas and provide live demonstrations of their work. Teams should think about the demonstrations at the end of the week as an informal, live proposal of their technology and solutions in lieu of a whitepaper.
After the Hackfest, those teams that have presented compelling solutions and want to engage with DARPA farther can consider several approaches. One possibility would be to propose a seed-level study that would probe the potential for an idea or technology to become the basis for bigger programs and/or to help further some existing DARPA effort. Any follow-on support from DARPA from this Hackfest most likely would be in that context. To help open the way to a DARPA collaboration for companies and research institutions that have not had any or much interaction with the Agency, DARPA Microsystems Technology Office (MTO) also recently issued a Commercial Performer Program Announcement (DARPA-PA-17-01) that provides a new work agreement framework. During the review sessions, teams will be welcome to discuss with the DARPA organizers other possible frameworks for collaborating with DARPA.