qm 0.9.9 → 0.9.10

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. checksums.yaml +4 -4
  2. data/README.md +54 -0
  3. metadata +6 -4
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA1:
3
- metadata.gz: 6c4e753bb154bc34b04a458387888cb45aa3fef0
4
- data.tar.gz: 0fc6da4f2303e8a80cd8b008efb3d6226b2fb9fc
3
+ metadata.gz: 83adcdab59e4cd27b2beadbfe253f82df0866120
4
+ data.tar.gz: 0582a69bfd5d9d0c2ed586fbe8c46b1d59ae58f4
5
5
  SHA512:
6
- metadata.gz: 1d67d1446218b0301ea73a083581a94d6ea8fd2b696594fd93397a20f4446b8ab9c6649a355e44bd25e4d5651291b6c14dd38e04c16719078a8496cc875993ab
7
- data.tar.gz: ad820605e8c1bfff782ba1d4b9e299c8d576b43ac070c8163a3dd4f373d922609ea6b16fbde61ee2828779b04996b145713b653b5348a3483f3c6684841c9e6e
6
+ metadata.gz: 9c3b7df32b206f3dbe68aab85b117d594a37b56a4c04b1593b466539ebd896e62801f4fd12229f2fb8a3510c6d6f69639fc76cd8208cfd4fb6899925748007b4
7
+ data.tar.gz: 4ee87ce21ed00528c85d12b4d3aaab6c1b64eabf6c856a44bdd47d920f4ff8ee61ef55b82116000b3ba8ba0737867ea221259e9dcb1738c524663a9618ca8d1c
@@ -0,0 +1,54 @@
1
+ QMachine
2
+ ========
3
+
4
+ [QMachine](https://www.qmachine.org) (QM) is a web service that uses
5
+ [Quanah](http://wilkinson.github.io/quanah) to create a distributed computer
6
+ that can use ordinary web browsers as ephemeral nodes. It contains three main
7
+ components: an API server, a web server, and a website. The API server and the
8
+ web server are both implemented in [Node.js](http://nodejs.org) and available
9
+ for use in server environments via [NPM](https://npmjs.org/package/qm). The API
10
+ server supports [CORS](http://www.w3.org/TR/cors/) and configurable persistent
11
+ storage for a variety of popular databases, including
12
+ [Apache CouchDB](http://couchdb.apache.org/),
13
+ [MongoDB](http://www.mongodb.org/), [PostgreSQL](http://www.postgresql.org),
14
+ [Redis](http://redis.io), and [SQLite](http://www.sqlite.org). The web server
15
+ exists only to serve the website. The website functions as an example browser
16
+ client for the QM API, and its implementation as static content written in
17
+ [HTML5](http://www.whatwg.org/specs/web-apps/current-work/multipage/),
18
+ [CSS](http://www.w3.org/Style/CSS/Overview.en.html), and
19
+ [JavaScript](http://www.ecma-international.org/publications/files/ECMA-ST/Ecma-262.pdf) allows it to be served out of memory by the web server for high
20
+ performance and used by ordinary web browsers for high portability. Parts of
21
+ the browser client are installable via Twitter's
22
+ [Bower](http://twitter.github.io/bower/) package manager, but I have only
23
+ recently experimented with that. The analytical layer can also be used from
24
+ [MinervaJS](http://minervajs.org/site/index.html#!/view/qm) and the
25
+ [TCGA Toolbox](http://tcga.github.io/).
26
+
27
+ There are several project "mirrors" available on
28
+ [Bitbucket](https://bitbucket.org/wilkinson/qmachine),
29
+ [GitHub](https://github.com/wilkinson/qmachine), and
30
+ [Google Code](https://qmachine.googlecode.com). Various project statistics are
31
+ available on [GitHub](https://github.com/wilkinson/qmachine/graphs) and
32
+ [Ohloh](https://www.ohloh.net/p/qm), too.
33
+
34
+ I have done some preliminary investigation into app integration for
35
+
36
+ - [Google Chrome](https://chrome.google.com/webstore/detail/meagomakeegjimdibmlodmilfhplkjgp)
37
+ - [Facebook](http://apps.facebook.com/qmachine/)
38
+ - [Firefox Marketplace](https://marketplace.firefox.com/app/qmachine/)
39
+ - [Twitter](https://dev.twitter.com/apps/1755018/)
40
+
41
+ I have now submitted the first of several manuscripts I have been preparing for
42
+ peer-reviewed academic journals. These reports will explain some of the design
43
+ decisions behind QM, demonstrate the use of QM in scientific workflows, and
44
+ elaborate on the future directions of QM. My labmates have finally convinced me
45
+ that my "documentation as comments in the source code" approach is inadequate,
46
+ and thus I have begun a [wiki](https://wiki.qmachine.org). I have also recently
47
+ published a few screencasts on
48
+ [YouTube](http://www.youtube.com/playlist?list=PLijUCyE0Z0-8nLL5qJ__v-VB3ZoRxSubg),
49
+ one of which has been featured on the
50
+ [insideHPC](http://insidehpc.com/2013/03/09/video-qmachine-commodity-supercomputing-with-web-browsers/)
51
+ and
52
+ [HPCwire](http://www.hpcwire.com/hpcwire/2013-03-14/qmachine_combines_hpc_with_www.html)
53
+ news sites.
54
+
metadata CHANGED
@@ -1,22 +1,24 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: qm
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.9.9
4
+ version: 0.9.10
5
5
  platform: ruby
6
6
  authors:
7
7
  - Sean Wilkinson
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2013-04-13 00:00:00.000000000 Z
11
+ date: 2013-04-14 00:00:00.000000000 Z
12
12
  dependencies: []
13
- description: This is a [buggy?] port of QMachine from Node.js.
13
+ description: This is a *very incomplete* port of QMachine.
14
14
  email: sean@mathbiol.org
15
15
  executables: []
16
16
  extensions: []
17
- extra_rdoc_files: []
17
+ extra_rdoc_files:
18
+ - README.md
18
19
  files:
19
20
  - lib/qm.rb
21
+ - README.md
20
22
  homepage: https://www.qmachine.org
21
23
  licenses: []
22
24
  metadata: {}