[Feature] Update website for launch diff #37
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request updates the website to visualize the new
launch_diff
event data generated by the parser. It introduces several new React components to display complex diff information in a user-friendly way. The mainKernelOverview
page is now much more powerful, allowing users to see not just the compilation details of a kernel, but also a detailed breakdown of how its parameters and arguments changed across multiple launches.Detailed Changes
New Components
ArgumentViewer.tsx
: A new component to display kernel arguments in a structured and readable format.DiffViewer.tsx
: A versatile component to visualize thelaunch_diff
data. It can render different types of diffs, including argument diffs, value distributions, and simple summaries.StackDiffViewer.tsx
: A specialized component for displaying differences in stack traces between launches.Page Updates
KernelOverview.tsx
:launch_diff
information. It shows total launches, which parameters were constant, and which ones varied, using the newArgumentViewer
andDiffViewer
components.Data Loading Logic
dataLoader.ts
:launch_diff
event type.processKernelData
now uses a two-pass approach. The first pass gathers all compilation events, and the second pass attaches the correspondinglaunch_diff
data. This ensures that the launch analysis is correctly associated with each kernel.LogEntry
,ProcessedKernel
) have been updated to include thelaunchDiff
data.