You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: Orchestrator/README.md
+11-14Lines changed: 11 additions & 14 deletions
Original file line number
Diff line number
Diff line change
@@ -23,13 +23,13 @@ Orchestrator can be used in different development environments:
23
23
-[Bot Framework SDK][24]: Orchestrator can be integrated into your code project by replacing LUIS for intent recognition, such as for skill delegation or dispatching to subsequent language understanding services. See the [SDK integration](#sdk-integration) section for more information. <!--We don't yet document Orchestrator in the SDK docs. Do we need to?-->
24
24
-[Bot Framework Composer][19]: Orchestrator can be selected as a recognizer within Bot Framework Composer. At this point there are limitations to using Orchestrator in Composer, primarily around importing of existing models and tuning recognition performance. (To use Orchestrator, enable the feature flag in your Composer settings.) See the [Composer integration](#composer-integration) section for more information.
25
25
26
-
In most cases, the [Bot Framework CLI][7]and [Bot Framework CLI Orchestrator plugin][11]is required to prepare and optimize the model for your domain. The [BF Orchestrator command usage][23] page describes how to create, evaluate, and use an Orchestrator model. This diagram illustrates the first part of that process. <!--The diagram leaves off steps 4 and 5.-->
26
+
In most cases, the [Bot Framework CLI][7] is required to prepare and optimize the model for your domain. The [BF Orchestrator command usage][23] page describes how to create, evaluate, and use an Orchestrator model. This diagram illustrates the first part of that process. <!--The diagram leaves off steps 4 and 5.-->
**Note**: To use the CLI, first install the [Bot Framework CLI Orchestrator plugin][11].
32
+
**Note**: To use the CLI, first install the [Bot Framework CLI][7].
33
33
34
34
See the [BF Orchestrator command usage][23] page for instructions on how to create and optimize the language model for your bot.
35
35
@@ -85,17 +85,14 @@ Orchestrator can be used as recognizer in [Bot Framework Composer][19].
85
85
86
86
In general, to specify Orchestrator as a dialog recognizer:
87
87
88
-
1. Enable the Orchestrator feature in Composer's **Application Settings** page. Particularly during the *Preview Release* please make sure to follow the latest up-to-date instructions in [Composer documentation][25].
89
-
2. Select **Orchestrator** in the **Recognizer Type** drop-down menu for your bot.
90
-
3. Review, evaluate and adjust examples in language data as you would normally for LUIS to ensure recognition quality.
88
+
1. Select **Orchestrator** in the **Recognizer Type** drop-down menu for your bot.
89
+
2. Review, evaluate and adjust examples in language data as you would normally for LUIS to ensure recognition quality.
91
90
92
-
This enables basic intent recognition. For more advanced scenarios follow the steps above to import and tune up routing quality. For more information about recognizers in Composer, see the discussion of [recognizers](https://docs.microsoft.com/composer/concept-dialog#recognizer) with respect to dialogs in Composer.
91
+
This enables basic intent recognition. For more advanced scenarios follow the steps above to import and tune up routing quality. For more information about recognizers in Composer, see the discussion of [recognizers](https://docs.microsoft.com/composer/concept-dialog#recognizer) with respect to dialogs in Composer. Please make sure to follow the latest up-to-date instructions in [Composer documentation][25]
93
92
94
93
## Limitations
95
94
96
95
* Orchestrator is limited to intents only. Entity definitions are ignored and no entity extraction is performed during recognition.
97
-
* Only English language recognition is available in this preview release.
98
-
* Only the *default* base model is available to Orchestrator solutions.
99
96
100
97
## Platform Support
101
98
Orchestrator supports the following platforms.
@@ -116,7 +113,7 @@ C# .NET Core 3.1
116
113
-[Tech overview][18]
117
114
-[API reference][14]
118
115
-[Roadmap](./docs/Overview.md#Roadmap)
119
-
-[BF CLI Orchestrator plugin][11]
116
+
-[BF CLI Orchestrator commands][11]
120
117
-[C# samples][12]
121
118
-[NodeJS samples][13]
122
119
-[BF Orchestrator Command Usage][23]
@@ -130,14 +127,14 @@ See the [School skill navigator](https://github.com/microsoft/BotBuilder-Samples
Copy file name to clipboardExpand all lines: Orchestrator/docs/BFOrchestratorUsage.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -93,7 +93,7 @@ Create a label .lu file with test data set of utterances. Run the following comm
93
93
bf orchestrator:test --in <snapshot file> --model <base model file> --out <report folder> --test <test data file>
94
94
```
95
95
96
-
See also [bf orchestrator test](https://github.com/microsoft/botframework-cli/tree/beta/packages/orchestrator#bf-orchestratortest) for full command line options.
96
+
See also [bf orchestrator test](https://github.com/microsoft/botframework-cli/tree/main/packages/orchestrator#bf-orchestratortest) for full command line options.
97
97
98
98
See also [Report Interpretation][6] for how to use the report to fine tune your language model.
0 commit comments