Mercurial > repos > adam-novak > hexagram

comparison hexagram-6ae12361157c/hexagram/hexagram.xml~ @ 0:1407e3634bcf draft default tip

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Uploaded r11 from test tool shed.
author adam-novak
date Tue, 22 Oct 2013 14:17:59 -0400
parents
children
comparison
equal deleted inserted replaced
-1:000000000000 0:1407e3634bcf
1 <?xml version="1.0"?>
2 <tool id="hexagram" name="Hexagram Visualization" version="0.1">
3 <description>Interactive hex grid clustering visualization</description>
4 <requirements>
5 <!--
6 Go get the drl-graph-layout package as defined in
7 tool_dependencies.xml
8 -->
9 <requirement type="package" version="1.1">drl-graph-layout</requirement>
10 <!--
11 And go get some Python modules that aren't standard.
12 -->
13 <requirement type="python-module">numpy</requirement>
14 <requirement type="python-module">scipy</requirement>
15 </requirements>
16 <!--
17 This is the command to run as a Cheetah template.
18 We do fancy iteration over multiple score matrices (see
19 ../plotting/xy_plot.xml).
20 -->
21 <command interpreter="python">hexagram.py
22 #for $i, $s in enumerate( $similarity )
23 "${s.similarity_matrix.file_name}"
24 #end for
25 #for $i, $s in enumerate ($similarity)
26 --names "${s.similarity_matrix.name}"
27 #end for
28 #for $i, $s in enumerate( $scores )
29 --scores "${s.score_matrix.file_name}"
30 #end for
31 #if $query:
32 --query "$query"
33 #end if
34 #if $colormaps
35 --colormaps "$colormaps"
36 #end if
37 --html "$output"
38 --directory "$output.files_path"
39 --truncation_edges $edges
40 #if $singletons
41 --include-singletons
42 #end if
43 #if $nostats
44 --no-stats
45 #end if
46 </command>
47 <inputs>
48 <repeat name="similarity" title="Similarity Matrices">
49 <param name="similarity_matrix" type="data" format="tabular"
50 label="Similarity matrix of signatures to visualize"/>
51 </repeat>
52 <repeat name="scores" title="Scores">
53 <param name="score_matrix" type="data" format="tabular"
54 label="Score matrix for signatures to visualize"/>
55 </repeat>
56 <param name="colormaps" type="data" format="text" optional="true"
57 label="Colormap configuration file"/>
58 <param name="edges" type="integer" value="10"
59 label="Number of edges to use per node"/>
60 <param name="query" type="text"
61 label="Name of query signature"
62 help="A signature name, or empty for no query"/>
63 <param name="singletons" type="boolean"
64 label="Keep unconnected singleton signatures"/>
65 <param name="nostats" type="boolean"
66 label="Skip calculation of heatmap clumpiness statistics"/>
67 </inputs>
68 <outputs>
69 <data name="output" label="Hexagram Visualization($edges edges)"
70 format="html" hidden="false"/>
71 </outputs>
72 <stdio>
73 <!--
74 The tool catches all errors and returns 1, or 0 if no errors
75 happened.
76 -->
77 <exit_code range="1" level="fatal"
78 description="Error in visualization generator (see below)" />
79 <exit_code range="2:" level="fatal" description="Unhandleable error" />
80 </stdio>
81 <help>
82
83 Hexagram Visualization
84 ======================
85
86 This tool produces a "hexagram visualization": an interactive Google Maps-based two-dimensional layout of the similarity matrix data, on a hexagonal grid, with the score matrix data represented as different available colorings of the hexagons. This visualization is an HTML web page with associated support files, and appears as the tool's output in your Galaxy history; to open it, click on the eyeball icon.
87
88 If, instead of a rich interactive Web application, you get a boring white page with some text on it, you probably have tool output sanitization on. Turn sanitization off in your universe_wsgi.ini, or download the visualization, unzip it, and open the HTML file it contains. If you want to use a downloaded visualization, you will need to open it in a browser other than Chrome (which, for security reasons, does not let local Web pages access local files programmatically).
89
90 Input Format
91 ------------
92
93 The tool takes three types of input files:
94
95 Similarity Matrix
96 +++++++++++++++++
97
98 The only required input file is a *similarity matrix*, which contains similarity information over a set of "samples" or "signatures". This file is a sparse matrix represented as three tab-delimited columns; the first two columns of each row contain the names of two signatures, and the last column contains a nonzero, non-negative floating-point "similarity" between them. No headers are used. Self-edges are permitted, and self-edges with a similarity of 1 will be added to every node if "Keep unconnected singleton signatures" is checked. The input similarity matrix need not describe a similarity graph that is connected, and similarity need not be transitive in any way.
99
100 Score Matrices
101 ++++++++++++++
102
103 You almost certainly want to run the tool with one or more *score matrices*, which specify some attribute data to overlay on the signature hexes once they are arranged. Any number of score matrices can be specified. Each score matrix is a TSV file; the first column contains sample names, and any other columns contain the values of attributes for those samples. Score matrices have a header line, which specifies some (unused) name for the column of sample names, and the name of the attribute described by each column of attribute data.
104
105 Attribute data may be continuous (floating-point numbers), categorical (non-negative integers), or binary (0 or 1). The visualizer assumes that each column is the most restrictive type that will fit the data given; a column with all 0.0s and 1.0s will be assumed to be binary, even if the user intended it to represent a continuous value. Categories in categorical columns are assumed to be numbered from 0, even if no 0s appear in the column.
106
107 Colormap Configuration File
108 +++++++++++++++++++++++++++
109
110 If you have categorical data to display, you probably want to write a *colormap configuration file* for it. Categorical data is displayed in the visualizer with one color per category; if you want to specify particular colors for each category, or names for each category (instead of the default labels of 0 through n), you need a colormap configuration file. Each line in this file should begin with the name of a categorical attribute, followed by, for each category used in that attribute, the category number, the desired name for the category, and a CSS color (like "white" or "#FFFFFF" or "rgb(255,255,255)) to use to represent that category. Fields on each line are separated by tab characters.
111
112 </help>
113 </tool>
114