-
Notifications
You must be signed in to change notification settings - Fork 1
June 13, 2017, Tuesday
Liya Wang edited this page Aug 1, 2017
·
4 revisions
- Workflow diagram bug or improvement
- If the workflow page in the central panel is replaced with other pages, workflow diagram is no longer accessible
- Job history can still be checked from the history panel so its not a big problem
- Workflow needs to be saved after completion
- Select the completed jobs and rebuild the workflow
- For live diagram, maybe we can display the workflow link (under user workflow)
- Add a status column to distinguish completed vs running
- Initial status of the workflow will determine the color of the nodes in workflow diagram
- For running workflow, name can be the workflow name + time, if starting from a saved workflow
- For running workflow, name can be temporary name + time, if starting from a group of jobs
- Also it seems there is a bug for updating the live diagram when the diagram is closed and reopened
- If the workflow page in the central panel is replaced with other pages, workflow diagram is no longer accessible
- Building workflows explicitly
- Shall we allow user to build workflow before executing any jobs
- Since we are pre-defining outputs
- We should be able to allow user to connect apps based on defined inputs and outputs
- Check: https://www.lab7.io/solutions/lab7-esp/#pipes
- Shall we allow user to build workflow before executing any jobs
- Building workflows without explicit output names
- One idea might be adding output id into the output name
- m_trait.txt --> trait_output_m_trait.txt
- Then m_trait.txt can be a variable so that it won't be replaced if brought together from two jobs using the same app
- Diagram and History panel can choose to display the name without output id
- One idea might be adding output id into the output name
- Support all Agave apps
- Under beta?