Source

qmachine /

Filename Size Date modified Message
etc
share
src
tests
161 B
1.3 KB
1.3 KB
30.7 KB
3.1 KB

QMachine

QMachine (QM) is a web service that uses Quanah to create a distributed computer that can use ordinary web browsers as ephemeral nodes. It contains three main components: an API server, a web server, and a website. The API server and the web server are both implemented in Node.js and available for use in server environments via NPM. The API server supports CORS and configurable persistent storage for a variety of popular databases, including Apache CouchDB, MongoDB, PostgreSQL, Redis, and SQLite. The web server exists only to serve the website. The website functions as an example browser client for the QM API, and its implementation as static content written in HTML5, CSS, and JavaScript allows it to be served out of memory by the web server for high performance and used by ordinary web browsers for high portability. Parts of the browser client are installable via Twitter's Bower package manager, but I have only recently experimented with that. The analytical layer can also be used from MinervaJS and the TCGA Toolbox.

There are several project "mirrors" available on Bitbucket, GitHub, and Google Code. Various project statistics are available on GitHub and Ohloh, too.

I have done some preliminary investigation into app integration for

I have now submitted the first of several manuscripts I have been preparing for peer-reviewed academic journals. These reports will explain some of the design decisions behind QM, demonstrate the use of QM in scientific workflows, and elaborate on the future directions of QM. My labmates have finally convinced me that my "documentation as comments in the source code" approach is inadequate, and thus I have begun a wiki. I have also recently published a few screencasts on YouTube, one of which has been featured on the insideHPC and HPCwire news sites.