> For the complete documentation index, see [llms.txt](https://arcos.gitbook.io/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://arcos.gitbook.io/home/algorithm-overview/event-detection-and-tracking.md).

# Event Detection and Tracking

### Identification of spatial clusters

A dbscan algorithm first spatially clusters entities deemed active in each frame. In step 2, clusters are sequentially linked between frames to capture collective events over time. The cluster in frame one forms a seed of a collective event. The cluster in frame two is linked to this seed cluster because several of its member cells are within the neighbourhood radius 𝜀. In frame three, only clusters #3, #5, & #6 are linked to the previous frame’s cluster. Cells in cluster #4 are too far and thus form a new seed of a collective event.

![Figure 1: Demonstration of the ARCOS algorithm on a growing activity cluster](/files/6yThOzJ25vEFtNZlMwjW)

### Flow-Chart overview of ARCOS event detection

The flow chart below outlines the steps in the algorithm.&#x20;

![Figure 2: Step by step overview of the event detection and tracking](/files/vd6gohR5cbMTtzCRlS5v)


---

# 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://arcos.gitbook.io/home/algorithm-overview/event-detection-and-tracking.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.
