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

Rewrite robotics content

Browse source
This commit is contained in:
Jake Howard 2017-02-05 15:49:59 +00:00
parent 088117e745
commit 70a0fb2ddb
7 changed files with 95 additions and 82 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

51
content/robotics/2014-index.html
View file

@ -1,37 +1,44 @@
<head>
<meta name="title" content="Student Robotics 2014">
<meta name="slug" content="2014">
z<head>
<meta name="title" content="Student Robotics 2014" />
<meta name="slug" content="2014" />
<meta name="no_container" content="true" />
<meta name="image" content="https://c2.staticflickr.com/8/7670/17115168179_1ef30ac6e9_b.jpg" />
</head>
<body>
<div class="row">
<div class="col-sm-4">
<img class="img-rounded" src="https://c2.staticflickr.com/8/7670/17115168179_1ef30ac6e9_b.jpg" />
</div>
<div class="col-sm-8">
<section>
<div class="container">
<p>
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.
</p>
</div>
</div>
<div class="row">
<div class="col-sm-8">
</section>
<section class="bg-primary">
<div class="container">
<h2>The Competition</h2>
<p>
The game for this year was called <em>Slots</em>. 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 3 cm.
The game for this year was called <em>Slots</em>. 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.
</p>
<p>
To see a copy of the rules from the competition, <a href="https://www.studentrobotics.org/resources/2014/rulebook.pdf">Click Here!</a>
</p>
</div>
<div class="col-sm-4">
<div class="list-group">
<a class="list-group-item active h4">Quick Links</a>
<a href="https://github.com/SR-CLY/2014" class="list-group-item">The Code</a>
<a href="https://www.flickr.com/photos/theorangeone/albums/72157651820386449" class="list-group-item">Gallery</a>
<a href="http://collyers-robotics14.tumblr.com/" class="list-group-item">Blog</a>
<a href="https://www.studentrobotics.org/schools/game#2014" class="list-group-item">Competition Information</a>
</div>
</div>
</section>
<section>
<div class="container text-center">
<h2 class="section-heading">Quick Links</h2>
<hr class="primary">
<a class="btn btn-primary btn-xl margin" href="https://github.com/SR-CLY/2014">
The Code
</a>
<a class="btn btn-primary btn-xl margin" href="https://www.flickr.com/photos/theorangeone/albums/72157651820386449">
Gallery
</a>
<a class="btn btn-primary btn-xl margin" href="http://collyers-robotics14.tumblr.com/">
Blog
</a>
<a class="btn btn-primary btn-xl margin" href="https://www.studentrobotics.org/schools/game#2014">
Competition Information
</a>
</div>
</section>
</body>

15
content/robotics/2015-code.md
View file

@ -4,22 +4,21 @@ html_title: The Code | SR2015
slug: 2015/code
---
The code used for this competition was by far the most complicated and advanced code that had ever been written by a Collyer's team.
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 using an entirely co-ordinate based movement system. Any input taken in from the camera was converted to co-ordinates in terms of the arena, so we could plot our movement more accurately and allow for any immovable objects such as the internal walls.
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, meaning we could allow for any imperfections in the build.
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.
There were a lot of really great features in this years code, that made our robot function much faster:
### Other features
- Position correction
- co-ordinate based movement
- Arc movement
- Distance based movement
- Pre-start calibration
- _move 'til touch_
- Camera rotation
### So, where is this code?
Unfortunately, due to the number of features, we have decided to keep the source private, so that only other Collyer's teams may access it. 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.
### 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).

52
content/robotics/2015-index.html
View file

