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

# Sector

This is an internal class automatically initialized by the [TrackManager ](/ttsystem/components-prefabs/trackmanager.md)based on the number of sectors present in a track and is calculated based on the number of track points and the type of track.

This is explained further in the TrackType section of the [TrackManager](/ttsystem/components-prefabs/trackmanager.md) component.

A sector holds important time trial information such as:

* The index of the sector
* Whether the sector has been completed by a [LapTimeTrackingObject](/ttsystem/components-prefabs/laptimetrackingobject.md)
* How long the sector took to be completed by a [LapTimeTrackingObject](/ttsystem/components-prefabs/laptimetrackingobject.md)
* A time formatted representation of that sector time. (Formatted to the nearest millisecond by default).

{% hint style="info" %}
**NOTE:** To change the formatting of how your lap and sector times are represented, you can modify the FormatTime function in the [LapTimeTrackingObject](/ttsystem/components-prefabs/laptimetrackingobject.md). The default time format is 'm\\:ss\\.fff' which rounds times to the nearest millisecond.
{% endhint %}


---

# 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://llando.gitbook.io/ttsystem/internal-classes/sector.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.