These docs are for version 1.x of Rasa Open Source.

## User Guide

- [Installation](https://legacy-docs-v1.rasa.com/1.10.13/user-guide/installation/)
- [Tutorial: Rasa Basics](https://legacy-docs-v1.rasa.com/1.10.13/user-guide/rasa-tutorial/)
- [Tutorial: Building Assistants](https://legacy-docs-v1.rasa.com/1.10.13/user-guide/building-assistants/)
- [Command Line Interface](https://legacy-docs-v1.rasa.com/1.10.13/user-guide/command-line-interface/)
- [Architecture](https://legacy-docs-v1.rasa.com/1.10.13/user-guide/architecture/)
- [Messaging and Voice Channels](https://legacy-docs-v1.rasa.com/1.10.13/user-guide/messaging-and-voice-channels/)
- [Testing Your Assistant](https://legacy-docs-v1.rasa.com/1.10.13/user-guide/testing-your-assistant/)
- [Setting up CI/CD](https://legacy-docs-v1.rasa.com/1.10.13/user-guide/setting-up-ci-cd/)
- [Validate Data](https://legacy-docs-v1.rasa.com/1.10.13/user-guide/validate-files/)
- [Configuring the HTTP API](https://legacy-docs-v1.rasa.com/1.10.13/user-guide/configuring-http-api/)
- [Deploying Your Rasa Assistant](https://legacy-docs-v1.rasa.com/1.10.13/user-guide/how-to-deploy/)
- [Cloud Storage](https://legacy-docs-v1.rasa.com/1.10.13/user-guide/cloud-storage/)

## NLU

- [About](https://legacy-docs-v1.rasa.com/1.10.13/nlu/about/)
- [Using NLU Only](https://legacy-docs-v1.rasa.com/1.10.13/nlu/using-nlu-only/)
- [Training Data Format](https://legacy-docs-v1.rasa.com/1.10.13/nlu/training-data-format/)
- [Language Support](https://legacy-docs-v1.rasa.com/1.10.13/nlu/language-support/)
- [Choosing a Pipeline](https://legacy-docs-v1.rasa.com/1.10.13/nlu/choosing-a-pipeline/#)
- [Components](https://legacy-docs-v1.rasa.com/1.10.13/nlu/components/)
- [Entity Extraction](https://legacy-docs-v1.rasa.com/1.10.13/nlu/entity-extraction/)

## Core

- [About](https://legacy-docs-v1.rasa.com/1.10.13/core/about/)
- [Stories](https://legacy-docs-v1.rasa.com/1.10.13/core/stories/)
- [Domains](https://legacy-docs-v1.rasa.com/1.10.13/core/domains/)
- [Responses](https://legacy-docs-v1.rasa.com/1.10.13/core/responses/)
- [Actions](https://legacy-docs-v1.rasa.com/1.10.13/core/actions/)
- [Reminders and External Events](https://legacy-docs-v1.rasa.com/1.10.13/core/reminders-and-external-events/)
- [Policies](https://legacy-docs-v1.rasa.com/1.10.13/core/policies/)
- [Slots](https://legacy-docs-v1.rasa.com/1.10.13/core/slots/)
- [Forms](https://legacy-docs-v1.rasa.com/1.10.13/core/forms/)
- [Retrieval Actions](https://legacy-docs-v1.rasa.com/1.10.13/core/retrieval-actions/)
- [Interactive Learning](https://legacy-docs-v1.rasa.com/1.10.13/core/interactive-learning/)
- [Fallback Actions](https://legacy-docs-v1.rasa.com/1.10.13/core/fallback-actions/)
- [Knowledge Base Actions](https://legacy-docs-v1.rasa.com/1.10.13/core/knowledge-bases/)

## Conversation Design

- [Dialogue Elements](https://legacy-docs-v1.rasa.com/1.10.13/dialogue-elements/dialogue-elements/)
- [Small Talk](https://legacy-docs-v1.rasa.com/1.10.13/dialogue-elements/small-talk/)
- [Completing Tasks](https://legacy-docs-v1.rasa.com/1.10.13/dialogue-elements/completing-tasks/)
- [Guiding Users](https://legacy-docs-v1.rasa.com/1.10.13/dialogue-elements/guiding-users/)

## API Reference

- [Action Server](https://legacy-docs-v1.rasa.com/1.10.13/api/action-server/)
- [HTTP API](https://legacy-docs-v1.rasa.com/1.10.13/api/http-api/)
- [Jupyter Notebooks](https://legacy-docs-v1.rasa.com/1.10.13/api/jupyter-notebooks/)
- [Agent](https://legacy-docs-v1.rasa.com/1.10.13/api/agent/)
- [Custom NLU Components](https://legacy-docs-v1.rasa.com/1.10.13/api/custom-nlu-components/)
- [Rasa SDK](https://legacy-docs-v1.rasa.com/1.10.13/api/rasa-sdk/)
- [Events](https://legacy-docs-v1.rasa.com/1.10.13/api/events/)
- [Tracker](https://legacy-docs-v1.rasa.com/1.10.13/api/tracker/)
- [Tracker Stores](https://legacy-docs-v1.rasa.com/1.10.13/api/tracker-stores/)
- [Event Brokers](https://legacy-docs-v1.rasa.com/1.10.13/api/event-brokers/)
- [Lock Stores](https://legacy-docs-v1.rasa.com/1.10.13/api/lock-stores/)
- [Training Data Importers](https://legacy-docs-v1.rasa.com/1.10.13/api/training-data-importers/)
- [Featurization of Conversations](https://legacy-docs-v1.rasa.com/1.10.13/api/core-featurization/)
- [TensorFlow Configuration](https://legacy-docs-v1.rasa.com/1.10.13/api/tensorflow_usage/)
- [Migration Guide](https://legacy-docs-v1.rasa.com/1.10.13/migration-guide/)
- [Rasa Open Source Change Log](https://legacy-docs-v1.rasa.com/1.10.13/changelog/)

## Migrate from (beta)

- [Dialogflow](https://legacy-docs-v1.rasa.com/1.10.13/migrate-from/google-dialogflow-to-rasa/)
- [Wit.ai](https://legacy-docs-v1.rasa.com/1.10.13/migrate-from/facebook-wit-ai-to-rasa/)
- [LUIS](https://legacy-docs-v1.rasa.com/1.10.13/migrate-from/microsoft-luis-to-rasa/)
- [IBM Watson](https://legacy-docs-v1.rasa.com/1.10.13/migrate-from/ibm-watson-to-rasa/)

## Reference

- [Glossary](https://legacy-docs-v1.rasa.com/1.10.13/glossary/)

## Versions

viewing: 1.10.13

## Choosing a Pipeline

In Rasa Open Source, incoming messages are processed by a sequence of components. These components are executed one after another in a so-called processing `pipeline` defined in your `config.yml`. Choosing an NLU pipeline allows you to customize your model and finetune it on your dataset.

### How to Choose a Pipeline

If your training data is in English, a good starting point is the following pipeline:

```
language: "en"

pipeline:
  - name: ConveRTTokenizer
  - name: ConveRTFeaturizer
  - name: RegexFeaturizer
  - name: LexicalSyntacticFeaturizer
  - name: CountVectorsFeaturizer
  - name: CountVectorsFeaturizer
    analyzer: "char_wb"
    min_ngram: 1
    max_ngram: 4
  - name: DIETClassifier
    epochs: 100
  - name: EntitySynonymMapper
  - name: ResponseSelector
    epochs: 100
```

If your training data is not in English, start with the following pipeline:

```
language: "fr"  # your two-letter language code

pipeline:
  - name: WhitespaceTokenizer
  - name: RegexFeaturizer
  - name: LexicalSyntacticFeaturizer
  - name: CountVectorsFeaturizer
  - name: CountVectorsFeaturizer
    analyzer: "char_wb"
    min_ngram: 1
    max_ngram: 4
  - name: DIETClassifier
    epochs: 100
  - name: EntitySynonymMapper
  - name: ResponseSelector
    epochs: 100
```

### Choosing the Right Components

There are components for entity extraction, for intent classification, response selection, pre-processing, and others. You can learn more about any specific component on the [Components](https://legacy-docs-v1.rasa.com/1.10.13/nlu/components/#components) page. If you want to add your own component, for example to run a spell-check or to do sentiment analysis, check out [Custom NLU Components](https://legacy-docs-v1.rasa.com/1.10.13/api/custom-nlu-components/#custom-nlu-components).

A pipeline usually consists of three main parts:

- [Tokenization](https://legacy-docs-v1.rasa.com/1.10.13/nlu/choosing-a-pipeline/#tokenization)

- [Featurization](https://legacy-docs-v1.rasa.com/1.10.13/nlu/choosing-a-pipeline/#featurization)

- [Entity Recognition / Intent Classification / Response Selectors](https://legacy-docs-v1.rasa.com/1.10.13/nlu/choosing-a-pipeline/#entity-recognition-intent-classification-response-selectors)

### Tokenization

For tokenization of English input, we recommend the [ConveRTTokenizer](https://legacy-docs-v1.rasa.com/1.10.13/nlu/components/#converttokenizer). You can process other whitespace-tokenized (words are separated by spaces) languages with the [WhitespaceTokenizer](https://legacy-docs-v1.rasa.com/1.10.13/nlu/components/#whitespacetokenizer). If your language is not whitespace-tokenized, you should use a different tokenizer. We support a number of different [tokenizers](https://legacy-docs-v1.rasa.com/1.10.13/nlu/components/#tokenizers), or you can create your own [custom tokenizer](https://legacy-docs-v1.rasa.com/1.10.13/api/custom-nlu-components/#custom-nlu-components).

### Featurization

You need to decide whether to use components that provide pre-trained word embeddings or not. We recommend in cases of small amounts of training data to start with pre-trained word embeddings. Once you have a larger amount of data and ensure that most relevant words will be in your data and therefore will have a word embedding, supervised embeddings, which learn word meanings directly from your training data, can make your model more specific to your domain. If you can’t find a pre-trained model for your language, you should use supervised embeddings.

- [Pre-trained Embeddings](https://legacy-docs-v1.rasa.com/1.10.13/nlu/choosing-a-pipeline/#pre-trained-embeddings)

- [Supervised Embeddings](https://legacy-docs-v1.rasa.com/1.10.13/nlu/choosing-a-pipeline/#supervised-embeddings)

### Entity Recognition / Intent Classification / Response Selectors

Depending on your data you may want to only perform intent classification, entity recognition or response selection. Or you might want to combine multiple of those tasks. We support several components for each of the tasks. All of them are listed in [Components](https://legacy-docs-v1.rasa.com/1.10.13/nlu/components/#components). We recommend using [DIETClassifier](https://legacy-docs-v1.rasa.com/1.10.13/nlu/components/#diet-classifier) for intent classification and entity recognition and [ResponseSelector](https://legacy-docs-v1.rasa.com/1.10.13/nlu/components/#response-selector) for response selection.

### Multi-Intent Classification

You can use Rasa Open Source components to split intents into multiple labels. For example, you can predict multiple intents (`thank+goodbye`) or model hierarchical intent structure (`feedback+positive` being more similar to `feedback+negative` than `chitchat`). To do this, you need to use the [DIETClassifier](https://legacy-docs-v1.rasa.com/1.10.13/nlu/components/#diet-classifier) in your pipeline. You’ll also need to define these flags in whichever tokenizer you are using:

- `intent_tokenization_flag`: Set it to `True`, so that intent labels are tokenized.

- `intent_split_symbol`: Set it to the delimiter string that splits the intent labels. In this case `+`, default `_`.

### Comparing Pipelines

Rasa gives you the tools to compare the performance of multiple pipelines on your data directly. See [Comparing NLU Pipelines](https://legacy-docs-v1.rasa.com/1.10.13/user-guide/testing-your-assistant/#comparing-nlu-pipelines) for more information.

### Handling Class Imbalance

Classification algorithms often do not perform well if there is a large class imbalance, for example if you have a lot of training data for some intents and very little training data for others. To mitigate this problem, you can use a `balanced` batching strategy. This algorithm ensures that all classes are represented in every batch, or at least in as many subsequent batches as possible, still mimicking the fact that some classes are more frequent than others. Balanced batching is used by default. In order to turn it off and use a classic batching strategy include `batch_strategy: sequence` in your config file.