Skip to content
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

show_params input walking #1561

Merged
merged 2 commits into from
Jan 22, 2016
Merged

show_params input walking #1561

merged 2 commits into from
Jan 22, 2016

Conversation

carlfeberhard
Copy link
Contributor

From a use-case described by admins at GCC2015 (and worked shortly after but not committed till now): the ability to move backward in a line of jobs from job input dataset to job input dataset to find where a workflow or series of jobs went wrong.

With this change, when viewing a dataset's parameter info (the 'i' button), ...
screen shot 2016-01-21 at 4 21 35 pm

you can now click job parameters that are input datasets...
screen shot 2016-01-21 at 4 21 47 pm

and:

  • the history panel on the right will scroll to the input dataset
  • the center panel will load with that input dataset's job parameter info

screen shot 2016-01-21 at 4 22 16 pm

From there you can keep walking back to the initial datasets.

The original context of the request was the history structure view, but this is a convenience/easy-grab that may tide things over until that's worked on again.

…' button in the datasets of histories) that, when clicked, 1) scroll the history to the dataset shown and 2) open *that* datasets info/show_params in the center panel
@martenson
Copy link
Member

great feature and smooth implementation, as usual with @carlfeberhard
👍

guerler added a commit that referenced this pull request Jan 22, 2016
@guerler guerler merged commit 1275dfd into galaxyproject:dev Jan 22, 2016
@carlfeberhard carlfeberhard deleted the input-walking branch January 22, 2016 19:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants