[UserFrustration] Add coloring for UserFrustration eval results in the eval run tab#19383
Conversation
47a55bc to
859f562
Compare
| const ERROR_BARCHART_BAR_COLOR = '#f09065'; | ||
|
|
||
| const TAG_PASS_COLOR = '#02B30214'; // From tagBackgroundLime. | ||
| const TAG_WARNING_COLOR = '#FCEACA'; |
There was a problem hiding this comment.
I'm using the yellow200 for this
There was a problem hiding this comment.
any reason not to use theme.colors.yellow200 directly? i see the other props use a function like (theme: ThemeType) => ...
There was a problem hiding this comment.
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'; |
There was a problem hiding this comment.
Let me know if there's a recommended color value for this
There was a problem hiding this comment.
can we use theme colors instead?
| icon?: string; | ||
| text?: string; | ||
| } | undefined => { | ||
| const builtInAssessment = BUILTIN_SCORER_ASSESSMENT_COLORS[assessmentInfo.name as BuiltInScorerAssessmentName]; |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
i think this is fine - users probably only change the name if they are customizing the instructions as well
|
Documentation preview for ee2a55e is available at: More info
|
859f562 to
96b51f1
Compare
smoorjani
left a comment
There was a problem hiding this comment.
Love this! would block on Dan/Daniel for UI review, but end result looks great!
mlflow/server/js/src/shared/web-shared/genai-traces-table/utils/Colors.ts
Show resolved
Hide resolved
| text?: string; | ||
| } | ||
| | undefined => { | ||
| const builtInAssessment = BUILTIN_SCORER_ASSESSMENT_COLORS[assessmentInfo.name as BuiltInScorerAssessmentName]; |
There was a problem hiding this comment.
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
a612e8b to
a653e6a
Compare
|
Updated PR to address @danielseong1 's comments |
a653e6a to
84e5f73
Compare
daniellok-db
left a comment
There was a problem hiding this comment.
lg after https://github.com/mlflow/mlflow/pull/19383/files#r2621704251 is addressed
… the eval run tab Signed-off-by: Xiang Shen <xshen.shc@gmail.com>
84e5f73 to
ee2a55e
Compare
|
Updated to PR to address @daniellok-db 's comment. Verified that dark mode with orange now looks good |
…e eval run tab (mlflow#19383) Signed-off-by: Xiang Shen <xshen.shc@gmail.com>
…e eval run tab (#19383) Signed-off-by: Xiang Shen <xshen.shc@gmail.com>

🥞 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
UserFrustrationjudge is not highlighted and difficult to read (ML-60165).This PR
Add coloring for
UserFrustrationbuilt-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?
Manual Test
Does this PR require documentation update?
Release Notes
Is this a user-facing change?
What component(s), interfaces, languages, and integrations does this PR affect?
Components
area/tracking: Tracking Service, tracking client APIs, autologgingarea/models: MLmodel format, model serialization/deserialization, flavorsarea/model-registry: Model Registry service, APIs, and the fluent client calls for Model Registryarea/scoring: MLflow Model server, model deployment tools, Spark UDFsarea/evaluation: MLflow model evaluation features, evaluation metrics, and evaluation workflowsarea/gateway: MLflow AI Gateway client APIs, server, and third-party integrationsarea/prompts: MLflow prompt engineering features, prompt templates, and prompt managementarea/tracing: MLflow Tracing features, tracing APIs, and LLM tracing functionalityarea/projects: MLproject format, project running backendsarea/uiux: Front-end, user experience, plotting, JavaScript, JavaScript dev serverarea/build: Build and test infrastructure for MLflowarea/docs: MLflow documentation pagesHow 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" sectionrn/breaking-change- The PR will be mentioned in the "Breaking Changes" sectionrn/feature- A new user-facing feature worth mentioning in the release notesrn/bug-fix- A user-facing bug fix worth mentioning in the release notesrn/documentation- A user-facing documentation change worth mentioning in the release notesShould this PR be included in the next patch release?
Yesshould be selected for bug fixes, documentation updates, and other small changes.Noshould 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?
Bug fixes, doc updates and new features usually go into minor releases.
Bug fixes and doc updates usually go into patch releases.