Add robotics content

content/robotics/2014.md

@@ -0,0 +1,11 @@
+---
+title: Student Robotics 2014
+---
+
+Welcome to the homepage of Collyer's Student Robotics 2014 team. Originally, this page was a part of the competition, but due to 3 different site rewrites, the original content and formatting has been lost.
+
+## The Competition
+
+The game for this year was called _Slots_. Teams compeated to get as many of their tokens into a scoring zone in 3 minutes. Teams would also get extra points if they could get the token into a zones 'slot', an area the size of a token, raised by around 3cm.
+
+To see a copy of the rules from the competition, [Click Here](https://www.studentrobotics.org/resources/2014/rulebook.pdf)!

content/robotics/2015/code.md

@@ -0,0 +1,23 @@
+---
+title: The Code
+show_in_nav: false
+---
+
+The code used for this competition was by far the most complicated and advanced code ever written by a Collyer's team.
+
+The main change between any other year was a co-ordinate based movement system. Any input taken in from the camera was converted to co-ordinates, so we could plot our movement more accurately and allow for any immovable objects such as the internal walls.
+
+The addition of this coordinate system allowed us to create the killer feature of this year, the position correction code. This code allowed us to automatically correct our position after we scanned for a marker, so we could allow for the motors not moving us exact distances.
+
+### Other features
+
+- Arc movement
+- Distance based movement
+- Pre-start calibration
+- _move 'til touch_
+- Camera rotation
+
+### So, where is it?
+Unfortunately, due to the number of features, we have decided to keep the source internal. A lot of blood, sweat and tears (not literally) went into writing this code, and it would be a shame if that were to be used to help any of our opponents.
+
+You can however see the code from some of our other years on our [GitHub organisation](https://github.com/SR-CLY).

content/robotics/2015/index.md

@@ -0,0 +1,13 @@
+---
+title: Student Robotics 2015
+slug: /
+---
+
+Welcome to the homepage of Collyer's Student Robotics Team 2015 (The 'A' Team) - Creators of 'A.L.I.C.E'! Here you can see everything that goes on throughout the competition.
+
+## The competition
+As was announced at kickstart, the game for this year is a take on the classic gamemode Capture the Flag. 4 teams compete over 5 flags to move as many of them as they can into their scoring zones. The person with the most flags in their scoring zone wins.
+
+The 'flags' are 25cm cubes of wood on caster wheels weighing roughly 2kg. The rules prevent us from lifting them, so the idea is to drag them around!
+
+To see a copy of the rules from the competition, [Click Here](https://www.studentrobotics.org/resources/2015/rulebook.pdf)!

content/robotics/2015/robot.md

@@ -0,0 +1,32 @@
+---
+title: The Robot - A.L.I.C.E
+show_in_nav: false
+image: https://c2.staticflickr.com/8/7726/17309695331_584e7de16c_z.jpg
+---
+
+Our entry for 2015, _Alice_, was a massive improvement over last years model, in both design, and the code for it. Before ALICE was built, the design team built us a very basic chassis using scrap parts from 2014, which allowed us to write a large amount of the code base before we even had the robot built. Originally I wanted the final chassis to be built before the end of January, so we had a lot of time to test out the design for the robot and test using the final, in reality, it was closer to the middle of march before this was a reality.
+
+The entire chassis was made from sheets of plywood, which we laser cut in college, allowing us to be very precise in the design of the robot to make sure that all the pieces would fit together properly, making the chassis less likely to break.
+
+The initial design was conceived by Ben, at kickstart, and was then refined over the coming weeks the rest of the building team. This was made much easier from the use of the 3D model, that Ben made, which helped us visualize any changes that were to be made, as well as work out strategy by seeing the measurements we had to work with.
+
+Once the build was completed, it was to a much higher design and quality than I could've ever imagined! It allowed us to forget about any shortcomings when it came to chassis, not having to compensate for weight distribution, or worry about the grip on the wheels, as we had to do last year.
+
+## Why call it _A.L.I.C.E_?
+The decision to name the robot 'Alice' was a decision made by the whole group!
+
+That's a lie.
+
+Ben suggested it and as no one had any better ideas and because he gets overruling vote on this, for some reason , it stuck.
+
+One idea was also suggested that we name the robot after the first sponsor we got, but as we didn't get one until after the team split, the other team took that name instead.
+
+I decided to try to find the cheesiest acronym for 'Alice', to make the name slightly more interesting, and not some random girls name pulled from thin air on the bus ride home from kickstart. There were a few rather good ideas, most of them coming from Sam:
+
+- _'Automated Laser-cut Interactive Capturing Entity'_
+- _'Abnormally Lame and Inaccurate Control-less Engine'_
+- _'Anti-Losing Immaculate Competitive Extravaganza'_
+
+But the one we went with was:
+
+### _'Autonomous Logistics and Inevitable Collision Engine'_