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

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...

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.

Cleaner switch expressions with pattern matching in C#

Ever find yourself mapping multiple string values to the same result? Being a C# developer for a long time, I sometimes forget that the C# has evolved so I still dare to chain case labels or reach for a dictionary. Of course with pattern matching this is no longer necessary. With pattern matching, you can express things inline, declaratively, and with zero repetition. A small example I was working on a small script that should invoke different actions depending on the environment. As our developers were using different variations for the same environment e.g.  "tst" alongside "test" , "prd" alongside "prod" .  We asked to streamline this a long time ago, but as these things happen, we still see variations in the wild. This brought me to the following code that is a perfect example for pattern matching: The or keyword here is a logical pattern combinator , not a boolean operator. It matches if either of the specified pattern...