root/galaxy-central/tools/data_source/upload.xml

リビジョン 2, 9.0 KB (コミッタ: hatakeyama, 14 年 前)

import galaxy-central

行番号 
1<?xml version="1.0"?>
2
3<tool name="Upload File" id="upload1" version="1.1.1">
4  <description>
5    from your computer 
6  </description>
7  <action module="galaxy.tools.actions.upload" class="UploadToolAction"/>
8  <command interpreter="python">
9      upload.py $GALAXY_ROOT_DIR $GALAXY_DATATYPES_CONF_FILE $paramfile
10    #set $outnum = 0
11    #while $varExists('output%i' % $outnum):
12        #set $output = $getVar('output%i' % $outnum)
13        #set $outnum += 1
14        ${output.dataset.dataset.id}:${output.files_path}:${output}
15    #end while
16  </command>
17  <inputs nginx_upload="true">
18    <param name="file_type" type="select" label="File Format" help="Which format? See help below">
19      <options from_parameter="tool.app.datatypes_registry.upload_file_formats" transform_lines="[ &quot;%s%s%s&quot; % ( line, self.separator, line ) for line in obj ]">
20        <column name="value" index="1"/>
21        <column name="name" index="0"/>
22        <filter type="sort_by" column="0"/>
23        <filter type="add_value" name="Auto-detect" value="auto" index="0"/>
24      </options>
25    </param>
26    <param name="async_datasets" type="hidden" value="None"/>
27    <upload_dataset name="files" title="Specify Files for Dataset" file_type_name="file_type" metadata_ref="files_metadata">
28      <param name="file_data" type="file" size="30" label="File" ajax-upload="true" help="TIP: For NGS and other large files (>~2GB), uploading via HTTP/FTP URL (below) is the most reliable method.">
29        <validator type="expression" message="You will need to reselect the file you specified (%s)." substitute_value_in_message="True">not ( ( isinstance( value, unicode ) or isinstance( value, str ) ) and value != "" )</validator> <!-- use validator to post message to user about needing to reselect the file, since most browsers won't accept the value attribute for file inputs -->
30      </param>
31      <param name="url_paste" type="text" area="true" size="5x35" label="URL/Text" help="Here you may specify a list of URLs (one per line) or paste the contents of a file."/>
32      <param name="space_to_tab" type="select" display="checkboxes" multiple="True" label="Convert spaces to tabs" help="Use this option if you are entering intervals by hand.">
33        <option value="Yes">Yes</option>
34      </param>
35    </upload_dataset>
36    <param name="dbkey" type="genomebuild" label="Genome" />
37    <conditional name="files_metadata" title="Specify metadata" value_from="self:app.datatypes_registry.get_upload_metadata_params" value_ref="file_type" value_ref_in_group="False" />
38    <!-- <param name="other_dbkey" type="text" label="Or user-defined Genome" /> -->
39  </inputs>
40  <help>
41 
42**Auto-detect**
43
44The system will attempt to detect Axt, Fasta, Fastqsolexa, Gff, Gff3, Html, Lav, Maf, Tabular, Wiggle, Bed and Interval (Bed with headers) formats. If your file is not detected properly as one of the known formats, it most likely means that it has some format problems (e.g., different number of columns on different rows). You can still coerce the system to set your data to the format you think it should be.  You can also upload compressed files, which will automatically be decompressed.
45
46-----
47
48**Ab1**
49
50A binary sequence file in 'ab1' format with a '.ab1' file extension.  You must manually select this 'File Format' when uploading the file.
51
52-----
53
54**Axt**
55
56blastz pairwise alignment format.  Each alignment block in an axt file contains three lines: a summary line and 2 sequence lines.  Blocks are separated from one another by blank lines.  The summary line contains chromosomal position and size information about the alignment. It consists of 9 required fields.
57
58-----
59
60**Bam**
61
62A binary file compressed in the BGZF format with a '.bam' file extension.
63
64-----
65
66**Bed**
67
68* Tab delimited format (tabular)
69* Does not require header line
70* Contains 3 required fields:
71
72  - chrom - The name of the chromosome (e.g. chr3, chrY, chr2_random) or contig (e.g. ctgY1).
73  - chromStart - The starting position of the feature in the chromosome or contig. The first base in a chromosome is numbered 0.
74  - chromEnd - The ending position of the feature in the chromosome or contig. The chromEnd base is not included in the display of the feature. For example, the first 100 bases of a chromosome are defined as chromStart=0, chromEnd=100, and span the bases numbered 0-99.
75
76* May contain 9 additional optional BED fields:
77
78  - name - Defines the name of the BED line. This label is displayed to the left of the BED line in the Genome Browser window when the track is open to full display mode or directly to the left of the item in pack mode.
79  - score - A score between 0 and 1000. If the track line useScore attribute is set to 1 for this annotation data set, the score value will determine the level of gray in which this feature is displayed (higher numbers = darker gray).
80  - strand - Defines the strand - either '+' or '-'.
81  - thickStart - The starting position at which the feature is drawn thickly (for example, the start codon in gene displays).
82  - thickEnd - The ending position at which the feature is drawn thickly (for example, the stop codon in gene displays).
83  - itemRgb - An RGB value of the form R,G,B (e.g. 255,0,0). If the track line itemRgb attribute is set to "On", this RBG value will determine the display color of the data contained in this BED line. NOTE: It is recommended that a simple color scheme (eight colors or less) be used with this attribute to avoid overwhelming the color resources of the Genome Browser and your Internet browser.
84  - blockCount - The number of blocks (exons) in the BED line.
85  - blockSizes - A comma-separated list of the block sizes. The number of items in this list should correspond to blockCount.
86  - blockStarts - A comma-separated list of block starts. All of the blockStart positions should be calculated relative to chromStart. The number of items in this list should correspond to blockCount.
87
88* Example::
89
90    chr22 1000 5000 cloneA 960 + 1000 5000 0 2 567,488, 0,3512
91    chr22 2000 6000 cloneB 900 - 2000 6000 0 2 433,399, 0,3601
92
93-----
94
95**Fasta**
96
97A sequence in FASTA format consists of a single-line description, followed by lines of sequence data.  The first character of the description line is a greater-than (">") symbol in the first column.  All lines should be shorter than 80 characters::
98
99    >sequence1
100    atgcgtttgcgtgc
101    gtcggtttcgttgc
102    >sequence2
103    tttcgtgcgtatag
104    tggcgcggtga
105
106-----
107
108**FastqSolexa**
109
110FastqSolexa is the Illumina (Solexa) variant of the Fastq format, which stores sequences and quality scores in a single file::
111
112    @seq1 
113    GACAGCTTGGTTTTTAGTGAGTTGTTCCTTTCTTT 
114    +seq1 
115    hhhhhhhhhhhhhhhhhhhhhhhhhhPW@hhhhhh 
116    @seq2 
117    GCAATGACGGCAGCAATAAACTCAACAGGTGCTGG 
118    +seq2 
119    hhhhhhhhhhhhhhYhhahhhhWhAhFhSIJGChO
120   
121Or::
122
123    @seq1
124    GAATTGATCAGGACATAGGACAACTGTAGGCACCAT
125    +seq1
126    40 40 40 40 35 40 40 40 25 40 40 26 40 9 33 11 40 35 17 40 40 33 40 7 9 15 3 22 15 30 11 17 9 4 9 4
127    @seq2
128    GAGTTCTCGTCGCCTGTAGGCACCATCAATCGTATG
129    +seq2
130    40 15 40 17 6 36 40 40 40 25 40 9 35 33 40 14 14 18 15 17 19 28 31 4 24 18 27 14 15 18 2 8 12 8 11 9
131   
132-----
133
134**Gff**
135
136GFF lines have nine required fields that must be tab-separated.
137
138-----
139
140**Gff3**
141
142The GFF3 format addresses the most common extensions to GFF, while preserving backward compatibility with previous formats.
143
144-----
145
146**Interval (Genomic Intervals)**
147
148- Tab delimited format (tabular)
149- File must start with definition line in the following format (columns may be in any order).::
150
151    #CHROM START END STRAND
152
153- CHROM - The name of the chromosome (e.g. chr3, chrY, chr2_random) or contig (e.g. ctgY1).
154- START - The starting position of the feature in the chromosome or contig. The first base in a chromosome is numbered 0.
155- END - The ending position of the feature in the chromosome or contig. The chromEnd base is not included in the display of the feature. For example, the first 100 bases of a chromosome are defined as chromStart=0, chromEnd=100, and span the bases numbered 0-99.
156- STRAND - Defines the strand - either '+' or '-'.
157
158- Example::
159
160    #CHROM START END   STRAND NAME COMMENT
161    chr1   10    100   +      exon myExon
162    chrX   1000  10050 -      gene myGene
163
164-----
165
166**Lav**
167
168Lav is the primary output format for BLASTZ.  The first line of a .lav file begins with #:lav..
169
170-----
171
172**MAF**
173
174TBA and multiz multiple alignment format.  The first line of a .maf file begins with ##maf. This word is followed by white-space-separated "variable=value pairs". There should be no white space surrounding the "=".
175
176-----
177
178**Scf**
179
180A binary sequence file in 'scf' format with a '.scf' file extension.  You must manually select this 'File Format' when uploading the file.
181
182-----
183
184**Sff**
185
186A binary file in 'Standard Flowgram Format' with a '.sff' file extension.
187
188-----
189
190**Tabular (tab delimited)**
191
192Any data in tab delimited format (tabular)
193
194-----
195
196**Wig**
197
198The wiggle format is line-oriented.  Wiggle data is preceded by a track definition line, which adds a number of options for controlling the default display of this track.
199
200-----
201
202**Other text type**
203
204Any text file
205
206  </help>
207</tool>
Note: リポジトリブラウザについてのヘルプは TracBrowser を参照してください。