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: articles/ai-services/computer-vision/Tutorials/liveness.md
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -37,7 +37,7 @@ The liveness solution integration involves two different components: a mobile ap
37
37
### Integrate liveness into mobile application
38
38
39
39
Once you have access to the SDK, follow instruction in the [azure-ai-vision-sdk](https://github.com/Azure-Samples/azure-ai-vision-sdk) GitHub repository to integrate the UI and the code into your native mobile application. The liveness SDK supports both Java/Kotlin for Android and Swift for iOS mobile applications:
40
-
- For Swift iOS, follow the instructions in the [iOS sample](https://aka.ms/liveness-sample-ios)
40
+
- For Swift iOS, follow the instructions in the [iOS sample](https://aka.ms/azure-ai-vision-face-liveness-client-sdk-ios-readme)
41
41
- For Kotlin/Java Android, follow the instructions in the [Android sample](https://aka.ms/liveness-sample-java)
42
42
43
43
Once you've added the code into your application, the SDK will handle starting the camera, guiding the end-user to adjust their position, composing the liveness payload, and calling the Azure AI Face cloud service to process the liveness payload.
@@ -54,7 +54,7 @@ The high-level steps involved in liveness orchestration are illustrated below:
// This allows Azure OpenAI to use an Azure AI Search index.
90
-
//
91
-
// > Because the model has access to, and can reference specific sources to support its responses, answers are not only based on its pretrained knowledge
92
-
// > but also on the latest information available in the designated data source. This grounding data also helps the model avoid generating responses
93
-
// > based on outdated or incorrect information.
94
-
//
95
-
// Quote from here: https://learn.microsoft.com/en-us/azure/ai-services/openai/concepts/use-your-data
&azopenai.ChatRequestUserMessage{Content: azopenai.NewChatRequestUserMessageContent("What are the differences between Azure Machine Learning and Azure AI services?")},
// This allows Azure OpenAI to use an Azure AI Search index.
85
+
//
86
+
// > Because the model has access to, and can reference specific sources to support its responses, answers are not only based on its pretrained knowledge
87
+
// > but also on the latest information available in the designated data source. This grounding data also helps the model avoid generating responses
88
+
// > based on outdated or incorrect information.
89
+
//
90
+
// Quote from here: https://learn.microsoft.com/en-us/azure/ai-services/openai/concepts/use-your-data
The application prints the response including both answers to your query and citations from your uploaded files.
137
132
138
133
> [!div class="nextstepaction"]
139
-
> [I ran into an issue when running the code samples.](https://microsoft.qualtrics.com/jfe/form/SV_0Cl5zkG3CnDjq6O?PLanguage=dotnet&Pillar=AOAI&Product=ownData&Page=quickstart&Section=Create-dotnet-application)
134
+
> [I ran into an issue when running the code samples.](https://microsoft.qualtrics.com/jfe/form/SV_0Cl5zkG3CnDjq6O?PLanguage=dotnet&Pillar=AOAI&Product=ownData&Page=quickstart&Section=Create-dotnet-application)
| Go |[Source code](https://github.com/Azure/azure-sdk-for-go/tree/main/sdk/ai/azopenai)|[Package (Go)](https://pkg.go.dev/github.com/Azure/azure-sdk-for-go/sdk/ai/azopenai)|[ Go examples](https://pkg.go.dev/github.com/Azure/azure-sdk-for-go/sdk/ai/azopenai#pkg-examples)|
When running your functions in an [App Service plan](./dedicated-plan.md), dependencies that you define in requirements.txt are given precedence over built-in Python modules, such as `logging`. This precedence can cause conflicts when built-in modules have the same names as directories in your code. When running in a [Consumption plan](./consumption-plan.md) or an [Elastic Premium plan](./functions-premium-plan.md), conflicts are less likely because your dependencies aren't prioritized by default.
975
975
976
-
To prevent issues running in an App Service plan, don't name your directories the same as any Python native modules and don't including Python native libraries in your project's requirements.txt file.
976
+
To prevent issues running in an App Service plan, don't name your directories the same as any Python native modules and don't include Python native libraries in your project's requirements.txt file.
0 commit comments