top of page

WHO WE ARE

Overview

Basically, Zero Robotics (ZR) is a programming competition where the contestants use code to solve a problem. The Interaction Zone is called the "game" of the matter, or really the atmosphere. The first round consists of 2D programming and only eliminates teams; the second begins the 3D challenge, creating a more strict deadline and following leaderboards.

Eventually the ZR Teams get thinned out through the number of points gathered over the course of the Game. The final match takes place with the SPHERES (or space robots being programmed) aboard the International Space Station (ISS).

Skills

PROGRAMMING

FLASH

ORGANIZATION

TEAM WORK

CODE INTEGRATION

Languages

The Team​

Mentors

Mr. Scott Hall & Mrs. Debbie Biggs

 

These two faculty members act as professional assets to the creation process of the Clarke ZR team. They are mainly used to pose guiding questions, a resource of reference, and (of course) a good laugh.

 

 

Team Leads

Ocie Grimsley (Info & Comm), Julia Thompson (Overall)

 

The team lead(s) is/are the person(s) who makes sure that things run smoothly. Leads answer questions, keep the team informed, track progress, and submit the final code compilation. Team leads do not have to be the official representation, they just receive updates from the ZR site and keep track of the deadlines.

 

 

Specialized Programmers

Clint Lentile & Caleb Knittle, Position Of Interests (POI) & Picture Uploading

 

​Clint is the programmer for the POIs--which will appear at 60-second intervals--responsible for the C++ code of locating POI coordinates, camera alignments, and distance from the asteroid (problem) to take the pictures.

 

Andrew Christian, Solar Flares

 

Andrew is in charge of programming the SPHERES robots to react to random solar flares throughout game time (240 sec, 4 min). He is responsible for choosing the reactions to solar flares (hiding behind the asteroid or shutting down) and tracking information about the solar flares through Game Manual updates.

 

Richard Catlett, SPHERE Movement & Momentum, Final Integration of Code

 

Richard is the programming operator that coordinates movement while on the playing field. Each team is given the responsibility to control one SPHERE to solve the provided problem. He also combines the separate pieces of code into one fluidly moving work of techy art.

 

John Ulbrich, Boundary Protection

 

The Game requires the contestants to stay within certain travel boundaries on the X-, Y-, and Z-planes of the playing area. John was the coordinator to make sure that Source Code's SPHERE was operating with non-penalizing zones.

 

Matthew Ghaffari & Dyess Harp, API & Game Manual Updates

 

Although this job SEEMS pointless, it is very important. API (Application programming interface) is how the user makes things happen in the game. Applicable to video games as well, ZR has a Manual that tells you the basics of the code, what the purpose of the game is, the point system, and other important factors of the competition. Knowing all aspects of the game is crucial to understanding the Leaderboards and the programming goal.

 

 

HTML/CSS

FRENCH

SPANISH

C0D3

Tournament Stuff
Corona SPHERES 2014-2015 Tournament Info
 

This year the question, or problem, is actually the first word "CORONA":

CONDUCTING OPTICAL RESEARCH ON NEARBY ASTEROIDS. So what does this mean? Simple: We are taking pictures of asteroids for research! And we have to code-ally find out the most efficient way to achieve that goal (answering the question).

bottom of page