You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: programming/sr/vision/markers.md
+16-20Lines changed: 16 additions & 20 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,23 +6,19 @@ title: Markers
6
6
Markers
7
7
=======
8
8
9
-
<imgsrc="{{ site.baseurl }}/images/content/marker-0.png"alt="An Example Marker: Arena marker 0"class="right" />
10
-
An example *libkoki* marker is given to the right; this one is *arena-0*.
11
-
There is a dot in the top-left corner of the black border. This corner is known as the *principal corner*, and its location is important if measuring the marker's orientation about the Z-axis.
12
-
There is also some text in the bottom-left corner of the black border.
13
-
This text will say something like `"libkoki marker #0 (v0.5) 'ARENA'"`.
14
-
Let's break that down:
15
-
`#0` means marker number 0;
16
-
`(v0.5)` tells you the version of the marker, it is important the latest version is used; and
17
-
`'ARENA'` is just a human-readable description of what the marker is for.
18
-
19
-
Details of the types and size of markers used in the SR2020 game can be found in the [rules](/docs/rules).
20
-
21
-
You can download all of the markers as a single [ZIP file](/docs/resources/2020/sr-dev-markers-sr2020.zip)
22
-
or individually from the [git repo](https://github.com/srobo/game-markers/tree/master/SR2020/dev).
23
-
The arena markers, due to their size, need to be printed on A3 paper.
24
-
Token markers can be printed on A4 so long as your printer can handle the very narrow 5mm page margins; if not, they will need to be printed on A3 as well.
25
-
Ensure you download the correct file for the paper size you intend to print on - the filenames all end in "-A3paper.pdf" or "-A4paper.pdf".
9
+
<imgsrc="{{ site.baseurl }}/images/content/vision/marker-0.png"alt="An Example Marker: 0"class="right half" />
10
+
11
+
An example marker is given to the right; this one is `0`. The marker is the correct way up, as shown by the text in the bottom left corner.
12
+
13
+
There is also some text in the bottom-left corner of the marker, in its padding: `Student Robotics APRILTAG_36H11 - Dev #0`.
14
+
15
+
-`#0` means marker number 0
16
+
-`APRILTAG_36H11` is the marker type
17
+
-`Dev` shows it's a development marker, rather than a competition marker
18
+
19
+
Details of the types and size of markers used in the game can be found in the [rules](/docs/rules).
20
+
21
+
You can download all the markers as a single [ZIP file](/docs/resources/2022/sr-dev-markers-sr2022.zip) or individually from the [git repo](https://github.com/srobo/game-markers/tree/master/SR2022/dev).
26
22
27
23
You must ensure that your PDF viewer is not resizing the documents when printing.
28
24
This can be checked by measuring the grey box around the marker and comparing this to the size defined in the rules.
@@ -32,6 +28,6 @@ Note that a different set of markers will be used in the arenas at the competiti
32
28
However, this is not something you need to worry about.
33
29
We will handle this for you automatically when your robot is started in competition mode.
34
30
35
-
The white space around the markers is very important -- without it, the markers probably won't be recognised.
36
-
If the markers become damaged (scuff markers, tears, etc...) they will not function as well (if at all).
37
-
If this happens, it is best to just print another one.
31
+
The white space around the markers is very important -- without it, the markers probably won't be recognised. This white border is needed to ensure there's enough contrast between the black marker and whatever it's attached to - its size isn't strictly important.
32
+
33
+
If the markers become damaged (scuff markers, tears, etc...) they will not function as well (if at all). If this happens, it is best to just print another one.
0 commit comments