> For the complete documentation index, see [llms.txt](https://njord.gitbook.io/njord/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://njord.gitbook.io/njord/the-challenge/technical-report.md).

# Technical Report

The technical report is a requirement in the Challenge to give teams a chance to highlight certain details of their work which may otherwise have been overlooked. Additionally, systems do not always behave as expected on the competition day itself, in which case the technical report can help communicate the system's intended behavior.

### Formal Requirements

The technical report must be a maximum of 10 pages long, excluding a title page and references or appendices. This limit is partially out of respect to the jury members, who are volunteering their time to read the reports. Additionally, it should motivate teams to pick out a few aspects of their autonomy system which they find particularly innovative or complex.\
The report should be written in English in (minimum) size 12 font, and be delivered as a PDF.

**Note:** The technical reports will be made publicly available in the days leading up to the competition. As such, do not include any personal information (or otherwise) you are not comfortable with having published.

### Jury Criteria

The technical report will be reviewed by the jury and awarded a score counting 25% of a team's total score. The jury will be awarding points based on their evaluation of the following aspects:

* The report communicates a basic overview of the team's autonomous system.
* The report includes a more detailed discussion of a certain component or aspect of the system which was found to be particularly challenging, or where an innovative solution was found.
* The report succeeds in highlighting both the capabilities and the limitations of the team's autonomous system.
* The report includes figures and/or diagrams which help convey the intended message.
* The report is written in a cohesive manner that reflects an understanding of the topics discussed.

Teams can assume that the jury are all familiar with fundamental engineering/marine cybernetics concepts, however if in doubt, include a short explanation or a reference to where more information can be found.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://njord.gitbook.io/njord/the-challenge/technical-report.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.