Remove unnecessary robotics section

content/robotics/_index.md

@@ -1,3 +0,0 @@
----
-title: Robotics
----

content/robotics/smallpeice/2017/_index.md

@@ -1,12 +0,0 @@
----
-title: Smallpeice 2017
-image: https://farm5.staticflickr.com/4426/35552704294_5aa52e2ed6_k_d.jpg
-linkTitle: 2017
-date: 2017-08-05
----
-
-Smallpeice 2017 was my first experience into the realm of Smallpeice's [_Computing and Micro Electronics_](https://www.smallpeicetrust.org.uk/courses/computing-and-microelectronics/) course. This took place between the 29th July and 5th August, for me. The students were only around 31st to 4th.
-
-## The Game 
-
-This year, teams competed in a game called _Tin Can Rally_, a take on a previous [Student Robotics](/robotics/student-robotics) game. Teams had to get around the arena circuit as many times as possible. Each time they passed a quarter marker, they gained a point. If they were carrying one of the 6 tokens in the arena when crossing the line, they would gain an additional point for each. The game was also shorter than standard SR games, at only 2 minutes.   

content/robotics/smallpeice/2018/_index.md

@@ -1,5 +0,0 @@
----
-title: Smallpeice 2018
-linkTitle: 2018
-date: 2018-08-11
----

content/robotics/smallpeice/_index.md

@@ -1,5 +0,0 @@
----
-title: Smallpeice
----
-
-[Smallpeice](https://www.smallpeicetrust.org.uk/courses/computing-and-microelectronics/) is competition in a very similar format to that of [Student Robotics]({{< relref "../student-robotics" >}}), but run by the [Smallpeice Trust](https://www.smallpeicetrust.org.uk/) and the [University of Southampton](https://www.southampton.ac.uk/). Rather than being run over 6 months like Student Robotics, Smallpeice is run over just 5 days.

content/robotics/student-robotics/2014/_index.md

@@ -1,12 +0,0 @@
----
-title: Student Robotics 2014
-linktitle: 2014
-image: https://c2.staticflickr.com/8/7670/17115168179_1ef30ac6e9_b.jpg
----
-## The Competition
-
-The game for this year was called _Slots_. Teams competed 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 3 centimetres.
-
-To see a copy of the rules from the competition, [Click Here](https://web.archive.org/web/20160303205015/https://www.studentrobotics.org/resources/2014/rulebook.pdf)!
-
-{{% youtube DL0iLDzHKig %}}

content/robotics/student-robotics/2014/code.md

@@ -1,8 +0,0 @@
----
-title: Code
-repo: SR-CLY/2014
----
-
-2014 is one of the only years in which we released the [full source code](https://github.com/SR-CLY/2014) for our robot, to our [GitHub organisation](https://github.com/SR-CLY/).
-
-{{% repobutton %}}

content/robotics/student-robotics/2014/videos.md

@@ -1,10 +0,0 @@
----
-title: Videos
-image: https://c2.staticflickr.com/8/7670/17115168179_1ef30ac6e9_b.jpg
----
-
-{{< youtube Lravftv_qLI >}}
-
-{{< youtube DL0iLDzHKig >}}
-
-{{< youtube TS-6Cbxr3UQ >}}

content/robotics/student-robotics/2015/_index.md

@@ -1,14 +0,0 @@
----
-title: Student Robotics 2015
-linktitle: 2015
-image: https://farm9.staticflickr.com/8700/17404219256_a9ba1ac510_o_d.jpg
----
-
-## The competition
-As was announced at kickstart, the game for this year is a take on the classic game mode 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 25 centimetres cubes of wood on caster wheels weighing roughly 2 kilograms. 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://web.archive.org/web/20160303205015/https://www.studentrobotics.org/resources/2015/rulebook.pdf)!
-
-{{% youtube egV3PY1qaSM %}}

content/robotics/student-robotics/2015/code.md

@@ -1,19 +0,0 @@
----
-title: Code
----
-
-The code used for this competition was by far the most complicated and advanced code ever written by a team of ours.
-
-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.

content/robotics/student-robotics/2015/robot.md

@@ -1,31 +0,0 @@
----
-title: Robot
-image: https://c2.staticflickr.com/8/7726/17309695331_584e7de16c_z.jpg
----
-
-Our entry for 2015, _A.L.I.C.E_, 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'_

content/robotics/student-robotics/2015/videos.md

@@ -1,7 +0,0 @@
----
-title: Videos
----
-
-{{% youtube egV3PY1qaSM %}}
-
-{{% youtube avdhF4sBYV8 %}}

content/robotics/student-robotics/_index.md

@@ -1,12 +0,0 @@
----
-title: Student Robotics
-image: https://c2.staticflickr.com/8/7674/17308375182_a172a341d6_h.jpg
----
-
-[Student Robotics](https://studentrobotics.org) is the the place where my development knowledge really started to grow. Thanks to the other people in my team teaching me. I had never done anything robotics related, and so when my computing teacher initially told us about it, I wasn't really interested. After I found out that my friend was also doing it, I signed up, and went along to the kickstart. From then on I was hooked, getting involved with all aspects of the development and design, as well as helping out other teams on the IRC room.
-
-## My Entries
-Being at college for 2 years, meant I was able to enter 2 years of competitions, [SR14]({{< ref "2014" >}}), and [SR15]({{< ref "2015" >}}). We were encouraged to gain an online presence for our team, so I created a basic web page for both years. The original pages have been lost, but the content is all still there.
-
-### Post 2015
-Unfortunately, after I left college, I also left behind the ability to enter Student Robotics as a competitor. Fortunately however, [they're always looking for volunteers](https://studentrobotics.org/volunteer/) to help run the competition itself, as a _Blue Shirt_.