Run Detail Page Improvements
planned
Mattia
Enhance the user experience by improving the widgets on the run detail page without altering user flows.
The primary goals of this UI update are:
- Improve the entire page's layout by reorganizing the order of widgets and the information within them.
- Unify color and icon use to ensure consistency across the application.
Specifically:
- To enhance the usability and aesthetics of the "General" widget in run detail page, improvements will involve reordering and resizing elements, optimizing the widget for increased interactive intuitiveness, unifying icon styles to outline format, and introducing an expand/collapse functionality. This aims to address the visual imbalance caused by the increased elements such as resource labels, pipeline name, and optimization details within the widget.
- The current Process widget layout presents problems because the names can be too long and unreadable, the numeric value is unclear, and the progress bar lacks clarity. We aim to improve this by resizing and restyling the Process widget, providing an easy way to jump into tasks, and evaluate an overall progress indicator for added clarity.
- Improve the Status widget UI on the run detail page, enhancing accessibility by adjusting text color contrast, consolidating the use of colors, especially for the "Cached" status, and renaming the widget to accurately reflect its content: "Task status." These changes aim to enhance user experience and clarity in interpreting the widget information.
- The Tasks table enhancement is addressed in a separate effort.
Rob Newman
Merged in a post:
Make original params.json file from the launch config downloadable as file
F
Flamingo pink Python
Currently when customers run launches, either via platform or automation they run into failures and want to access the current
params.json
file. There are options to view the contents via the UI but users cannot download them as a file to retrieve and use later. Create a feature to download this file when looking at the runs page so that customers can download it via the UI and via scripts/API during automation.
F
Flamingo pink Python
Hi Rob, that is not the correct
params
. I need to original parameters that were provided by the user when they submitted the pipeline Run. The Parameters shown in the 'Parameters' tab is not the same. It includes a millions settings that were not provided by the user, but were instead derived dynamically (somehow?). It seems like the parameters that I need are still saved in the Platform, however, they are buried under the Run > Relaunch menu. These are the parameters I am trying to retrieve and save to file so that I can re-run the pipeline with the exact same settings. These parameters are not available from the Run Page directly, and they are not available from the
tw
cli.Rob Newman
Flamingo pink Python: Understood - thanks for the clarification. Looking into this now.
Rob Newman
My understanding is that this
params
file is a combination of (1) the original parameters provided by the user when submitting the pipeline Run, and (2) additional/expanded settings that are provided by the nextflow.config
file (for example, the reference genomes which are expanded in the Run results page). I'll research to see if the original params can be retrieved.F
Flamingo pink Python
Rob Newman thanks and also as an aside, considering that the desired params are retrievable from the "Relaunch" page, I guess the desired "feature" of getting these into a file somehow could be more flexible, let me know what you all think is the best way to handle it to make this as convenient as possible. Thanks
Rob Newman
Flamingo pink Python: Thanks for the update. We've confirmed that this is missing from the pipeline Run results page, and are currently determining level-of-effort and prioritization. In the meantime, I'm going to merge with the "Improved Runs page" FR.
Rob Newman
Flamingo pink Python: This has been available in Seqera Platform since v23.3.0. In the Run details page, select the parameters tab, and click the download button (see attached screenshot). You can also gather this information programmatically using the Tower CLI by running
tw runs dump -i <workflow_id> -w <org/wksp> -o <output_file>
. See the docs for further information.Rob Newman
I'll now close this feature request. Please comment if you have further questions.
Rob Newman
Merged in a post:
Platform"View Workflow Run" page needs to fill the webpage horizontally
F
Flamingo pink Python
sorry I am not a web dev so I am not 100% sure what the correct term for this is, but when you are viewing a single Workflow Run, the elements on the page are all constricted to a single narrow column on the screen.
I frequently want to take a Screenshot of the Run's page, and I want to be able to fit everything in the screenshot;
- run label + status box
- command line / parameters / config box
- General info box
- Status box
- Processes box
- Stats box
- Load / Utilization boxes
- a tiny portion of the top of the Tasks box
There is a lot of stuff on the page. I frequently need to fit
all
of it in a single Screenshot. Currently that is almost impossible, because you must scroll vertically to see everything. If I want to be able to fit all of these elements into a single Screenshot, I end up having to set my web browser Zoom level to 30% in order to fit everything, at which point all the text is too tiny to read, and I have a massive amount of empty white space in the screen on the sides. The thing is, there would be plenty of space on the screen to fit this all in one Screenshot, if the page's elements were not constricted to a single narrow vertical band in the center of the page. There should be some way to configure the web page to instead place the elements intelligently to fit the full horizontal space of the available web page. I believe this might be called the "responsive design" ?
Not sure what plans there are for the future UI updates but maybe this could hopefully be considered.
this ticket sounds related https://feedback.seqera.io/feature-requests/p/run-detail-page-improvements however I dont have any issue with the Widgets themselves, its just their layout on the page that is too constricted
Rob Newman
planned
Rob Newman
evaluating
Rob Newman
Merged in a post:
Draw the user's attention to runs that are "stuck" in a state
Rob Syme
It is possible to accidentally configure a run that will get "stuck" in a state where it will not submit jobs, or those jobs will never progress into a running state. Situation might include when submitting a GPU-requiring task to a queue that does not have GPUs, or submitting a job that requests more memory than is available.
These jobs will sit idle and consume resource. Once they fall off the first page on the "Runs" tab, it is possible that they go unnoticed. In such instances, it may be helpful to draw the user's attention to these misconfigured runs so that they can be cancelled, the resources cleaned up and the configuration error corrected.
Rob Newman
Inquisitive Reindeer: Thanks for your feedback. I'm merging your "Lexicographic/alphabetical sort of parameters in workflow runs" feature request into our existing
Run Detail Page Improvements
feature request which includes listing parameters in alphabetical order. The merge process automatically upvotes on your behalf.Rob Newman
Rob Newman
Merged in a post:
Workflow Run detail page improvements
L
Late Macaw
Suggested improvements on the Run detail page UI with the tabs on
Parameters
and Configuration
:Parameters tab:
- Add a search widget in the top right corner: if I need to find a specific parameter from a very long list, I can search for it and the resulting view should shrink like the task table or highlight it.
- List the parameters in alphabetical order
Configuration tab:
- Add a search widget in the top right corner: if I need to find a specific parameter from the very long resolved configuration list, I can search for it and the resulting view should shrink like the task table or highlight it.
- Add a Secretssection that displays the secret(s) used in the pipeline: Only thenameof the secret, not the value. If we havefoosecret andbaras the value, then something like:
secrets {
name = foo,
value = hidden
}
Load More
→