Skip to content

[UserFrustration] Add coloring for UserFrustration eval results in the eval run tab#19383

Merged
xsh310 merged 1 commit intomlflow:masterfrom
xsh310:stack/user-frustration-eval-run-tab-ui-polish
Dec 16, 2025
Merged

[UserFrustration] Add coloring for UserFrustration eval results in the eval run tab#19383
xsh310 merged 1 commit intomlflow:masterfrom
xsh310:stack/user-frustration-eval-run-tab-ui-polish

Conversation

@xsh310
Copy link
Collaborator

@xsh310 xsh310 commented Dec 15, 2025

🥞 Stacked PR

Use this link to review incremental changes.


What changes are proposed in this pull request?

Context

One feedback from the multi-turn M1 bug bash was that the UI for UserFrustration judge is not highlighted and difficult to read (ML-60165).

This PR

Add coloring for UserFrustration built-in judge results in the eval run tab and trace tab so that the result is highlighted and easier to read.

How is this PR tested?

  • Existing unit/integration tests
  • New unit/integration tests
  • Manual tests

Manual Test

Before After
image image
image image
image image

Does this PR require documentation update?

  • No. You can skip the rest of this section.
  • Yes. I've updated:
    • Examples
    • API references
    • Instructions

Release Notes

Is this a user-facing change?

  • No. You can skip the rest of this section.
  • Yes. Give a description of this change to be included in the release notes for MLflow users.

What component(s), interfaces, languages, and integrations does this PR affect?

Components

  • area/tracking: Tracking Service, tracking client APIs, autologging
  • area/models: MLmodel format, model serialization/deserialization, flavors
  • area/model-registry: Model Registry service, APIs, and the fluent client calls for Model Registry
  • area/scoring: MLflow Model server, model deployment tools, Spark UDFs
  • area/evaluation: MLflow model evaluation features, evaluation metrics, and evaluation workflows
  • area/gateway: MLflow AI Gateway client APIs, server, and third-party integrations
  • area/prompts: MLflow prompt engineering features, prompt templates, and prompt management
  • area/tracing: MLflow Tracing features, tracing APIs, and LLM tracing functionality
  • area/projects: MLproject format, project running backends
  • area/uiux: Front-end, user experience, plotting, JavaScript, JavaScript dev server
  • area/build: Build and test infrastructure for MLflow
  • area/docs: MLflow documentation pages

How should the PR be classified in the release notes? Choose one:

  • rn/none - No description will be included. The PR will be mentioned only by the PR number in the "Small Bugfixes and Documentation Updates" section
  • rn/breaking-change - The PR will be mentioned in the "Breaking Changes" section
  • rn/feature - A new user-facing feature worth mentioning in the release notes
  • rn/bug-fix - A user-facing bug fix worth mentioning in the release notes
  • rn/documentation - A user-facing documentation change worth mentioning in the release notes

Should this PR be included in the next patch release?

Yes should be selected for bug fixes, documentation updates, and other small changes. No should be selected for new features and larger changes. If you're unsure about the release classification of this PR, leave this unchecked to let the maintainers decide.

What is a minor/patch release?
  • Minor release: a release that increments the second part of the version number (e.g., 1.2.0 -> 1.3.0).
    Bug fixes, doc updates and new features usually go into minor releases.
  • Patch release: a release that increments the third part of the version number (e.g., 1.2.0 -> 1.2.1).
    Bug fixes and doc updates usually go into patch releases.
  • Yes (this PR will be cherry-picked and included in the next patch release)
  • No (this PR will be included in the next minor release)

@xsh310 xsh310 force-pushed the stack/user-frustration-eval-run-tab-ui-polish branch from 47a55bc to 859f562 Compare December 15, 2025 03:55
@xsh310 xsh310 changed the title [MultiTurn][BuiltIn] Add coloring for UserFrustration eval results in the eval run tab [UserFrustration] Add coloring for UserFrustration eval results in the eval run tab Dec 15, 2025
const ERROR_BARCHART_BAR_COLOR = '#f09065';

const TAG_PASS_COLOR = '#02B30214'; // From tagBackgroundLime.
const TAG_WARNING_COLOR = '#FCEACA';
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm using the yellow200 for this

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

any reason not to use theme.colors.yellow200 directly? i see the other props use a function like (theme: ThemeType) => ...

Copy link
Collaborator

@daniellok-db daniellok-db Dec 16, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

also does this look good in dark mode? if not then let's definitely use the same pattern as the other color getters and define a separate dark mode color

