Skip to content

Commit 31e2cec

Browse files
ChristianH99ChristianH99
committed
Adjusted build scripts to build more than one file from scoresheets folder
Build of rules still untested Combination of Scoresheets into one PDF file still missing
1 parent ef5496e commit 31e2cec

File tree

9 files changed

+230
-492
lines changed

9 files changed

+230
-492
lines changed

‎.ci/adoc-to-tex.sh‎

Lines changed: 26 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1,18 +1,33 @@
11
#!/bin/bash
2-
mkdir -p tmp rules_documents
32

43
set -euo pipefail
54

6-
OUTPUT_FILE=$1
5+
INPUT_DIR=$1
6+
OUTPUT_FOLDER=$(basename "$INPUT_DIR")
7+
rm -rf "rules_documents/$OUTPUT_FOLDER/"
8+
mkdir -p tmp "rules_documents/$OUTPUT_FOLDER/"
79

8-
cp $OUTPUT_FILE/rules.adoc tmp/$OUTPUT_FILE.adoc
10+
for FILE in "$INPUT_DIR"/*.adoc; do
11+
FILE_NAME=$(basename "$FILE" .adoc)
12+
13+
cp "$FILE" "tmp/$FILE_NAME.adoc"
14+
15+
cd tmp
16+
17+
cp "$FILE_NAME.adoc" "_$FILE_NAME.adoc"
18+
python3 ../.ci/criticmarkup_to_adoc.py "_$FILE_NAME.adoc" > "$FILE_NAME.adoc"
19+
20+
asciidoctor "$FILE_NAME.adoc"
21+
asciidoctor -b docbook "$FILE_NAME.adoc"
22+
23+
NEW_FILE_NAME="$FILE_NAME"
24+
25+
if [[ "$FILE_NAME" =~ ^[0-9]{2}_(.*) ]]; then
26+
NEW_FILE_NAME="${BASH_REMATCH[1]}"
27+
fi
928

10-
cd tmp
29+
mv "$FILE_NAME.html" "../rules_documents/$OUTPUT_FOLDER/$NEW_FILE_NAME.html"
30+
31+
cd ..
1132

12-
cp $OUTPUT_FILE.adoc _$OUTPUT_FILE.adoc
13-
python3 ../.ci/criticmarkup_to_adoc.py _$OUTPUT_FILE.adoc > $OUTPUT_FILE.adoc
14-
15-
asciidoctor $OUTPUT_FILE.adoc
16-
asciidoctor -b docbook $OUTPUT_FILE.adoc
17-
18-
mv $OUTPUT_FILE.html ../rules_documents/
33+
done

‎.ci/tex-to-pdf.sh‎

Lines changed: 43 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,25 +1,58 @@
11
#!/bin/bash
22
set -euo pipefail
33

4-
OUTPUT_FILE=$1
4+
INPUT_DIR=$1
5+
OUTPUT_FOLDER=$(basename "$INPUT_DIR")
56

67
cp manual.sty tmp/
78
cp -r media tmp/
89
cd tmp
910

1011
# Apply custom styling to DocBook
11-
dblatex -T db2latex $OUTPUT_FILE.xml -t tex --texstyle=./manual.sty -p ../custom.xsl
12+
for FILE in *.xml; do
13+
dblatex -T db2latex "$FILE" -t tex --texstyle=./manual.sty -p ../custom.xsl
14+
done
1215

1316
# Go through the generated .tex output, find the place where the preamble ends
1417
# (marked by the \mainmatter command) and create a file without it.
15-
cat $OUTPUT_FILE.tex | awk 'f;/\\mainmatter/{f=1}' > $OUTPUT_FILE"_without_preamble.tex"
16-
# Concat the standardized preamble with the "without_preamble" version of the file
17-
cat "../preamble.tex" "../"$OUTPUT_FILE"/header_footer.tex" "../"$OUTPUT_FILE"/title.tex" "../committee_list.tex" $OUTPUT_FILE"_without_preamble.tex" > $OUTPUT_FILE.tex
18-
texliveonfly $OUTPUT_FILE.tex
19-
pdflatex $OUTPUT_FILE.tex
20-
pdflatex $OUTPUT_FILE.tex
18+
for FILE in *.tex; do
19+
FILE_NAME=$(basename "$FILE" .tex)
20+
21+
cat "$FILE" | awk 'f;/\\mainmatter/{f=1}' > "${FILE_NAME}_without_preamble.tex"
2122

22-
mv $OUTPUT_FILE.pdf ../rules_documents/
23+
ORIGINAL_TITLE_LINE=$(grep -m 1 '^\\title' "$FILE")
24+
TITLE_LINE=$(echo "$ORIGINAL_TITLE_LINE" | sed 's/\\title{\(.*\)}/\\title{\\vspace{-5ex}\1\\vspace{-9ex}}/')
25+
26+
# Concat the standardized preamble with the "without_preamble" version of the file + additional content
27+
if [[ "$FILE_NAME" == 00_* ]]; then
28+
# For file starting with "00_", include committee list
29+
cat "../preamble.tex" \
30+
"../${INPUT_DIR}/header_footer.tex" \
31+
<(echo "$TITLE_LINE") \
32+
<(echo "\maketitle") \
33+
"../committee_list.tex" \
34+
"${FILE_NAME}_without_preamble.tex" > "$FILE_NAME.tex"
35+
else
36+
# For other files, skip committee list
37+
cat "../preamble.tex" \
38+
"../${INPUT_DIR}/header_footer.tex" \
39+
<(echo "$TITLE_LINE") \
40+
<(echo "\maketitle") \
41+
"${FILE_NAME}_without_preamble.tex" > "$FILE_NAME.tex"
42+
fi
43+
44+
texliveonfly $FILE_NAME.tex
45+
pdflatex $FILE_NAME.tex
46+
pdflatex $FILE_NAME.tex
47+
48+
NEW_FILE_NAME="$FILE_NAME"
49+
50+
if [[ "$FILE_NAME" =~ ^[0-9]{2}_(.*) ]]; then
51+
NEW_FILE_NAME="${BASH_REMATCH[1]}"
52+
fi
53+
54+
cp $FILE_NAME.pdf "../rules_documents/$OUTPUT_FOLDER/$NEW_FILE_NAME.pdf"
55+
done
2356

2457
cd ..
25-
rm -r tmp
58+
rm -r tmp

‎onstage_entry_rules/rules.adoc‎ renamed to ‎onstage_entry_rules/onstage_entry_rules.adoc‎

File renamed without changes.

‎onstage_rules/rules.adoc‎ renamed to ‎onstage_rules/onstage_rules.adoc‎

File renamed without changes.

‎onstage_scoresheets/00_introduction.adoc‎

Lines changed: 43 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,43 @@
1+
= RoboCupJunior OnStage Score Sheets 2025
2+
{docdate}
3+
:toc: left
4+
:sectanchors:
5+
:sectlinks:
6+
:xrefstyle: full
7+
:section-refsig: Section
8+
:sectnums:
9+
10+
ifdef::basebackend-html[]
11+
++++
12+
<link rel="stylesheet" href="https://use.fontawesome.com/releases/v5.3.1/css/all.css" integrity="sha384-mzrmE5qonljUremFsqc01SB46JvROS7bZs3IO2EmfFsd15uHvIt+Y8vEf7N7fWAU" crossorigin="anonymous">
13+
<script src="https://hypothes.is/embed.js" async></script>
14+
++++
15+
endif::basebackend-html[]
16+
17+
:icons: font
18+
:numbered:
19+
20+
These are the official score sheets of the _RoboCup Federation_ for the _RoboCupJunior_ (RCJ) OnStage events in 2025.
21+
22+
*The International Original score sheets (in English) have priority over [.underline]#any# translations.*
23+
24+
Major changes from the previous years OnStage score sheets are written in *[red]#red#*.
25+
26+
*Teams should make sure to review _ALL_ pages of these score sheets.* The score sheets have been changed to deepen and broaden the educational benefits of competing in RoboCupJunior. It focuses on the evolving technologies available in our time.
27+
28+
*The rules, score sheets, and all forms of documentation can be downloaded from the official RoboCupJunior website* (https://junior.robocup.org). Each team has a responsibility to verify the latest version of these documents prior to the competition, as changes may be made at any moment. Teams are encouraged to study all documents in detail.
29+
30+
[discrete]
31+
== RoboCupJunior Forum
32+
33+
For inquiries and questions about the score sheets or competition updates, the *Official RoboCupJunior forum* (https://junior.forum.robocup.org/) can be used to contact the OnStage League Committee. All official communication from the committee will be published here before and during the competition season.
34+
35+
[discrete]
36+
== RoboCupJunior OnStage Community Website
37+
38+
Ressources for participating in the OnStage league can be found on the OnStage community website: https://robocup-junior.github.io/onstage
39+
40+
[discrete]
41+
== RoboCupJunior OnStage YouTube channel
42+
43+
Examples of good performances and documentation can be found on the *Official RoboCupJunior OnStage YouTube channel* (https://www.youtube.com/@rcjonstage).

‎onstage_scoresheets/01_technical_demonstration_video.adoc‎

Lines changed: 59 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,59 @@
1+
= [.underline]#Technical Demonstration Video# Score Sheet 2025
2+
{docdate}
3+
:toc: left
4+
:sectanchors:
5+
:sectlinks:
6+
:xrefstyle: full
7+
:section-refsig: Section
8+
:sectnums:
9+
10+
ifdef::basebackend-html[]
11+
++++
12+
<link rel="stylesheet" href="https://use.fontawesome.com/releases/v5.3.1/css/all.css" integrity="sha384-mzrmE5qonljUremFsqc01SB46JvROS7bZs3IO2EmfFsd15uHvIt+Y8vEf7N7fWAU" crossorigin="anonymous">
13+
<script src="https://hypothes.is/embed.js" async></script>
14+
++++
15+
endif::basebackend-html[]
16+
17+
:icons: font
18+
:numbered:
19+
20+
21+
[cols="8,40,>.>3"]
22+
|===
23+
|Category |Examples of how high marks may be achieved are: |Mark
24+
25+
|*Robotic Demonstration and Features*
26+
a|*Demonstration of a fully working robotic system including the four chosen features.*
27+
[compact]
28+
* Demonstrates the overall capabilities of the robot(s), including the four chosen features
29+
* Demonstrates fully working robotic systems without costumes
30+
* Explanations of how the four chosen features were selected by the team.
31+
|/6
32+
33+
|*Design Process*
34+
a|*Explain the design processes used during the development of the robotic systems including electromechanical, sensor, communication and software design choices.*
35+
[compact]
36+
* Highlights how the team overcame challenges in their design process, especially focusing on team’s problem solving and teamwork
37+
* Communicates team member’s roles and the contributions to the different systems (electromechanical, software etc.)
38+
|/3
39+
40+
|*Presentation*
41+
a|*Clarity and quality of the presentation.*
42+
[compact]
43+
* Presents a well-polished demonstration. Graphics and accompanying materials are clearly explained and presented.
44+
* Effectively communicates the technical capabilities of the robot to the audience in a concise and clear manner.
45+
* Technically unusual, creative, or ambitious concepts in the team’s robotic performance are clearly explained.
46+
|/3
47+
48+
|*Innovation and Sustainability*
49+
a|*Illustrating new and/or innovative technology to the OnStage competition.*
50+
[compact]
51+
* Innovation achieved with clear evidence of testing, research and development of the four chosen features.
52+
* Innovation can be an inspiration for future competitors.
53+
* Teams are able to explain how they considered sustainable practices during the development of their project.
54+
|/3
55+
56+
|*Total Score*
57+
|
58+
|*/15*
59+
|===

