Design Scoring
To reward teams for their creativity, technical skill, and hard work, we will be judging several design categories. This section breaks down how your team can earn points for your base station, codebase, and drone construction.
Total Possible Design Score: 22 Points
| Category | Maximum Points |
|---|---|
| Look & Feel of Base Station App | 6 Points |
| Codebase | 8 Points |
| Drone Construction | 8 Points |
| Total | 22 Points |
Base Station App Look & Feel (6 Points)
This category scores the user interface (UI) and user experience (UX) of your base station application. The goal is a control interface that is not only functional but also intuitive and easy to use under pressure.
| Score | Criteria |
|---|---|
| Excellent (5-6 Points) | The app is intuitive, responsive, and visually polished. Information is presented clearly and logically, or it effectively follows a theme. A new user could understand its basic functions with little to no instruction. |
| Good (3-4 Points) | The app is functional and gets the job done. It may have some minor layout issues, be slightly confusing to navigate, or lack visual polish. |
| Needs Improvement (1-2 Points) | The app is difficult to use, cluttered, or unresponsive. Key information is hard to find or understand. There is little to no styling. |
Codebase (8 Points)
Your team's codebase will be evaluated on its organization, originality, efficiency, and use of source control. It should demonstrate good programming practices and reflect the team's unique work.
You will receive 0 points for the entire Codebase category if you do not submit your code before the deadline. If you need an extension, you must request one from competition organizers. You can see the current competition deadlines on the front page of the docs at all times.
| Category | Max Points | Excellent | Good | Needs Improvement |
|---|---|---|---|---|
| Codebase Organization | 2 Points | The codebase is well-structured, easy to navigate, and follows the best practices outlined in the Getting Started guide. | The code has some structure, but files may be disorganized or named confusingly. | Code is in a single file or has no clear organizational structure. |
| Code Originality | 3 Points | Code shows significant student-authored logic and problem-solving beyond the provided examples. | Code is a functional modification of the examples, but relies heavily on the original structure. | Code is a direct copy of the provided examples with minimal changes. |
| Code Elegance | 1 Point | Code is clean, efficient, and easy to read. It solves problems in a direct and clever way, and applies existing libraries and utilities effectively to problems. | The code is functional, but may be inefficient or difficult to follow. | The code does not consistently function, or functions with frequent errors or warnings. |
| Good Use of Source Control | 2 Points | The git history shows frequent, well-described commits. | Commits are infrequent, or have vague descriptions. | The repository has only one or two commits with large amounts of code. |
How to Submit Your Codebase
You can submit your code in one of two ways:
- GitHub: Publish your code in a public GitHub repository and send us the link.
- ZIP File: Send a complete ZIP file of your project, making sure to include the
.gitfolder so we can review your commit history.
Please contact competition administrators via Discord or email if you need any support with your submission. You do not need to resubmit your code if you make changes after the deadline.
For more information, see the corresponding section in the Rules and Laws page.
Drone Construction (8 Points)
This category scores the physical design and build quality of your drone. Judges will look for a blend of creative expression and smart, robust engineering.
| Category | Max Points | Excellent | Good | Needs Improvement |
|---|---|---|---|---|
| Artistic Expression | 3 Points | The drone has a highly creative, well-executed, and unique theme or design. The customization is neat and clearly intentional. | The drone has some custom decorations or a theme, but it may be simple or not fully realized. | The drone is the stock build with no artistic modifications. |
| Intelligent Engineering | 5 Points | Components (like sensors and payload mechanisms) are mounted securely and thoughtfully. The design is robust, and wiring is managed cleanly. The drone is well-balanced and shows careful planning. | Components are functional and attached, but the implementation may be simple (e.g., lots of electrical tape). Wiring may be messy, or mounts may seem like an afterthought. | Components are insecurely attached, dangle loosely, or are placed in a way that could impede flight or safety. |