{"id":2635,"date":"2015-07-02T21:11:38","date_gmt":"2015-07-02T21:11:38","guid":{"rendered":"https:\/\/notebooks.dataone.org\/?p=2635"},"modified":"2019-05-24T18:05:41","modified_gmt":"2019-05-24T18:05:41","slug":"week-6-presentation-week","status":"publish","type":"post","link":"https:\/\/notebooks.dataone.org\/workflow-view\/week-6-presentation-week\/","title":{"rendered":"Week 6: Presentation Week"},"content":{"rendered":"
This week I had a presentation with a few Biology researchers from UIUC. I would be presenting the GUI I have created so far after the Yes Workflow team presented our project to several researchers who are interested in working and displaying their own scripts into workflows. Although having been on the team for nearly 2 months now, I learned a lot during the meeting about Yes Workflow, such as the motivation behind it, the several uses for it in the future, as well as hearing some researchers talk about some of the advantages it could provide them.<\/p>\n
Aside from the presentation, I worked with updating rendered graphs in the GUI once the Watchdog detected an update within scripts from the local directory. The Watchdog API would look only at those files that have been processed through Yes Workflow and once a modification had been made to a file, the graph would be re-rendered. In addition to this, I added functionality to zoom in and zoom out of the graphs that have been rendered so that the user can have a more optimal view of their workflow scripts.<\/a><\/p>\n","protected":false},"excerpt":{"rendered":" This week I had a presentation with a few Biology researchers from UIUC. I would be presenting the GUI I have created so far after the Yes Workflow team presented our project to several researchers who are interested in working and displaying their own scripts into workflows. Although having been Continue reading Week 6: Presentation Week<\/span>