Sentence examples for analyses was generated from from inspiring English sources
The phylogeny produced in the current analyses was generated from nine coding regions present in all members of the genus Orthopoxvirus as well as the members of the Poxviridae and would not be influenced by gene loss.
Input for the statistical analyses was generated from separate text files using a Perl script.
The phylogenetic tree used in the pgls analyses was generated from an alignment of 763 nuclear loci sequenced by a novel targeted enrichment method [ 64].
The DNase accessible control datasets used in over-representation analyses were generated from DNase I hypersensitivity datasets (UW DNase: University of Washington) [ 42] downloaded from the UCSC ENCODE database [ 43].
RNA-Seq data for all analyses were generated from the same RNA reference sample (Human Brain Reference RNA) of the MicroArray Quality Control (MAQC) project (MAQC Consortium 2006; [ 43]).
Natural matings between B6 and CAST were used to generate F1 hybrid males for spermatozoa collection; all other F1 hybrid tissues used for bisulfite analyses were generated from natural matings between B6 and CAST12 mice.
A training dataset for Machine Learning (ML) and Exploratory Data Analyses (EDA) was generated from promoter region sequences of a set of genes known to be targets of CREB transcription regulation and a set of genes whose transcription regulations are potentially CREB-independent.
For HuCV phylogenetic analyses, a multiple-sequence alignment was generated from the consensus sequence of each of the isolates and the reference strains by using ClustalX 1.8 methods.
In both analyses, a bootstrap consensus tree was generated from the 100 resulting consensus trees using the CONSENSE program of the PHYLIP package.
The peptide database was generated from analyses performed using several mass spectrometers, including LCQ Duo, LCQ Deca, LCQ XP, and LTQ (ThermoFinnigan, San Jose, CA) ion trap mass spectrometers.
