-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
An alternative visualizer for pipeline execution view #1766
Comments
I think there is certainly room for improvement with the execution index view though I am not sure I find the azure pipelines example very compelling. The tabs for "all" and "recent" are not a bad idea. One of the important things about the execution index (which doesn't really have a good analog in azure pipelines) is the ability to compare metrics across different experiments/executions. Currently, it assumes that plots should be combined for all selected executions. This is a bit over simplistic as operations can have multiple plots and pipelines can have multiple operations. It would be useful to give users manual control over the combining plots to help compare various metrics (probably with intelligent defaults). |
Hi, a little relevant question on pipeline visualization: |
@dustinjoe - Unfortunately, not :/ So far, we have been just numbering them if we would like to communicate an order. However, adding something like sorting alphabetically would be pretty simple if that would be sufficient. If that is of interest, feel free to open an issue! It would also be a pretty good first issue if you were interested in contributing; I would be happy to provide some guidance! |
This is related to #1747, but I think worth a mention here/ separate Issue. Here are my thoughts on enhancing
|
It might be nice to add an alternative to ExecutionIndex or enhance ExecutionIndex like the one in azure pipelines giving more holistic view/ additional information of a run. Again, this is a pretty vague in terms of specifics but definitely something we can work on.
The text was updated successfully, but these errors were encountered: