How_to_Build_a_Commons/HowToBuildACommonsWorkbooks
2
0
Fork 1
mirror of https://github.com/How-To-Build-a-Commons/HowToBuildACommonsWorkbooks.git synced 2026-04-19 16:51:04 +00:00
Code Issues Projects 1 Releases Packages Activity

adding a software section

Browse source
This commit is contained in:
Kevin Harrington 2023-12-29 18:26:29 -05:00
parent 508112f5ba
commit 212497f35b
1 changed files with 15 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

22
ZenCompetition.tex
View file

@ -47,9 +47,9 @@ Students will compete in independent categories for:
\item time of completion
\item design contribution
\item mechanical design contribution
\item code contribution
\item code design contribution
\item build quality, adornment and animation
\end{enumerate}
@ -86,16 +86,17 @@ Students will compete in independent categories for:
\item \textbf{Performance:} Before proceeding into the obstacle course, the robot will be judged on a 90 second animation intended to hype up the crowd. At each save-point through the course another 90 second animation will be required.
\item \textbf{Eligibility:} High school and Jr High school students affiliated with public schools or not for profit organizations.
\end{enumerate}
\pagebreak
{\huge \textbf{Competition structure}}
The competition will be held over the same weekend by all teems wishing to compete.
The competition will be held over the same weekend by all teams wishing to compete.
Teams will register with the completion central ranking server and may submit early if they so choose. Early submissions with novel code elements may be picked up by other teams, increasing the likelihood the team that posts early gets recognition for design contributions award.
All teams that compete in the code portion must have at least on hardware submission. Multiple code teams may use a single hardware entry. A code entry may be used on more than one hardware entry.
All teams that compete in the code portion must have at least one hardware submission. Multiple code teams may use a single hardware entry. A code entry may be used on more than one hardware entry.
Hardware only teams may compete for the design award. They must demonstrate that the design works with an existing software release, or that they have developed and released a working software stack by performing well in the obstacle course.
@ -105,13 +106,20 @@ All teams that wish to compete for top prizes must compete over the competition
Competition consists of the judges running the tagged code against the student provided robot, connected to the judges station's network. The judge will run the tagged code in a standard execution environment. Students code must work as a self contained system, or bootstrap components as they are needed. Judges station will have access to the internet during practice run to ensure bootstrapping. Student downloads are limited to 8gb of total used disk space. The student provided software will have a competition.groovy file that will perform then entire task of animation, course navigation and stopping at the end to press the button. Animation audio will play through the station computer.
Each team in the competition must perform some portion of the obstacle course to be counted for judging. All runs of the course are recorded for the instant runnoff judging. Judging for objective measures such ad distance and timme will be judged instantly. Performance and design contribution judging will be performed over the following weeks. Finalists will be invited to submit a new animation for second round judging at a central event. The finalists will be judged and awarded at that time.
Each team in the competition must perform some portion of the obstacle course to be counted for judging. All runs of the course are recorded for the instant runoff judging. Judging for objective measures such ad distance and time will be judged instantly. Performance and design contribution judging will be performed over the following weeks. Finalists will be invited to submit a new animation for second round judging at a central event. The finalists will be judged and awarded at that time.
\pagebreak
{\huge \textbf{Software}}
\textbf{Competition Runtime:} The competition runtime is BowlerStudio. Student code will consist of a BowlerStudio launcher script that performs the entire course without further human interaction. The competition runtime computer will be Ubuntu LTS on x86\_64 processor with 32gb of ram. The competition station will be connected to a WiFi station. The robot will be connected to the same WIFi station.
\textbf{Libraries:} Code and design libraries can be kept as BowlerStudio Groovy scripts, or they my be distributed on Maven. Teams are expected to provide authorship of all libraries used within a submission.
\textbf{Design tools:} IDE's, CAD packages, Simulation tools, project planning and any other necessary piece of software used in the process of planning, design, or production of a submission must also be open source. BowlerStudio, FreeCAD, Blender, OpenSCAD, Inkscape are examples of CAD design tools that would be acceptable. Web based tools do not count.
\end{enumerate}
\vspace{1cm}