> For the complete documentation index, see [llms.txt](https://wiki.ariitk.in/wiki/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.ariitk.in/wiki/competitions/inter-iit-techmeet-11.0.md).

# Inter-IIT TechMeet 11.0

This page contains codes and resources for the event Drona Aviation Pluto Drone swarm challenge in the Inter-IIT TechMeet 11.0

## Inter-IIT TechMeet 11.0

#### Problem Statement

{% file src="/files/x7XvVdRHYKcS0R9Kv7No" %}
Swarm Drone Challenge Problem Statement
{% endfile %}

#### Technical Report & Slides

This file contains our architecture and approach to the problem statement:

{% file src="/files/BrA8iChkjxPnRRYC5adl" %}
Technical Report
{% endfile %}

This file contains the slides presented after the competition:

{% file src="/files/0mI2c0oM4kAaP1nrH7mN" %}
Slides
{% endfile %}

#### Software Stack

The complete software stack is available on Github. It contains all the modules we have used:

* <https://github.com/AerialRobotics-IITK/interiit_11.0>

**General Overview of the modules used:**

* **Pose\_ocam**: A detection and pose estimation module to detect the aruco marker and calculate the corresponding pose of the marker.
* **Pluto\_control**: A module which acts as a server for the socket communication. It receives the raw position from the pose\_ocam module, applies kalman filter to it for smoothening, uses the MPC control theory to calculate the desired Roll, Pitch, Yaw and Thrust and sends it to the drone using the MSP protocol.
* **Visualizer**: A module for accurate and precise visualization of the P,I,D values along with variable thrust, roll, pitch, and yaw plotted over time


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://wiki.ariitk.in/wiki/competitions/inter-iit-techmeet-11.0.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.