Notes:
Type of apps
Executable - user interface for command line tools (this is what we use for BioViz Connect)
VICE - Visual and Interactive Computing Environment
Apps Under Development - apps you the user are building
My Public Apps - apps you have that have been made public
High-Performance Computing - apps that use TACC resources
My Collections - can create groups of apps
The Documentation points to the example data in the DE that every app is supposed to have.
They default analysis name to the nameOfTheApp_analysis1
When you launch an analysis it immediately takes you to the analysis page(we did not do this in BioViz Connect since it would prevent a user from quickly launching multiple analyses).
I do like that they have an info icon that shows most of the settings used to run that analysis in the analysis history.
They also have a way to see the errors from failed analyses, but again, we made the BioViz Connect analyses as simple as possible, so unclear if useful.
Made a point on special characters not being allowed when running analysis. I'm pretty sure we encode all special characters so the can be run on analysis. I thought DE did the same.
VICE allows for applications that have a GUI.
JupyterLab and RStudio as a VICE app.
When I last talked with Jason Williams he mentioned trying to make IGB a VICE app.
VICE apps last for 48 hours and are then terminated.
Need to fill out an extra form to use VICE.
Building VICE apps also involves creating Docker container, but is easier than the executable apps (https://learning.cyverse.org/en/latest/tools_and_apps.html).
Can use a workflow to pipe one apps output through another app.
Click on Create Workflow, add apps, then match the outputs to the inputs -> this could be very useful for BioViz Connect. Would need to investigate further to see how we could set this up to work.
Notes:
Type of apps
Executable - user interface for command line tools (this is what we use for BioViz Connect)
VICE - Visual and Interactive Computing Environment
Apps Under Development - apps you the user are building
My Public Apps - apps you have that have been made public
High-Performance Computing - apps that use TACC resources
My Collections - can create groups of apps
The Documentation points to the example data in the DE that every app is supposed to have.
They default analysis name to the nameOfTheApp_analysis1
When you launch an analysis it immediately takes you to the analysis page(we did not do this in BioViz Connect since it would prevent a user from quickly launching multiple analyses).
I do like that they have an info icon that shows most of the settings used to run that analysis in the analysis history.
They also have a way to see the errors from failed analyses, but again, we made the BioViz Connect analyses as simple as possible, so unclear if useful.
Made a point on special characters not being allowed when running analysis. I'm pretty sure we encode all special characters so the can be run on analysis. I thought DE did the same.
VICE allows for applications that have a GUI.
JupyterLab and RStudio as a VICE app.
When I last talked with Jason Williams he mentioned trying to make IGB a VICE app.
VICE apps last for 48 hours and are then terminated.
Need to fill out an extra form to use VICE.
Building VICE apps also involves creating Docker container, but is easier than the executable apps (https://learning.cyverse.org/en/latest/tools_and_apps.html).
Can use a workflow to pipe one apps output through another app.
Click on Create Workflow, add apps, then match the outputs to the inputs -> this could be very useful for BioViz Connect. Would need to investigate further to see how we could set this up to work.