Sentence examples for the sequences were processed using from inspiring English sources

Furthermore, the sequences were processed using the Picard tool and R/Bioconductor.

The sequences were processed using the program Jellyfish [ 48] into kmers with length 31 and each kmer was counted in each individual, and placed into a matrix.

In order to reduce the EST sequence redundancy and consequently the time complexity of the process, the sequences were processed using CD-HIT [ 52] prior to database formatting.

Raw ABI chromatograph files of the sequences were processed using trace2seq.pl (a perl program that uses phred [ 63, 64] to identify high-quality base calls; A. Anthony and M. Blaxter, unpublished).

The results are discussed in detail in the Additional file 2. The assembled sequences were processed using the ESTPiper for annotation against the UniProtKB protein database (date: August 7, 2011) [ 49].

The protein sequences were processed using the following programs: SignalP (version 3.0 and 4.0) (21, 21), Phobius (22), WoLF PSORT (23) and TargetP (24) for secretory signal peptide and subcellular location prediction.

The raw sequences were processed using PHRED and CROSS MATCH programs as previously reported [ 18, 65].

The raw EST sequences were processed using Sequencher 4.7 (Gene Codes Corporation, MI) to trim vector and ambiguous ends.

The complete genome sequences were processed using RNAmmer (Lagesen et al. 2007), tRNAscan-SE (Lowe and Eddy 1997), and PRODIGAL (Hyatt et al. 2010) for gene prediction.

Shotgun sequences were processed using the MetaPhlAn pipeline and a multivariate analysis of the taxonomic results was carried out.

Furthermore, obtained sequences were processed using the Classifier tool (Wang et al. 2007) of the RDP pyrosequencing pipeline http://pyro.cme.msu.edu/.msu.edu/