# Citing catch22

If you use ***catch22*** in a scientific publication, please read and cite this open-access article:

{% hint style="success" %}
Lubba et al. [*catch22*: CAnonical Time-series CHaracteristics](https://doi.org/10.1007/s10618-019-00647-x), *Data Min Knowl Disc* **33**, 1821 (2019).
{% endhint %}

{% hint style="info" %}
**Note**: When presenting results using *catch22*, please identify the **version used** to allow clear reproduction of your results. For example, `CO_f1ecac` was altered from an integer-valued output to a linearly interpolated real-valued output from `v0.3`. 
{% endhint %}

***

### BibTeX Entry:

```
@article{Lubba2019:Catch22CAnonicalTimeseries,
	title = {catch22: {CAnonical} {Time}-series {CHaracteristics}},
	volume = {33},
	issn = {1573-756X},
	url = {https://doi.org/10.1007/s10618-019-00647-x},
	doi = {10.1007/s10618-019-00647-x},
	number = {6},
	journal = {Data Mining and Knowledge Discovery},
	author = {Lubba, Carl H. and Sethi, Sarab S. and Knaute, Philip and Schultz, Simon R. and Fulcher, Ben D. and Jones, Nick S.},
	month = nov,
	year = {2019},
	pages = {1821--1852},
}
```

***


---

# Agent Instructions: 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://time-series-features.gitbook.io/catch22/welcome-to-catch22/citing-catch22.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.