This box searches only this space. The box at the upper right searches the entire iPlant wiki.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

Team Name

Reetu and Friends


Team Members

Reetu Tuteja - Created the Sequenceserver2.0 app on Discovery Environment

Jennen Maryniak - presentation

Jiatian Wang - initial Makeflow and Work Queue scripts

Hayden Dunn

Erika Tapia - benchmarking and documentation

Andy Garcia

Nick Reppe


Project Summary:

CyVerse provides life scientists with a powerful computational infrastructure to handle huge datasets and complex analyses that enable data-driven discovery. CyVerse's extensible platforms provide data storage, bioinformatics tools, image analyses, cloud services, APIs, and more.


The Discovery Environment (DE) is a key product of the CyVerse cyber-infrastructure, providing a modern web interface for powerful computing. The visual and interactive computing environment (VICE) is the recently introduced feature within CyVerse’s Discovery Environment (DE) for running interactive apps.


Our midterm project is an implementation of CyVerse's Discovery Environment using an app we created via VICE within CyVerse. 

Project Description

Code Availability

Initial Scripts:


Sequences used were provided by Team BlastEasy :

Installing/Running Instructions

(Through Discovery Environment, open a SequenceServer app, upload a query through the input GUI on DE, run, and look at analysis.)?


Project Timeline/Plan


Benchmarking was ran by running the sequenceserver app we created in the Discovery Environment (DE) within CyVerse. Before launching the app, the number of cores was specified in the drop-down field "Number of threads":

The running analysis was accessed which allowed us to paste the protein sequences in Sequence Server to run BLAST:

All protein sequences ran through Sequence Server were 100 residues in length and the number of cores were pre-selected before launching the app analysis. A significant decrease in run-time was observed as more cores were involved in running queries. Running queries on 8 cores clearly reduces run-time as compared to running queries on simply 1 core. 


Number of Protein Sequences

Time (seconds)


Time (seconds)


Time (seconds)


Time (seconds)







  • No labels