Skip to main content

Microsoft.Extensions.AI–Part VIII–Evaluations

Back from holiday with charged batteries, we continue our journey exploring the Microsoft.Extensions.AI library. Today we have a look at evaluating AI models.

This post is part of a blog series. Other posts so far:

What is Microsoft.Extensions.AI.Evaluation?

Microsoft.Extensions.AI.Evaluation is a set of libraries with one common goal; simplifying the process of evaluating the quality and accuracy of responses generated by AI models. Measuring the quality of your AI apps is challenging, you need to evaluate metrics like:

  • Relevance: How effective is the response for a given prompt?
  • Truthfulness: Is the response factually correct?
  • Coherence: Is the response logically structured and consistent?
  • Completeness: Is the response a sufficient answer?
  • And many more…

The evaluation libraries handle this for you through a list of available evaluators that can easily be integrated in your existing test infrastructure and framework.

But enough talking, let’s give it a try…

Integrate AI quality validation for our chat application

Start by adding a new test project to your solution using the framework of your choice. I'll be using XUnit in this post but the library itself is completely test framework agnostic.

Add a reference to the Microsoft.Extensions.AI.Evaluation.Quality library:

dotnet package add Microsoft.Extensions.AI.Evaluation.Quality

Now we first need to bootstrap our ChatConfiguration:

And also build up our prompt:

Once these 2 things are in place, we can setup the evaluator(s) for our test, invoke our LLM and evaluate the results:

Of course, this test fails as the AI suggested the moon as a good holiday location.

Tomorrow we further extend this example and have a look at caching of the model responses and reporting of the evaluations.

More information

The Microsoft.Extensions.AI.Evaluation libraries - .NET | Microsoft Learn

ai-samples/src/microsoft-extensions-ai-evaluation/api/README.md at main · dotnet/ai-samples

Exploring new Agent Quality and NLP evaluators for .NET AI applications - .NET Blog

Popular posts from this blog

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...