export const COMPARE_TO_RUN_COLOR = '#FFAB00';

const PASS_BARCHART_BAR_COLOR = '#99DDB4';
const WARNING_BARCHART_BAR_COLOR = '#F7C58A';
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let me know if there's a recommended color value for this

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can we use theme colors instead?

icon?: string;
text?: string;
} | undefined => {
const builtInAssessment = BUILTIN_SCORER_ASSESSMENT_COLORS[assessmentInfo.name as BuiltInScorerAssessmentName];
Copy link
Collaborator Author

@xsh310 xsh310 Dec 15, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm currently checking with assessmentInfo.name which means this change won't work if user provides a custom name to the UserFrustration scorer. From what I'm seeing our, we don't have the scorer class information rn at this level and we might need some protocol change to acquire this information. I will explore that in a separate PR.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i think this is fine - users probably only change the name if they are customizing the instructions as well

@xsh310 xsh310 marked this pull request as ready for review December 15, 2025 04:30
@github-actions github-actions bot added area/evaluation MLflow Evaluation area/uiux Front-end, user experience, plotting, JavaScript, JavaScript dev server rn/none List under Small Changes in Changelogs. labels Dec 15, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Dec 15, 2025

Documentation preview for ee2a55e is available at:

More info
  • Ignore this comment if this PR does not change the documentation.
  • The preview is updated when a new commit is pushed to this PR.
  • This comment was created by this workflow run.
  • The documentation was built by this workflow run.

@xsh310 xsh310 force-pushed the stack/user-frustration-eval-run-tab-ui-polish branch from 859f562 to 96b51f1 Compare December 15, 2025 17:24
Copy link
Collaborator

@smoorjani smoorjani left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Love this! would block on Dan/Daniel for UI review, but end result looks great!

text?: string;
}
| undefined => {
const builtInAssessment = BUILTIN_SCORER_ASSESSMENT_COLORS[assessmentInfo.name as BuiltInScorerAssessmentName];
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we probably shouldn't have this as BuiltInScorerAssessmentName since we don't have all built in assessment names in the map. just having string here should be fine

@xsh310 xsh310 force-pushed the stack/user-frustration-eval-run-tab-ui-polish branch 3 times, most recently from a612e8b to a653e6a Compare December 16, 2025 00:48
@xsh310
Copy link
Collaborator Author

xsh310 commented Dec 16, 2025

Updated PR to address @danielseong1 's comments

@xsh310 xsh310 force-pushed the stack/user-frustration-eval-run-tab-ui-polish branch from a653e6a to 84e5f73 Compare December 16, 2025 02:41
@xsh310 xsh310 enabled auto-merge December 16, 2025 02:42
@xsh310 xsh310 disabled auto-merge December 16, 2025 03:02
@xsh310 xsh310 requested a review from daniellok-db December 16, 2025 04:10
Copy link
Collaborator

@daniellok-db daniellok-db left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

… the eval run tab

Signed-off-by: Xiang Shen <xshen.shc@gmail.com>
@xsh310 xsh310 force-pushed the stack/user-frustration-eval-run-tab-ui-polish branch from 84e5f73 to ee2a55e Compare December 16, 2025 05:24
@xsh310
Copy link
Collaborator Author

xsh310 commented Dec 16, 2025

Updated to PR to address @daniellok-db 's comment. Verified that dark mode with orange now looks good
image

@xsh310 xsh310 added the v3.8.0 label Dec 16, 2025
@xsh310 xsh310 enabled auto-merge December 16, 2025 05:27
@xsh310 xsh310 added this pull request to the merge queue Dec 16, 2025
Merged via the queue into mlflow:master with commit ea009cf Dec 16, 2025
58 checks passed
@xsh310 xsh310 deleted the stack/user-frustration-eval-run-tab-ui-polish branch December 16, 2025 06:04
WeichenXu123 pushed a commit to WeichenXu123/mlflow that referenced this pull request Dec 19, 2025
…e eval run tab (mlflow#19383)

Signed-off-by: Xiang Shen <xshen.shc@gmail.com>
WeichenXu123 pushed a commit that referenced this pull request Dec 19, 2025
…e eval run tab (#19383)

Signed-off-by: Xiang Shen <xshen.shc@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/evaluation MLflow Evaluation area/uiux Front-end, user experience, plotting, JavaScript, JavaScript dev server rn/none List under Small Changes in Changelogs. v3.8.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants