You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The purpose of this feature is to provide a way for users to select a part of their pipeline, change the parameters, and generate a run command for the terminal. This would contribute towards solving the reporting use case of Kedro-Viz(#1279).
pop up comes with table of list of used parameters and their current values.
These values are editable like in a spreadsheet.
When you make the changes and click apply, a new popup shows up with a constructed kedro run command.
You can copy this command and run in your terminal.
Context
Why is this change important to you? How would you use it? How can it benefit other users?
This will support the reporting use case but also increase collaboration between technical and non-technical stakeholders in a team. Users will be able to visualise outputs of a run, change those outputs and visualise the change, without having to leave the Kedro-VIz UI.
As mentioned in #1279, this will make Kedro-Viz a single-entry point for visualising outputs from a run and will also support non-technical users who need the insights, resulting in increased usage of Kedro-Viz.
Possible Implementation
This would be a pipeline selector for selection of nodes.
Backend would provide to the front end the list of current parameters and their values being used in that specific pipeline.
Frontend should visualise and enable the edit of these parameters.
Generate kedro run command with the changes.
Possible Alternatives
A future iteration would be running the updated parameters from Kedro-Viz and seeing the immediate result. But this puts Kedro-Viz in the orchestrator group, which is not the current product vision.
The text was updated successfully, but these errors were encountered:
Description
The purpose of this feature is to provide a way for users to select a part of their pipeline, change the parameters, and generate a run command for the terminal. This would contribute towards solving the reporting use case of Kedro-Viz(#1279).
It was also highlighted in the #1750 research.
The user journey could be:
Context
Why is this change important to you? How would you use it? How can it benefit other users?
This will support the reporting use case but also increase collaboration between technical and non-technical stakeholders in a team. Users will be able to visualise outputs of a run, change those outputs and visualise the change, without having to leave the Kedro-VIz UI.
As mentioned in #1279, this will make Kedro-Viz a single-entry point for visualising outputs from a run and will also support non-technical users who need the insights, resulting in increased usage of Kedro-Viz.
Possible Implementation
Possible Alternatives
A future iteration would be running the updated parameters from Kedro-Viz and seeing the immediate result. But this puts Kedro-Viz in the orchestrator group, which is not the current product vision.
The text was updated successfully, but these errors were encountered: