Kacper/HowToBuildACommonsWorkbooks
1
0
Fork 0
forked from How_to_Build_a_Commons/HowToBuildACommonsWorkbooks
Code Issues Pull requests Projects Releases Packages Wiki Activity

Update ZenCompetition.tex

Browse source
This commit is contained in:
Kevin Harrington 2025-08-01 11:26:53 -04:00 • committed by GitHub
parent 397322053b
commit 77a617a108
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 19 additions and 18 deletions
Download patch file Download diff file Expand all files Collapse all files

35
ZenCompetition.tex
View file

@ -37,23 +37,6 @@ This pentathlon is designed to foster a connection to these principles for each
\pagebreak
{\huge \textbf{Justification of Decisions}}
\vspace{1cm}
This competition was inspired as an act of schismogenesis in response to FIRST and Vex competitions. The competition structure, team-on-team competition and my-win-requires-your-loss aspects are the motivations for a change. There are elements that are desirable, such as team collaboration, across-team collaboration and high school engineering.
Why Linux as the runtime?
\begin{enumerate}
\item We want to encourage full-scale compute hardware as the runtime for robot programs.
\item We want to see tight integration of Control Code, Robot Kinematics, Robot CAD and Robot Simulation.
\item We want to see fully open source designs that can be composites of many repositories, with runtime self-bootstrapping on new systems.
\item We want to have students able to open up the robot in an Integrated Robotics Development Environment.
\item We want to encourage a distributed architecture of compute and edge devices.
\end{enumerate}
\pagebreak
@ -212,8 +195,26 @@ Each team in the competition must perform some portion of the obstacle course to
\vspace{1cm}
\pagebreak
{\huge \textbf{Appendix}}
\pagebreak
{\huge \textbf{Justification of Decisions}}
\vspace{1cm}
This competition was inspired as an act of schismogenesis in response to FIRST and Vex competitions. The competition structure, team-on-team competition and my-win-requires-your-loss aspects are the motivations for a change. There are elements that are desirable, such as team collaboration, across-team collaboration and high school engineering.
Why Linux as the runtime?
\begin{enumerate}
\item We want to encourage full-scale compute hardware as the runtime for robot programs.
\item We want to see tight integration of Control Code, Robot Kinematics, Robot CAD and Robot Simulation.
\item We want to see fully open source designs that can be composites of many repositories, with runtime self-bootstrapping on new systems.
\item We want to have students able to open up the robot in an Integrated Robotics Development Environment.
\item We want to encourage a distributed architecture of compute and edge devices.
\end{document}