archive/theorangeone.net-legacy
1
Fork 0
Code Activity

Merge SR2015 pages

Browse source
This commit is contained in:
Jake Howard 2017-05-13 21:33:34 +01:00
parent 4530917469
commit fdf27d0cdc
3 changed files with 33 additions and 42 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

37
content/robotics/2015/robot.md → content/robotics/2015.md
View file

@ -1,9 +1,38 @@
---
title: The Robot - A.L.I.C.E
show_in_nav: false
image: https://c2.staticflickr.com/8/7726/17309695331_584e7de16c_z.jpg
title: Student Robotics 2015
linktitle: 2015
image: https://c2.staticflickr.com/8/7726/17309695331_584e7de16c_b.jpg
---
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)!
## The code
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.
## The Robot
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.
@ -12,7 +41,7 @@ The initial design was conceived by Ben, at kickstart, and was then refined over
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_?
### 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.

23
content/robotics/2015/code.md
View file

@ -1,23 +0,0 @@
---
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).

15
content/robotics/2015/index.md
View file

@ -1,15 +0,0 @@
---
title: Student Robotics 2015
linktitle: 2015
slug: /
image: https://c2.staticflickr.com/8/7726/17309695331_584e7de16c_b.jpg
---
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)!