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
{{ message }}
This repository has been archived by the owner on Oct 16, 2023. It is now read-only.
It would be nice to have some custom text to help identify each run (in the runs view). At the moment it can be a bit difficult to relate runs from their run name (eg fancy_newton) to what the analysis actually is. Tags could be a way of doing it but it seems there is a low limit on the number of available tags.
Basically I suggest some short field in the runs view that looked like: "patient 3658, WGS..." that helps quickly identify the run.
The text was updated successfully, but these errors were encountered:
Question and a suggestion:
Do the names of each run in nf-tower need to be unique? If I'm iteratively working on a pipeline, sometimes I'll run the same configuration multiple times, so this would be good to know.
And, in addition to specifying the run name, I would *love* the ability to specify tags with each run in that run's config file. It would be especially helpful when developing, as I could attach a tag for each tool. This would allow me to search through past runs to see how the tool performs under different configurations and with different samples.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It would be nice to have some custom text to help identify each run (in the runs view). At the moment it can be a bit difficult to relate runs from their run name (eg fancy_newton) to what the analysis actually is. Tags could be a way of doing it but it seems there is a low limit on the number of available tags.
Basically I suggest some short field in the runs view that looked like: "patient 3658, WGS..." that helps quickly identify the run.
The text was updated successfully, but these errors were encountered: