[rocprofiler-compute] Fix kernel/dispatch filtering

[vedithal-amd]

Motivation

Fix kernel/dispatch filtering in GUI

Technical Details

• Fix kernel/dispatch filtering in GUI

• Fix dispatch filtering in analyze mode where a range of dispatch ids is provided like --dispatch "> 2"

• Gracefully handle N/A values in GUI

• Ensure workload path is valid before using it in GUI

JIRA ID

AIPROFCOMP-85

Test Plan

Open occupancy workload profile output in GUI mode.
Select empty kernel.

Test Result

Ensure no errors output in console.

Submission Checklist

• Look over the contributing guidelines at https://github.com/ROCm/ROCm/blob/develop/CONTRIBUTING.md#pull-requests.

[Copilot]

Pull request overview

This PR fixes kernel and dispatch filtering issues in the GUI analyzer by preventing command-line filters from conflicting with GUI frontend dropdown menus, handling N/A values consistently, and ensuring proper path validation.

• Disallows --kernel and --dispatch command-line options when using --gui mode, directing users to use GUI dropdown menus instead
• Updates N/A value handling from empty string checks ("") to explicit "N/A" string checks in chart generation functions
• Moves workload path initialization from constructor to pre_processing() method to ensure path validation occurs first

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
gui.py	Updates chart generation functions to handle "N/A" values instead of empty strings when processing metrics
analysis_webui.py	Moves dest_dir initialization from __init__() to pre_processing() to ensure path is validated before use
analysis_base.py	Adds validation to prevent using --kernel or --dispatch options with --gui mode
standalone-gui.rst	Adds documentation note explaining that kernel/dispatch filtering should be done via GUI dropdowns, not command-line options
CHANGELOG.md	Documents the fix for kernel/dispatch filtering in GUI mode

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[xuchen-amd]

Looks good! Please add unit tests for this new override.

[xuchen-amd]

Looks good! Please add unit tests for this new override.

For CLI at least, we don't seem to have proper GUI tests atm

[feizheng10]

Well, to make it simple, I could accept the current solution.
However, it is a valid case that: User might want to filter out specific dispatches from a single kernel. For example, -k 1 --dispatch >3

[vedithal-amd]

However, it is a valid case that: User might want to filter out specific dispatches from a single kernel. For example, -k 1 --dispatch >3

@feizheng10 , this is still possible, in this case we will just filter for dispatch 3 and ignore kernel, since fixing dispatch id(s) already fixes kernel, let me know if there are any questions

[feizheng10]

However, it is a valid case that: User might want to filter out specific dispatches from a single kernel. For example, -k 1 --dispatch >3

@feizheng10 , this is still possible, in this case we will just filter for dispatch 3 and ignore kernel, since fixing dispatch id(s) already fixes kernel, let me know if there are any questions

dispatches could be a range or set. Ignoring kernel seems not meet the case:
Think about a mocked workload repeat calling k0, k1, k2 1000 times. User is interested in only filtering out k1 invocations after 21. There are 2 ways the users could specify: (1) He/she knows and specifies exactly which dispatches targeted, (2) -k 1 --dispatch >=21. I 'd guess user would prefer (2)

[vedithal-amd]

However, it is a valid case that: User might want to filter out specific dispatches from a single kernel. For example, -k 1 --dispatch >3

@feizheng10 , this is still possible, in this case we will just filter for dispatch 3 and ignore kernel, since fixing dispatch id(s) already fixes kernel, let me know if there are any questions

dispatches could be a range or set. Ignoring kernel seems not meet the case: Think about a mocked workload repeat calling k0, k1, k2 1000 times. User is interested in only filtering out k1 invocations after 21. There are 2 ways the users could specify: (1) He/she knows and specifies exactly which dispatches targeted, (2) -k 1 --dispatch >=21. I 'd guess user would prefer (2)

Hi @feizheng10 ,

I agree with you, since dispatch filtering can be a range (e.g. > 2) we cannot ignore kernel filtering. I have reverted my changes for ignoring kernel filtering.

However, I noticed that dispatch filtering using a range (e.g. > 2) was not working due to a bug, which I have fixed now.

Can you please review the changes again?

Thanks,
Vignesh

[cfallows-amd]

Retested GUI mode, no issues starting with dispatch or kernel filter, and then adding/removing in actual gui mode once loaded in browser. Approving.