> For the complete documentation index, see [llms.txt](https://time-series-features.gitbook.io/catch22/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://time-series-features.gitbook.io/catch22/information-about-catch22.md).

# INFORMATION ABOUT CATCH22

- [Feature Descriptions](https://time-series-features.gitbook.io/catch22/information-about-catch22/feature-descriptions.md): This chapter contains an overview table of the catch22 features as well as detailed descriptions and examples of each feature, organized into 9 distinct conceptual categories.
- [Feature Overview Table](https://time-series-features.gitbook.io/catch22/information-about-catch22/feature-descriptions/feature-overview-table.md): A high-level summary table of all catch22 features.
- [Distribution shape](https://time-series-features.gitbook.io/catch22/information-about-catch22/feature-descriptions/distribution-shape.md): The DN\_HistogramMode features measure properties of the shape of the distribution of time-series values.
- [Extreme event timing](https://time-series-features.gitbook.io/catch22/information-about-catch22/feature-descriptions/extreme-event-timing.md): The DN\_OutlierInclude features measure the timing of extreme events relative to the start and end of the time series.
- [Linear autocorrelation structure](https://time-series-features.gitbook.io/catch22/information-about-catch22/feature-descriptions/linear-autocorrelation-structure.md): Features quantifying linear autocorrelation structure (from the autocorrelation function or power spectrum).
- [Nonlinear autocorrelation](https://time-series-features.gitbook.io/catch22/information-about-catch22/feature-descriptions/nonlinear-autocorrelation.md): These features capture nonlinear autocorrelation properties of a time series.
- [Symbolic](https://time-series-features.gitbook.io/catch22/information-about-catch22/feature-descriptions/symbolic.md): Features based on a discrete symbolisation of real-valued time-series data.
- [Incremental differences](https://time-series-features.gitbook.io/catch22/information-about-catch22/feature-descriptions/incremental-differences.md): Properties of the 1-point incremental differences of the time series.
- [Simple forecasting](https://time-series-features.gitbook.io/catch22/information-about-catch22/feature-descriptions/simple-forecasting.md): Feature of a 3-point mean forecast.
- [Self-affine scaling](https://time-series-features.gitbook.io/catch22/information-about-catch22/feature-descriptions/self-affine-scaling.md): Features that capture the properties of long-range correlations in time series.
- [Other](https://time-series-features.gitbook.io/catch22/information-about-catch22/feature-descriptions/other.md): Time series features which do not fall into any of the other categories.
- [API Reference](https://time-series-features.gitbook.io/catch22/information-about-catch22/api-reference.md): Language-specific API reference.
- [Python API](https://time-series-features.gitbook.io/catch22/information-about-catch22/api-reference/python-api.md): This is the class and function reference of pycatch22. Please refer to the user guide for further details as the class and function specifications may not be sufficient to give full context.
- [Julia API](https://time-series-features.gitbook.io/catch22/information-about-catch22/api-reference/julia-api.md): This is the class and function reference of catch22.jl. Please refer to the user guide for further details as the class and function specifications may not be sufficient to give full context.
- [R API](https://time-series-features.gitbook.io/catch22/information-about-catch22/api-reference/r-api.md): This is the class and function reference of Rcatch22. Please refer to the user guide for further details as the class and function specifications may not be sufficient to give full context on their
- [MATLAB API](https://time-series-features.gitbook.io/catch22/information-about-catch22/api-reference/matlab-api.md): This is the class and function reference of catch22. Please refer to the user guide for further details as the class and function specifications may not be sufficient to give full context.
- [Contributing to catch22](https://time-series-features.gitbook.io/catch22/information-about-catch22/contributing-to-catch22.md): A guide on how users and developers can contribute to the project.
- [Contributor Code of Conduct](https://time-series-features.gitbook.io/catch22/information-about-catch22/contributing-to-catch22/contributor-code-of-conduct.md): catch22's contributor code of conduct.
- [Related Packages](https://time-series-features.gitbook.io/catch22/information-about-catch22/related-packages.md): Packages that are related to catch22 and the hctsa ecosystem.
- [License](https://time-series-features.gitbook.io/catch22/information-about-catch22/license.md): catch22 is licensed under the GNU GPL v3 license (or later).


---

# 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://time-series-features.gitbook.io/catch22/information-about-catch22.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.
