-
Notifications
You must be signed in to change notification settings - Fork 1
April 10, 2018, Tuesday
Liya Wang edited this page Apr 10, 2018
·
1 revision
- SciTeam meeting
- Remove private category from the maizecode version
- Install maizecode version on halcott
- Prepare slides on how to build SciApps ready apps
- Demo (WBS)
- Added diagram rotation, and direct workflow link for sharing
- Support saving and retrieving a running workflow
- Support maxCardinality for arbitrary number of inputs
- Improved workflow engine by passing output ids as prefixes
- Science workflows (RNA-Seq + partial Meth + Variations?)
- Possible bugs/improvements for user version (temporarily held on brie)
- Form not loading from Agave, for inputs, values of all fields become null in app json from time to time (visible become null)
- Change checking to display if visible is null but default won't be displayed
- Agave issue? Apache issue (restart sometimes works)?
- Check with Cornel and Rion for possible solutions
- Login need to be formalized as AgaveToGo/iMicrobie
- Check with Rion
- Make apps public
- Form not loading from Agave, for inputs, values of all fields become null in app json from time to time (visible become null)
- Possible improvements for maizecode version (temporarily held on halcott)
- Remove the private category since all apps need to be shared with maizecode user
- Possible improvements for all sites
- Overall, how do we deal with failed workflow
- If one job failed, jobs depending on it will keep checking job status if in history panel
- Take turn to fail jobs if jobs it depends on failed
- Making public workflows
- All apps should be public (disable sharing for workflows contain private apps and display info message)
- Given that all apps in a workflow are made public, we need to release the workflow as public
- Click on 'Share', user gets a link
- We can add a button for 'Make workflow public'
- Email to [email protected] with workflow id
- We need to add app json, app list json for the app category (with a form?)
- Share it with maizecode user
- Overall, how do we deal with failed workflow