Skip to content
a platform for the collection, storage, retrieval, and analysis of experimental data for laboratory workflows
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
data/HLA Import Viroverse code for public development Jan 24, 2019
devel Dump sequence notes for ViroDB May 29, 2019
etc
lib Fix execution of quality command-line tool Jun 13, 2019
root
schema Migrate sequence notes to a proper table May 29, 2019
scripts
sql
t Move all non-runtime configuration into root-level viroverse.conf May 17, 2019
vendor/mullins
.gitattributes Import Viroverse code for public development Jan 24, 2019
.gitignore
LICENSE
Makefile
README.md
THIRDPARTY Add MIT license and third party license details Jan 31, 2019
Vagrantfile Import Viroverse code for public development Jan 24, 2019
app.psgi Import Viroverse code for public development Jan 24, 2019
cpanfile Change configuration interface to use Config::Any May 16, 2019
cpanfile.snapshot Import Viroverse code for public development Jan 24, 2019
logger.conf
package.json Import Viroverse code for public development Jan 24, 2019
sqitch.conf
viroverse.conf Add simple root redirection logic May 30, 2019
vv Import Viroverse code for public development Jan 24, 2019
yarn.lock Bump canvas from 1.6.9 to 1.6.13 Jun 5, 2019

README.md

Viroverse

Viroverse is a platform for the collection, storage, retrieval, and analysis of experimental data for laboratory workflows. Developed in-house for twelve years, it serves as the principal data store for HIV sequencing experiments conducted in the Mullins Lab. Viroverse currently houses tens of thousands of viral nucleotide sequences, together with comprehensive metadata about their creation including PCR protocols, gel images, subject clinical data, and more. Learn more about Viroverse at https://viroverse.washington.edu.

The initial public release of Viroverse has many rough edges and very little documentation. If you’re interested in using Viroverse in production after trying it out in dev mode, please reach out to us so we can engage one-on-one to help you out.

Help us fund Viroverse!

Development of Viroverse has been supported by the US National Institutes of Health grants P01AI057005, R01AI111806, R01AI125026, R21AI122361, R37AI047734, and R21AI087161 to Jim Mullins and P30AI027757 to the University of Washington Center for AIDS Research.

You can help us maintain funding for Viroverse by letting us know when you give Viroverse a try or adopt it for use in your lab. We very much appreciate hearing from you.

Getting Started

The easiest way to run Viroverse in a development environment is to start a local virtual machine using Vagrant and VirtualBox. After installing VirtualBox and Vagrant, running vagrant up in the root of a clone of this repository will start and provision a development VM. This will take quite some time! The provisioning script will install dependencies, create a database, and if all goes well, create a user account named after your username on the host system. To run the development server, log in to the VM with vagrant ssh, enter the /home/vagrant/viroverse directory, and run REMOTE_USER=username ./vv plackup, replacing username with your desktop login name. The application should start and its web interface should be available by browsing to http://192.168.0.2:5000 from your desktop.

You can’t perform that action at this time.