bio-phyta 0.9.1 → 0.9.2

Sign up to get free protection for your applications and to get access to all the features.
data/Gemfile CHANGED
@@ -4,7 +4,7 @@ source "http://rubygems.org"
4
4
 
5
5
  # Runtime dependencies
6
6
  gem "bio", ">= 1.4.2"
7
- gem "mysql", ">= 2.8.1"
7
+ gem "mysql2"
8
8
  # For JRuby: gem "mysql", "~> 2.8.1"
9
9
  gem "sequel", ">= 3.28.0"
10
10
  gem "fastercsv", ">= 1.5.4" # only for 1.8.7
@@ -1,6 +1,327 @@
1
1
  = bio-phyta
2
2
 
3
- Description goes here.
3
+ PhyTA is a BioRuby program specifically designed for identifying and removing from Expressed Sequence Tag data contaminant sequences from other (non-target) species. PhyTA assigns a higher taxonomic rank to EST sequences based on their BLAST annotation, performs taxonomy-based sequence sorting and constructs a contamination-free sub-library.
4
+ It consists of the following tools:
5
+
6
+ [phyta-assign] Is in charge of the higher taxonomic rank sequence annotation.
7
+
8
+ [phyta-split] Identifies putative contaminant sequences based on the higher taxonomic rank annotation and user-specified criteria.
9
+
10
+ [phyta-extract] Constructs two sub-libraries: a “clean” sub-library that consists of annotated sequences from the target species and a “contaminant” one that includes putative contaminant sequences.
11
+
12
+ [phyta-setup-taxonomy-db] Facilitates setting up a local copy of the NCBI taxonomy database.
13
+
14
+ The detailed description of these tool's function is provided below.
15
+
16
+ All PhyTA scripts are written in Ruby 1.8.7 and are delivered as a Ruby gem. PhyTA has been tested with MRI 1.8.7 and 1.9.2.
17
+
18
+ To install PhyTA simply type:
19
+
20
+ gem install bio-phyta
21
+
22
+ PhyTA requires Ruby 1.8.7 or higher and a MySQL database. See the "Installation" section for more information.
23
+
24
+ == phyta-assign
25
+
26
+ phyta-assignparses the NCBI BLASTplus XML format output, assigns a higher taxonomic rank to ESTs based on the BLAST annotation and stores attributes of BLASTplus and the taxonomy assignments in tabular form as a CSV file.
27
+ To generate an input for phyta-assign, a large set of query sequences is compared to an NCBI database standard stand-alone or network-client BLASTplus programs.
28
+
29
+ An example the BLASTplus command for generating input for phyta-assign is:
30
+
31
+ blastx -query Corticium_candelabrum.fasta -db BLASTDB/nr -evalue 0.0001 -max_target_seqs 3 -out Corticium_candelabrum_blast5.xml -outfmt 5
32
+
33
+ where the blast5.xml file can be used as an input for phyta-assign.
34
+
35
+ The output of phyta-assign contains:
36
+
37
+ 1. Query sequence ID and the following information for the three top BLAST hits:
38
+ 2. accession number
39
+ 3. sgi
40
+ 4. e-value
41
+ 5. species name
42
+ 6. subject annotation
43
+ 7. Subject score
44
+ 8. Higher rank (e.g. Kingdom) taxonomy information
45
+
46
+ An example output file could look like this:
47
+
48
+ AW3C1;ACR38454;238014838;3.34982954962278e-19;Zea mays;unknown;78.5665508561758;Viridiplantae
49
+ AW3C1;XP_002489117;253761439;1.33094019753946e-18;Sorghum bicolor;hypothetical protein SORBIDRAFT_0057s002150;76.6405529765891;Viridiplantae
50
+ AW3C1;XP_002488963;253760039;1.23820662046332e-15;Sorghum bicolor;hypothetical protein SORBIDRAFT_1150s002010;66.6253640027379;Viridiplantae
51
+ AW5C3;XP_001629010;156372369;1.85315736381546e-09;Nematostella vectensis;predicted protein;66.2401644268205;Metazoa
52
+
53
+ As you see the first three entries are the three best BLAST hits for the query sequence AW3C1. They all get assigned to the Phylum Viridiplantae. The second query sequence only has one hit from the species <i>Nematostella vectensis</i> which gets assigned to the Kingdom Metazoa.
54
+
55
+ The higher rank taxonomy is assigned based on species name acquired from the hit gi number and NCBI taxonomy information. The default list of the higher rank taxonomic groups used by phyta-assign is provided in the built-in Taxonomy filter I. The default taxonomy list and instructions for creating a custom filter are provided below in the section "Custom filters".
56
+
57
+ === Usage
58
+
59
+ Phyta-assign takes the following command line arguments:
60
+
61
+ [\--input-file, -i] The output of the BLASTplus alignment in XML format
62
+
63
+ [\--output-file, -o] The name of the output table in CSV format
64
+
65
+ [\--database-server, -d] Optional: The address of the MySQL database server (default: localhost)
66
+
67
+ [\--database-user, -u] Optional: The name of the database user (default: root)
68
+
69
+ [\--database-password, -p] Optional: The password of the database user (default: no password)
70
+
71
+ [\--database-name, -n] Optional: The name of the NCBI taxonomy database (default: kingdom_assignment_taxonomy)
72
+
73
+ [\--filter, -f] A file in YAML format containing a list of the higher rank taxonomic groups The default filter information and instructions for creating your own filters can be found in the section "Custom filters".
74
+
75
+ [\--help, -h] Show a help message
76
+
77
+ Here is an example for how phyta-assign is used from the command line:
78
+
79
+ phyta-assign -i Corticium_candelabrum_blast5.xml -o Corticium_candelabrum_blast5_annotated.csv -d localhost -u root -p password -n kingdom_assignment_taxonomy -f default_filter.yaml
80
+
81
+ == phyta-split
82
+
83
+ Phyta-split takes the CSV file generated by phyta-assign as input, performs taxonomy-based sorting of the annotated ESTs and outputs two new files in CSV format. One file contains annotations for all ESTs that deemed to belong to the target-species. The second file contains annotations for those sequences that received three top hits from taxa defined as contaminant by the phyta-split taxonomy filter.
84
+
85
+ === Usage
86
+
87
+ [\--input-file, -i ] The output of phyta-assign in CSV format
88
+
89
+ [\--output-clean, -c ] The name of the clean output table in CSV format (default: [name_of_input_file]_clean.csv)
90
+
91
+ [\--output-contaminated, -d ] The name of the contaminated output table in CSV format (default: [name_of_input_file]_contaminated.csv)
92
+
93
+ [\--filter, -f ] A file in YAML format containing a list of taxa to be considered contaminants (default: Use builtin filter capturing Bacteria, Archaea, Viruses and NONE (unidentified species).
94
+
95
+ [\--help, -h] Show a help message
96
+
97
+ Here is an example for how phyta-split can be used from the command line. Note that no custom filter is used, so only the taxa "Bacteria", "Archaea", "Viruses" and "NONE" will be considered contaminations.
98
+
99
+ phyta-split -i Corticium_candelabrum_blast5_annotated.csv -c Corticium_candelabrum_clean.csv -d Corticium_candelabrum_contaminated.csv
100
+
101
+ === Rules
102
+
103
+ Sequences are included into the "clean" target-species sub-library annotation when at least one of their three top BLAST hits does not match any taxa in the phyta-split contamination filter. The default filter provided with the program contains the following taxonomic groups: Bacteria, Archaea, Viruses and NONE, which represents {unknown sequences}[http://www.ncbi.nlm.nih.gov/Taxonomy/Browser/wwwtax.cgi?mode=Undef&id=12908&lvl=3&keep=1&srchmode=1&unlock].
104
+
105
+ == Custom filters
106
+
107
+ Custom filters for phyta-assign and phyta-split can be provided in YAML format. This file can be passed to the corresponding tools as a command line parameter. In order to write a custom filter, it is not necessary to learn the YAML syntax.
108
+ Here's what an example filter looks like:
109
+
110
+ # Filter file for PhyTA 0.9
111
+ ---
112
+ - Bacteria
113
+ - Archaea
114
+ - Viridiplantae
115
+ - Rhodophyta
116
+ - Glaucocystophyceae
117
+ - Alveolata
118
+ - Cryptophyta
119
+ - stramenopiles
120
+ - Amoebozoa
121
+ - Apusozoa
122
+ - Euglenozoa
123
+ - Fornicata
124
+ - Haptophyceae
125
+ - Heterolobosea
126
+ - Jakobida
127
+ - Katablepharidophyta
128
+ - Malawimonadidae
129
+ - Nucleariidae
130
+ - Oxymonadida
131
+ - Parabasalia
132
+ - Rhizaria
133
+ - unclassified eukaryotes
134
+ - Fungi
135
+ - Metazoa
136
+ - Choanoflagellida
137
+ - Opisthokonta incertae sedis
138
+ - Viruses
139
+
140
+ The line starting with a # is a comment and is entirely optional. Just copy the text above into a new plain text file and modify it to your liking. Just make sure to copy the line with the three dashes over as well.
141
+ You can also download this filter directly from https://github.com/PalMuc/bio-phyta/raw/master/misc/default_filter.yaml (right click the link and select "save as").
142
+
143
+ == phyta-extract
144
+
145
+ Constructs two sub-libraries: a “clean” sub-library that consists of annotated sequences from the target species and a “contaminant” one that includes putative contaminant sequences.
146
+
147
+ The output files will be written in FASTA format.
148
+
149
+ === Usage
150
+
151
+ [\--fasta, -f] The file containing the sequences in FASTA format
152
+
153
+ [\--input-clean, -c] The name of the clean sequence table in CSV format
154
+
155
+ [\--input-contaminated, -d] The name of the contaminated sequence table in CSV format[\--output-clean, -o ] The name of the FASTA file where clean sequences will be written to
156
+
157
+ [\--output-contaminated, -p] The name of the FASTA file where contaminated sequences will be written to
158
+
159
+ [\--help, -h] Show a help message
160
+
161
+ Here is an example for how phyta-extract can be used from the command line.
162
+
163
+ phyta-extract -f Corticium_candelabrum.fasta -c Corticium_candelabrum_clean.csv -d Corticium_candelabrum_contaminated.csv -o Corticium_candelabrum_clean.fasta -p Corticium_candelabrum_contaminated.fasta
164
+
165
+ == Installation
166
+
167
+ == Prerequisites
168
+ In order to install this gem you need to have several programs
169
+ installed:
170
+
171
+ * Ruby either in version 1.8.7 or 1.9.2. JRuby unfortunately is not supported at the moment.
172
+ * Git
173
+ * cURL
174
+ * MySQL
175
+
176
+ In the following, the installation procedure is given for <b>Mac OS X</b> and <b>Ubuntu Linux 10.10</b>. The commands for Ubuntu also have been tested to work for <b>Debian Squeeze</b> although you should substitute apt-get by aptitude.
177
+
178
+ Please note that in order to use the sudo command, your user account must allowed to acquire root user privileges if this is not the case, please ask your administrator.
179
+
180
+ === Installing Git
181
+ An installer for Mac OS X can be obtained from the [official website](http://git-scm.com/). For any Linux distribution it is recommended that you use your system's package manager to install Git. Look for a package called git or git-core. For Ubuntu 10.10 the command is:
182
+
183
+ sudo apt-get install git
184
+
185
+ === Installing cURL
186
+ Mac OS X comes with curl by default, on a Linux system, cURL can be obtained via the system's package manager. For Ubuntu 10.10 the command is:
187
+
188
+ sudo apt-get install curl
189
+
190
+ === Installing Ruby
191
+ You can find out what version of Ruby comes with your system by typing the following from the command line:
192
+
193
+ ruby -v
194
+
195
+ The output of that command looks like that:
196
+
197
+ ruby 1.8.7 (2011-06-30 patchlevel 352) [i686-darwin10.8.0]
198
+
199
+ If you have ruby 1.8.7 or higher, you're all set.
200
+ If Ruby is not available on your system or if you have an older version, you should install the most recent version of Ruby.
201
+
202
+ The easiest way to install the most recent version of Ruby is via the {Ruby Version Manager}[http://rvm.beginrescueend.com/] (RVM) by Wayne E. Seguin.
203
+
204
+ Before you install RVM, make sure you have git and curl installed on your system.
205
+
206
+ RVM can be installed by calling:
207
+
208
+ bash < <( curl http://rvm.beginrescueend.com/releases/rvm-install-head )
209
+
210
+ This will install RVM to .rvm in your home folder and print several instructions specific to your platform on how to finish the installation. Please pay close attention to the "dependencies" section and look for the part where it says something like this:
211
+
212
+ # For Ruby (MRI & ree) you should install the following OS dependencies:
213
+ ruby: /usr/bin/apt-get install build-essential bison openssl libreadline6 libreadline6-dev curl git-core zlib1g zlib1g-dev libssl-dev libyaml-dev libsqlite3-0 libsqlite3-dev sqlite3 libxml2-dev libxslt-dev autoconf libc6-dev ncurses-dev
214
+
215
+ It is advisable that you install all of these prerequisites. Please do not copy the commands from this file, look at the output of the RVM installer.
216
+ If installing any of these packages gives you an error, consider updating your packages by using your system's update manager.
217
+
218
+ Next, you have to make sure that RVM is loaded when you start a new shell. Look for the part where it says: "You must now complete the install by loading RVM in new shells."
219
+
220
+ On Ubuntu 10.10 you can edit your .bashrc by calling:
221
+
222
+ gedit .bashrc
223
+
224
+ On Mac OS X, you can type:
225
+
226
+ open -a TextEdit .bash_profile
227
+
228
+ At the very end of this file add the following line:
229
+
230
+ [[ -s "$HOME/.rvm/scripts/rvm" ]] && source "$HOME/.rvm/scripts/rvm" # This loads RVM into a shell session.
231
+
232
+ Now save the file, close your editor and close your shell. Start a new shell and type:
233
+
234
+ type rvm | head -1
235
+
236
+ If you see something like "rvm is a function" the installation was
237
+ successful. If you run into problems, read the {documentation}[http://rvm.beginrescueend.com/rvm/install/].
238
+
239
+ <b>The following command is not part of the installation procedure!</b>
240
+
241
+ You can always delete RVM and start from scratch by typing:
242
+
243
+ rvm implode
244
+
245
+ Please note that this will delete all versions of Ruby you installed with RVM as well as all of the gems you installed. It will not reverse the changes you made to your shell's load configuration.
246
+
247
+ Now you can install Ruby by calling:
248
+
249
+ rvm install 1.9.2
250
+
251
+ Please note that everything RVM installs is placed in the folder .rvm in your home directory. Therefore, it is not necessary to use sudo when calling rvm.
252
+
253
+ In order to use Ruby instead of your system's Ruby version you must type
254
+
255
+ rvm use 1.9.2
256
+
257
+ every time you open a new shell. You can check which version you are currently using with:
258
+
259
+ ruby -v
260
+
261
+ If you want to switch back to the version of Ruby that came with your system, type:
262
+
263
+ rvm use system
264
+
265
+ In order to use Ruby as the default Ruby implementation on your system you can type:
266
+
267
+ rvm --default use 1.9.2
268
+
269
+ Now Ruby 1.9.2 will be called when you type ruby in a new shell.
270
+
271
+ === Installing MySQL
272
+ PhyTA uses a MySQL database in order to store information from the {NCBI taxonomy database}[ftp://ftp.ncbi.nih.gov/pub/taxonomy/] efficiently.
273
+
274
+ The database does not have to be hosted on the system that is running PhyTA, but it is advantageous for performance reasons.
275
+
276
+ The correct installation procedure for MySQL varies widely among different platforms. For many systems (like Mac OS X) binaries can be obtained from the {official website}[http://www.mysql.com/downloads/mysql/]. In the following, the setup under Ubuntu 10.10 is explained.
277
+
278
+ sudo apt-get install mysql-server
279
+
280
+ On Mac OS X, you can install the MySQL preference pane and start the server from there. The MySQL binaries are at /usr/local/mysql/bin/. In order to be able to execute the following examples without having to prefix this path every time, you can add aliases to your bash configuration:
281
+
282
+ open -a TextEdit .bash_profile
283
+
284
+ Now add the following lines at the end:
285
+
286
+ alias mysql=/usr/local/mysql/bin/mysql
287
+ alias mysqladmin=/usr/local/mysql/bin/mysqladmin
288
+
289
+ Refer to the ReadMe file that comes with the MySQL installer if you are using tclsh instead of bash.
290
+
291
+ === Starting the database
292
+
293
+ Usually the MySQL setup creates an administrator account named "root" with
294
+ an empty password. If your administrator name is different or you have
295
+ set a password, you must adjust the commands in the next section accordingly.
296
+ You can now start MySQL by typing
297
+
298
+ sudo service mysql start
299
+
300
+ == phyta-setup-taxonomy-db
301
+
302
+ First, you need to set up an empty database for the NCBI taxonomy data. This can be achieved by typing:
303
+
304
+ mysql -u root -p password -e "CREATE DATABASE kingdom_assignment_taxonomy"
305
+
306
+ In this example, substitute root for your MySQL username, password for your password and kingdom_assignment_taxonomy for the database name. Leave out the parameter -p if your database does not have a password.
307
+
308
+ After that, the program phyta-setup-taxonomy-db will help you set up the NCBI taxonomy database. Its command line options are the following.
309
+
310
+ [\--database-server, -d] Optional: The address of the MySQL database server (default: localhost)
311
+
312
+ [\--database-user, -u] Optional: The name of the database user (default: root)
313
+
314
+ [\--database-password, -p] Optional: The password of the database user (default: no password)
315
+
316
+ [\--database-name, -n] Optional: The name of the NCBI taxonomy database (default: kingdom_assignment_taxonomy)
317
+
318
+ [\--help, -h] Show a help message
319
+
320
+ Here is an example command consistent with the example above:
321
+
322
+ phyta-setup-taxonomy-db -d localhost -u root -p password -n kingdom_assignment_taxonomy
323
+
324
+ Phyta-setup-taxonomy-db will now download the NCBI taxonomy dump files and load them into your MySQL database. This might take a while.
4
325
 
5
326
  == Contributing to bio-phyta
6
327
 
@@ -14,6 +335,12 @@ Description goes here.
14
335
 
15
336
  == Copyright
16
337
 
17
- Copyright (c) 2011 Philipp Comans. See LICENSE.txt for
18
- further details.
338
+ Copyright (c) 2011 Philipp Comans.
339
+
340
+ The MySQL schema used in phyta-setup-taxonomy-db and phyta-assign has been developed by Matthew Horton of the the Department of Ecology and Evolution of the Division of Biological Sciences at the University of Chicago and is available at http://bergelson.uchicago.edu/Members/mhorton/taxonomydb.build .
341
+
342
+ See LICENSE.txt for further details.
343
+
344
+ == Acknowledgements
345
+ Development of this program was supported by the {Molecular Geo- and Palaeobiology Lab}[http://www.mol-palaeo.de/] of the Department of Earth and Environmental Sciences and the initiative "{Gleichstellung in Forschung und Lehre}[http://www.frauenbeauftragte.uni-muenchen.de/foerdermoegl/lmu1/tg73/index.html]" of the Ludwig-Maximilians-University Munich (LMU).
19
346
 
data/VERSION CHANGED
@@ -1 +1 @@
1
- 0.9.1
1
+ 0.9.2
@@ -30,12 +30,11 @@ if RUBY_PLATFORM =~ /java/
30
30
  puts "You are running JRuby, the jdbc/mysql database connector will be used."
31
31
  require 'jdbc/mysql'
32
32
  else
33
- require 'mysql'
33
+ require 'mysql2'
34
34
  end
35
35
 
36
36
  require 'sequel'
37
37
  require 'nokogiri'
38
- require 'bio'
39
38
  require 'yaml'
40
39
 
41
40
  require 'csv'
@@ -20,7 +20,7 @@ unless opts[:database_password_given]
20
20
  end
21
21
 
22
22
  #Connect to the target database
23
- connect_string = 'mysql://'+ opts[:database_server] + '/' + opts[:database_name] + '?user=' + opts[:database_user]
23
+ connect_string = 'mysql2://'+ opts[:database_server] + '/' + opts[:database_name] + '?user=' + opts[:database_user]
24
24
 
25
25
  if !opts[:database_password].nil?
26
26
  connect_string = connect_string + '&password=' + opts[:database_password]
@@ -31,7 +31,7 @@ if RUBY_PLATFORM =~ /java/
31
31
  require 'jdbc/mysql'
32
32
  connect_string = 'jdbc:' + connect_string
33
33
  else
34
- require 'mysql'
34
+ require 'mysql2'
35
35
  end
36
36
 
37
37
  PROTEIN_TABLE_NAME = 'proteinGiToTaxonId'
@@ -54,7 +54,7 @@ ftp.login
54
54
  files = ftp.chdir('pub/taxonomy/')
55
55
 
56
56
  #Do the following in a temporary directory, automatically delete it afterwards
57
- Dir.mktmpdir do |dir|
57
+ Dir.mktmpdir() do |dir|
58
58
  Dir.chdir(dir)
59
59
 
60
60
  tax_dmp = 'taxdump.tar.gz'
@@ -119,11 +119,11 @@ database.run "TRUNCATE #{NAMES_TABLE_NAME}"
119
119
  database.run "TRUNCATE #{NODES_TABLE_NAME}"
120
120
  database.run "TRUNCATE #{PROTEIN_TABLE_NAME}"
121
121
 
122
- database.run "LOAD DATA INFILE '#{dir}/gi_taxid_prot.dmp' INTO TABLE #{PROTEIN_TABLE_NAME} FIELDS TERMINATED BY '\t' LINES TERMINATED BY '\n' (gi,taxonid);"
122
+ database.run "LOAD DATA LOCAL INFILE '#{dir}/gi_taxid_prot.dmp' INTO TABLE #{PROTEIN_TABLE_NAME} FIELDS TERMINATED BY '\t' LINES TERMINATED BY '\n' (gi,taxonid);"
123
123
 
124
- database.run "LOAD DATA INFILE '#{dir}/names.dmp' INTO TABLE #{NAMES_TABLE_NAME} FIELDS TERMINATED BY '\t|\t' LINES TERMINATED BY '\t|\n' (taxonid, name, uniquename, class);"
124
+ database.run "LOAD DATA LOCAL INFILE '#{dir}/names.dmp' INTO TABLE #{NAMES_TABLE_NAME} FIELDS TERMINATED BY '\t|\t' LINES TERMINATED BY '\t|\n' (taxonid, name, uniquename, class);"
125
125
 
126
- database.run "LOAD DATA INFILE '#{dir}/nodes.dmp' INTO TABLE #{NODES_TABLE_NAME} FIELDS TERMINATED BY '\t|\t' LINES TERMINATED BY '\t|\n' (taxonid, parenttaxonid,rank,embl_code,division_id,inherited_div_flag,genetic_code_id,inherited_gc_flag, mitochondrial_genetic_codeid,inherited_mgc_flag,genBank_hidden_flag,hidden_subtree_root_flag,comments);"
126
+ database.run "LOAD DATA LOCAL INFILE '#{dir}/nodes.dmp' INTO TABLE #{NODES_TABLE_NAME} FIELDS TERMINATED BY '\t|\t' LINES TERMINATED BY '\t|\n' (taxonid, parenttaxonid,rank,embl_code,division_id,inherited_div_flag,genetic_code_id,inherited_gc_flag, mitochondrial_genetic_codeid,inherited_mgc_flag,genBank_hidden_flag,hidden_subtree_root_flag,comments);"
127
127
 
128
128
  end
129
129
 
@@ -1,6 +1,3 @@
1
- # To change this template, choose Tools | Templates
2
- # and open the template in the editor.
3
-
4
1
  class BlastStringParser
5
2
  def initialize
6
3
 
@@ -13,7 +13,7 @@ class KingdomDB
13
13
 
14
14
  def initialize(server, user, password, database)
15
15
 
16
- connect_string = 'mysql://'+ server + '/' + database + '?user=' + user
16
+ connect_string = 'mysql2://'+ server + '/' + database + '?user=' + user
17
17
 
18
18
  if !password.nil?
19
19
  connect_string = connect_string + '&password=' + password
@@ -0,0 +1,29 @@
1
+ # Filter file for PhyTA 0.9
2
+ ---
3
+ - Bacteria
4
+ - Archaea
5
+ - Viridiplantae
6
+ - Rhodophyta
7
+ - Glaucocystophyceae
8
+ - Alveolata
9
+ - Cryptophyta
10
+ - stramenopiles
11
+ - Amoebozoa
12
+ - Apusozoa
13
+ - Euglenozoa
14
+ - Fornicata
15
+ - Haptophyceae
16
+ - Heterolobosea
17
+ - Jakobida
18
+ - Katablepharidophyta
19
+ - Malawimonadidae
20
+ - Nucleariidae
21
+ - Oxymonadida
22
+ - Parabasalia
23
+ - Rhizaria
24
+ - unclassified eukaryotes
25
+ - Fungi
26
+ - Metazoa
27
+ - Choanoflagellida
28
+ - Opisthokonta incertae sedis
29
+ - Viruses
metadata CHANGED
@@ -1,138 +1,189 @@
1
- --- !ruby/object:Gem::Specification
1
+ --- !ruby/object:Gem::Specification
2
2
  name: bio-phyta
3
- version: !ruby/object:Gem::Version
4
- version: 0.9.1
3
+ version: !ruby/object:Gem::Version
4
+ hash: 63
5
5
  prerelease:
6
+ segments:
7
+ - 0
8
+ - 9
9
+ - 2
10
+ version: 0.9.2
6
11
  platform: ruby
7
- authors:
12
+ authors:
8
13
  - Philipp Comans
9
14
  autorequire:
10
15
  bindir: bin
11
16
  cert_chain: []
12
- date: 2011-10-21 00:00:00.000000000Z
13
- dependencies:
14
- - !ruby/object:Gem::Dependency
15
- name: bio
16
- requirement: &2153022740 !ruby/object:Gem::Requirement
17
+
18
+ date: 2011-11-30 00:00:00 Z
19
+ dependencies:
20
+ - !ruby/object:Gem::Dependency
21
+ requirement: &id001 !ruby/object:Gem::Requirement
17
22
  none: false
18
- requirements:
19
- - - ! '>='
20
- - !ruby/object:Gem::Version
23
+ requirements:
24
+ - - ">="
25
+ - !ruby/object:Gem::Version
26
+ hash: 3
27
+ segments:
28
+ - 1
29
+ - 4
30
+ - 2
21
31
  version: 1.4.2
22
- type: :runtime
32
+ version_requirements: *id001
33
+ name: bio
23
34
  prerelease: false
24
- version_requirements: *2153022740
25
- - !ruby/object:Gem::Dependency
26
- name: mysql
27
- requirement: &2153022260 !ruby/object:Gem::Requirement
28
- none: false
29
- requirements:
30
- - - ! '>='
31
- - !ruby/object:Gem::Version
32
- version: 2.8.1
33
35
  type: :runtime
36
+ - !ruby/object:Gem::Dependency
37
+ requirement: &id002 !ruby/object:Gem::Requirement
38
+ none: false
39
+ requirements:
40
+ - - ">="
41
+ - !ruby/object:Gem::Version
42
+ hash: 3
43
+ segments:
44
+ - 0
45
+ version: "0"
46
+ version_requirements: *id002
47
+ name: mysql2
34
48
  prerelease: false
35
- version_requirements: *2153022260
36
- - !ruby/object:Gem::Dependency
37
- name: sequel
38
- requirement: &2153021780 !ruby/object:Gem::Requirement
49
+ type: :runtime
50
+ - !ruby/object:Gem::Dependency
51
+ requirement: &id003 !ruby/object:Gem::Requirement
39
52
  none: false
40
- requirements:
41
- - - ! '>='
42
- - !ruby/object:Gem::Version
53
+ requirements:
54
+ - - ">="
55
+ - !ruby/object:Gem::Version
56
+ hash: 119
57
+ segments:
58
+ - 3
59
+ - 28
60
+ - 0
43
61
  version: 3.28.0
44
- type: :runtime
62
+ version_requirements: *id003
63
+ name: sequel
45
64
  prerelease: false
46
- version_requirements: *2153021780
47
- - !ruby/object:Gem::Dependency
48
- name: fastercsv
49
- requirement: &2153021300 !ruby/object:Gem::Requirement
65
+ type: :runtime
66
+ - !ruby/object:Gem::Dependency
67
+ requirement: &id004 !ruby/object:Gem::Requirement
50
68
  none: false
51
- requirements:
52
- - - ! '>='
53
- - !ruby/object:Gem::Version
69
+ requirements:
70
+ - - ">="
71
+ - !ruby/object:Gem::Version
72
+ hash: 11
73
+ segments:
74
+ - 1
75
+ - 5
76
+ - 4
54
77
  version: 1.5.4
55
- type: :runtime
78
+ version_requirements: *id004
79
+ name: fastercsv
56
80
  prerelease: false
57
- version_requirements: *2153021300
58
- - !ruby/object:Gem::Dependency
59
- name: nokogiri
60
- requirement: &2153020820 !ruby/object:Gem::Requirement
81
+ type: :runtime
82
+ - !ruby/object:Gem::Dependency
83
+ requirement: &id005 !ruby/object:Gem::Requirement
61
84
  none: false
62
- requirements:
63
- - - ! '>='
64
- - !ruby/object:Gem::Version
85
+ requirements:
86
+ - - ">="
87
+ - !ruby/object:Gem::Version
88
+ hash: 3
89
+ segments:
90
+ - 1
91
+ - 5
92
+ - 0
65
93
  version: 1.5.0
66
- type: :runtime
94
+ version_requirements: *id005
95
+ name: nokogiri
67
96
  prerelease: false
68
- version_requirements: *2153020820
69
- - !ruby/object:Gem::Dependency
70
- name: trollop
71
- requirement: &2153020340 !ruby/object:Gem::Requirement
97
+ type: :runtime
98
+ - !ruby/object:Gem::Dependency
99
+ requirement: &id006 !ruby/object:Gem::Requirement
72
100
  none: false
73
- requirements:
74
- - - ! '>='
75
- - !ruby/object:Gem::Version
101
+ requirements:
102
+ - - ">="
103
+ - !ruby/object:Gem::Version
104
+ hash: 83
105
+ segments:
106
+ - 1
107
+ - 16
108
+ - 2
76
109
  version: 1.16.2
77
- type: :runtime
110
+ version_requirements: *id006
111
+ name: trollop
78
112
  prerelease: false
79
- version_requirements: *2153020340
80
- - !ruby/object:Gem::Dependency
81
- name: shoulda
82
- requirement: &2153019860 !ruby/object:Gem::Requirement
113
+ type: :runtime
114
+ - !ruby/object:Gem::Dependency
115
+ requirement: &id007 !ruby/object:Gem::Requirement
83
116
  none: false
84
- requirements:
85
- - - ! '>='
86
- - !ruby/object:Gem::Version
87
- version: '0'
88
- type: :development
117
+ requirements:
118
+ - - ">="
119
+ - !ruby/object:Gem::Version
120
+ hash: 3
121
+ segments:
122
+ - 0
123
+ version: "0"
124
+ version_requirements: *id007
125
+ name: shoulda
89
126
  prerelease: false
90
- version_requirements: *2153019860
91
- - !ruby/object:Gem::Dependency
92
- name: bundler
93
- requirement: &2153019380 !ruby/object:Gem::Requirement
127
+ type: :development
128
+ - !ruby/object:Gem::Dependency
129
+ requirement: &id008 !ruby/object:Gem::Requirement
94
130
  none: false
95
- requirements:
131
+ requirements:
96
132
  - - ~>
97
- - !ruby/object:Gem::Version
133
+ - !ruby/object:Gem::Version
134
+ hash: 23
135
+ segments:
136
+ - 1
137
+ - 0
138
+ - 0
98
139
  version: 1.0.0
99
- type: :development
140
+ version_requirements: *id008
141
+ name: bundler
100
142
  prerelease: false
101
- version_requirements: *2153019380
102
- - !ruby/object:Gem::Dependency
103
- name: jeweler
104
- requirement: &2153018900 !ruby/object:Gem::Requirement
143
+ type: :development
144
+ - !ruby/object:Gem::Dependency
145
+ requirement: &id009 !ruby/object:Gem::Requirement
105
146
  none: false
106
- requirements:
147
+ requirements:
107
148
  - - ~>
108
- - !ruby/object:Gem::Version
149
+ - !ruby/object:Gem::Version
150
+ hash: 7
151
+ segments:
152
+ - 1
153
+ - 6
154
+ - 4
109
155
  version: 1.6.4
110
- type: :development
156
+ version_requirements: *id009
157
+ name: jeweler
111
158
  prerelease: false
112
- version_requirements: *2153018900
113
- - !ruby/object:Gem::Dependency
114
- name: rcov
115
- requirement: &2153018420 !ruby/object:Gem::Requirement
116
- none: false
117
- requirements:
118
- - - ! '>='
119
- - !ruby/object:Gem::Version
120
- version: '0'
121
159
  type: :development
160
+ - !ruby/object:Gem::Dependency
161
+ requirement: &id010 !ruby/object:Gem::Requirement
162
+ none: false
163
+ requirements:
164
+ - - ">="
165
+ - !ruby/object:Gem::Version
166
+ hash: 3
167
+ segments:
168
+ - 0
169
+ version: "0"
170
+ version_requirements: *id010
171
+ name: rcov
122
172
  prerelease: false
123
- version_requirements: *2153018420
173
+ type: :development
124
174
  description: Pipeline to remove contaminations from EST libraries
125
175
  email: philipp.comans@googlemail.com
126
- executables:
176
+ executables:
177
+ - phyta-split
127
178
  - phyta-assign
128
179
  - phyta-extract
129
180
  - phyta-setup-taxonomy-db
130
- - phyta-split
131
181
  extensions: []
132
- extra_rdoc_files:
182
+
183
+ extra_rdoc_files:
133
184
  - LICENSE.txt
134
185
  - README.rdoc
135
- files:
186
+ files:
136
187
  - .document
137
188
  - Gemfile
138
189
  - LICENSE.txt
@@ -145,6 +196,7 @@ files:
145
196
  - bin/phyta-split
146
197
  - lib/blast_string_parser.rb
147
198
  - lib/kingdom_db.rb
199
+ - misc/default_filter.yaml
148
200
  - test/helper.rb
149
201
  - test/test_blackbox_assign.rb
150
202
  - test/test_blackbox_extract.rb
@@ -152,31 +204,37 @@ files:
152
204
  - test/test_blast_string_parser.rb
153
205
  - test/test_kingdom_db.rb
154
206
  homepage: https://github.com/PalMuc/bio-phyta
155
- licenses:
207
+ licenses:
156
208
  - LGPL
157
209
  post_install_message:
158
210
  rdoc_options: []
159
- require_paths:
211
+
212
+ require_paths:
160
213
  - lib
161
- required_ruby_version: !ruby/object:Gem::Requirement
214
+ required_ruby_version: !ruby/object:Gem::Requirement
162
215
  none: false
163
- requirements:
164
- - - ! '>='
165
- - !ruby/object:Gem::Version
166
- version: '0'
167
- segments:
216
+ requirements:
217
+ - - ">="
218
+ - !ruby/object:Gem::Version
219
+ hash: 3
220
+ segments:
168
221
  - 0
169
- hash: -3130547697683155421
170
- required_rubygems_version: !ruby/object:Gem::Requirement
222
+ version: "0"
223
+ required_rubygems_version: !ruby/object:Gem::Requirement
171
224
  none: false
172
- requirements:
173
- - - ! '>='
174
- - !ruby/object:Gem::Version
175
- version: '0'
225
+ requirements:
226
+ - - ">="
227
+ - !ruby/object:Gem::Version
228
+ hash: 3
229
+ segments:
230
+ - 0
231
+ version: "0"
176
232
  requirements: []
233
+
177
234
  rubyforge_project:
178
235
  rubygems_version: 1.8.10
179
236
  signing_key:
180
237
  specification_version: 3
181
238
  summary: Pipeline to remove contaminations from EST libraries
182
239
  test_files: []
240
+