Skip to content

Commit 48d8068

Browse files
authored
Removed bf orchestrator plugin instruction since it's no longer a separate bf cli plugin (#6260)
* Update DispatchMigrationExample.md Remove separate bf orchestrator plugin install instruction * Update README.md - Updated links to bf cli orchestrator - Updated bf cli links in references - Removed english only support * updated orchstrator links
1 parent 503a58e commit 48d8068

File tree

5 files changed

+15
-19
lines changed

5 files changed

+15
-19
lines changed

Orchestrator/README.md

Lines changed: 11 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -23,13 +23,13 @@ Orchestrator can be used in different development environments:
2323
- [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?-->
2424
- [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.
2525

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.-->
2727

2828
<p align="center">
2929
<img width="350" src="./docs/media/authoring.png" />
3030
</p>
3131

32-
**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].
3333

3434
See the [BF Orchestrator command usage][23] page for instructions on how to create and optimize the language model for your bot.
3535

@@ -85,17 +85,14 @@ Orchestrator can be used as recognizer in [Bot Framework Composer][19].
8585

8686
In general, to specify Orchestrator as a dialog recognizer:
8787

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.
9190

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]
9392

9493
## Limitations
9594

9695
* 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.
9996

10097
## Platform Support
10198
Orchestrator supports the following platforms.
@@ -116,7 +113,7 @@ C# .NET Core 3.1
116113
- [Tech overview][18]
117114
- [API reference][14]
118115
- [Roadmap](./docs/Overview.md#Roadmap)
119-
- [BF CLI Orchestrator plugin][11]
116+
- [BF CLI Orchestrator commands][11]
120117
- [C# samples][12]
121118
- [NodeJS samples][13]
122119
- [BF Orchestrator Command Usage][23]
@@ -130,14 +127,14 @@ See the [School skill navigator](https://github.com/microsoft/BotBuilder-Samples
130127
[5]:https://docs.microsoft.com/azure/bot-service/bot-builder-tutorial-dispatch?tabs=cs
131128
[6]:https://aka.ms/adaptive-dialogs
132129
[7]:https://github.com/microsoft/botframework-cli
133-
[8]:https://github.com/microsoft/botframework-cli/tree/master/packages/luis#bf-luisversionexport
134-
[9]:https://github.com/microsoft/botframework-cli/tree/master/packages/luis#bf-luisconvert
135-
[10]:https://github.com/microsoft/botframework-cli/tree/master/packages/qnamaker#bf-qnamakerkbexport
136-
[11]:https://github.com/microsoft/botframework-cli/tree/beta/packages/orchestrator
130+
[8]:https://github.com/microsoft/botframework-cli/tree/main/packages/luis#bf-luisversionexport
131+
[9]:https://github.com/microsoft/botframework-cli/tree/main/packages/luis#bf-luisconvert
132+
[10]:https://github.com/microsoft/botframework-cli/tree/main/packages/qnamaker#bf-qnamakerkbexport
133+
[11]:https://github.com/microsoft/botframework-cli/tree/main/packages/orchestrator
137134
[12]:https://github.com/microsoft/BotBuilder-Samples/tree/main/experimental/orchestrator/csharp_dotnetcore
138135
[13]:https://github.com/microsoft/BotBuilder-Samples/tree/main/experimental/orchestrator/javascript_nodejs
139136
[14]:https://aka.ms/bforchestratorapi
140-
[16]:https://github.com/microsoft/botframework-cli/tree/beta/packages/orchestrator#bf-orchestratorcreate
137+
[16]:https://github.com/microsoft/botframework-cli/tree/main/packages/orchestrator#bf-orchestratorcreate
141138
[18]:./docs/Overview.md
142139
[19]: https://docs.microsoft.com/composer/introduction
143140
[20]: https://aka.ms/NLRModels "Natural Language Representation Models"

Orchestrator/docs/BFOrchestratorReport.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -176,4 +176,4 @@ This evaluation report is created using several thresholds that they can also be
176176
[2]:https://en.wikipedia.org/wiki/Confusion_matrix "Wikipedia: Confusion matrix"
177177
[3]:https://aka.ms/nlrmodels "NLR Models"
178178
[4]:https://docs.microsoft.com/en-us/azure/bot-service/file-format/bot-builder-lu-file-format?view=azure-bot-service-4.0 ".LU format"
179-
[5]: https://github.com/microsoft/botframework-cli/tree/beta/packages/orchestrator#bf-orchestratortest "bf orchestrator:test"
179+
[5]: https://github.com/microsoft/botframework-cli/tree/main/packages/orchestrator#bf-orchestratortest "bf orchestrator:test"

Orchestrator/docs/BFOrchestratorUsage.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -93,7 +93,7 @@ Create a label .lu file with test data set of utterances. Run the following comm
9393
bf orchestrator:test --in <snapshot file> --model <base model file> --out <report folder> --test <test data file>
9494
```
9595

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.
9797

9898
See also [Report Interpretation][6] for how to use the report to fine tune your language model.
9999

Orchestrator/docs/DispatchMigrationExample.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,6 @@ Here, we will modify that sample to use Orchestrator in place of the top LUIS ar
2121
* Have access to create & use [LUIS][4] and [QnAMaker][5] services.
2222
* See [Dispatch Sample documentation][1] for full details.
2323
* Install [BF CLI][6]
24-
* Install BF CLI [Orchestrator Plugin][7]
2524
* Bot project must target x64 platform
2625
* Install latest supported version of [Visual C++ runtime](https://support.microsoft.com/en-gb/help/2977003/the-latest-supported-visual-c-downloads)
2726

@@ -522,5 +521,5 @@ Compile and run. The sample will use Orchestrator to arbitrate ("dispatch") to t
522521
[4]:https://luis.ai "LUIS"
523522
[5]:https://qnamaker.ai "QnAMaker"
524523
[6]:https://github.com/microsoft/botframework-cli "BF CLI"
525-
[7]:https://github.com/microsoft/botframework-cli/tree/beta/packages/orchestrator "Orchestrator plugin"
524+
[7]:https://github.com/microsoft/botframework-cli/tree/main/packages/orchestrator "Orchestrator plugin"
526525
[8]:https://github.com/microsoft/botbuilder-tools/tree/master/packages/Dispatch "Dispatch CLI"

parsers/LU/JS/packages/lu/package.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@
1414
],
1515
"homepage": "https://github.com/microsoft/botframework-cli",
1616
"license": "MIT",
17-
"repository": "https://github.com/microsoft/botframework-cli/tree/master/packages/lu",
17+
"repository": "https://github.com/microsoft/botframework-cli/tree/main/packages/lu",
1818
"scripts": {
1919
"postpack": "",
2020
"posttest": "tslint -p test -t stylish",

0 commit comments

Comments
 (0)