@ -1,21 +1,19 @@
<head>
<meta name="title" content="Student Robotics 2015">
<meta name="slug" content="2015">
<meta name="title" content="Student Robotics 2015" />
<meta name="slug" content="2015" />
<meta name="no_container" content="true" />
<meta name="image" content="https://c2.staticflickr.com/8/7674/17308375182_a172a341d6_h.jpg" />
</head>
<body>
<div class="row">
<div class="col-sm-4">
<img class="img-rounded" src="https://c2.staticflickr.com/8/7726/17309695331_584e7de16c_z.jpg" />
</div>
<div class="col-sm-8">
<section>
<div class="container">
<p>
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.
</p>
</div>
</div>
<div class="row">
<div class="col-sm-8">
</section>
<section class="bg-primary">
<div class="container">
<h2>The Competition</h2>
<p>
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.
@ -27,16 +25,26 @@
To see a copy of the rules from the competition, <a href="https://www.studentrobotics.org/resources/2015/rulebook.pdf">Click Here!</a>
</p>
</div>
<div class="col-sm-4">
<div class="list-group">
<a class="list-group-item active h4">Quick Links</a>
<a href="/robotics/2015/robot/" class="list-group-item">The Robot - A.L.I.C.E</a>
<a href="/robotics/2015/code/" class="list-group-item">The Code</a>
<a href="https://flic.kr/s/aHska26DoH" class="list-group-item">Gallery</a>
<a href="http://collyersstudentrobotics.blogspot.co.uk/" class="list-group-item">Blog</a>
<a href="https://www.studentrobotics.org/schools/game#2015" class="list-group-item">Competition Information</a>
</section>
<section>
<div class="container text-center">
<h2 class="section-heading">Quick Links</h2>
<hr class="primary">
<a class="btn btn-primary btn-xl margin" href="/robotics/2015/robot/">
The Robot - A.L.I.C.E
</a>
<a class="btn btn-primary btn-xl margin" href="/robotics/2015/code/">
The Code
</a>
<a class="btn btn-primary btn-xl margin" href="https://flic.kr/s/aHska26DoH">
Gallery
</a>
<a class="btn btn-primary btn-xl margin" href="http://collyersstudentrobotics.blogspot.co.uk/">
Blog
</a>
<a class="btn btn-primary btn-xl margin" href="https://www.studentrobotics.org/schools/game#2015">
Competition Information
</a>
</div>
</div>
</div>
<div class="image-panel" data-image="https://c2.staticflickr.com/8/7674/17308375182_a172a341d6_h.jpg"></div>
</section>
</body>

39
content/robotics/2015-robot.md
View file

@ -2,45 +2,36 @@
title: The Robot - A.L.I.C.E
html_title: The Robot | SR2015
slug: 2015/robot
image: https://c2.staticflickr.com/8/7726/17309695331_584e7de16c_z.jpg
---
<div class="row">
<div class="col-sm-4">
<!-- Image of initial design (on paper) -->
</div>
<div class="col-sm-8">
<p>
Our entry for 2015, named '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 usind 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.
</p>
</div>
</div>
Our entry for 2015, named '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 usind 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.
The initial design was conceived by Ben, at kickstart, and was then refined over the coming weeks by me and 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.
Once the build was completed, it was to a much higher design and quality than I could have 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.
<div class="image-panel" data-image="https://farm1.staticflickr.com/737/20984044320_ccbba155f9_o.gif"></div>
<section class="image" data-image="https://farm1.staticflickr.com/737/20984044320_ccbba155f9_o.gif"></section>
## 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.
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.
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.
After this decisions was made, I decided to set out to find the cheesiest acronym we could 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:
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'</li>
- 'Abnormally Lame and Inaccurate Control-less Engine'</li>
- 'Anti-Losing Immaculate Competitive Extravaganza'</li>
- _'Automated Laser-cut Interactive Capturing Entity'_
- _'Abnormally Lame and Inaccurate Control-less Engine'_
- _'Anti-Losing Immaculate Competitive Extravaganza'_
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. In the end we decided to go with one that Sam initially suggested, so 'ALICE' officially stands for:
But the one we went with was:
<h3 class="text-center">'Autonomous Logistics and Inevitable Collision Engine'</h3>
### _'Autonomous Logistics and Inevitable Collision Engine'_
<div class="image-panel" data-image="https://c2.staticflickr.com/8/7656/16687742984_ee1c76d1d9_h.jpg"></div>
<section class="image" data-image="https://c2.staticflickr.com/8/7656/16687742984_ee1c76d1d9_h.jpg"></section>

1
theme/static/src/scss/homepage.scss
View file

@ -1,5 +1,4 @@
header {
background-image: url("../img/header.jpg");
min-height: 100%;
h1 {

5
theme/static/src/scss/index.scss
View file

@ -46,6 +46,11 @@ p a {
background-size: cover;
}
section.image {
height: 55vh;
background-attachment: fixed;
}
.container > img,
.container p > img,
.row > div > img {

4
theme/templates/article.html
View file

@ -10,9 +10,13 @@
{% block content %}
{% include 'extras/header.html' with instance=article %}
{% if not article.no_container %}
<section>
<div class="container">
{{ article.content }}
</div>
</section>
{% else %}
{{ article.content }}
{% endif %}
{% endblock %}