‎onstage_scoresheets/02_technical_description_poster.adoc‎

Lines changed: 59 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,59 @@
1+
= [.underline]#Technical Description Poster# Score Sheet 2025
2+
{docdate}
3+
:toc: left
4+
:sectanchors:
5+
:sectlinks:
6+
:xrefstyle: full
7+
:section-refsig: Section
8+
:sectnums:
9+
10+
ifdef::basebackend-html[]
11+
++++
12+
<link rel="stylesheet" href="https://use.fontawesome.com/releases/v5.3.1/css/all.css" integrity="sha384-mzrmE5qonljUremFsqc01SB46JvROS7bZs3IO2EmfFsd15uHvIt+Y8vEf7N7fWAU" crossorigin="anonymous">
13+
<script src="https://hypothes.is/embed.js" async></script>
14+
++++
15+
endif::basebackend-html[]
16+
17+
:icons: font
18+
:numbered:
19+
20+
21+
[cols="8,40,>.>3"]
22+
|===
23+
|Category |Examples of how high marks may be achieved are: |Mark
24+
25+
|*Robotic Demonstration and Features*
26+
a|*Demonstration of a fully working robotic system including the four chosen features.*
27+
[compact]
28+
* Demonstrates the overall capabilities of the robot(s), including the four chosen features
29+
* Demonstrates fully working robotic systems without costumes
30+
* Explanations of how the four chosen features were selected by the team.
31+
|/6
32+
33+
|*Design Process*
34+
a|*Explain the design processes used during the development of the robotic systems including electromechanical, sensor, communication and software design choices.*
35+
[compact]
36+
* Highlights how the team overcame challenges in their design process, especially focusing on team’s problem solving and teamwork
37+
* Communicates team member’s roles and the contributions to the different systems (electromechanical, software etc.)
38+
|/3
39+
40+
|*Presentation*
41+
a|*Clarity and quality of the presentation.*
42+
[compact]
43+
* Presents a well-polished demonstration. Graphics and accompanying materials are clearly explained and presented.
44+
* Effectively communicates the technical capabilities of the robot to the audience in a concise and clear manner.
45+
* Technically unusual, creative, or ambitious concepts in the team’s robotic performance are clearly explained.
46+
|/3
47+
48+
|*Innovation and Sustainability*
49+
a|*Illustrating new and/or innovative technology to the OnStage competition.*
50+
[compact]
51+
* Innovation achieved with clear evidence of testing, research and development of the four chosen features.
52+
* Innovation can be an inspiration for future competitors.
53+
* Teams are able to explain how they considered sustainable practices during the development of their project.
54+
|/3
55+
56+
|*Total Score*
57+
|
58+
|*/15*
59+
|===

0 commit comments

Comments
 (0)