Statements in which the resource exists.
SubjectPredicateObjectContext
pubmed-article:18053244rdf:typepubmed:Citationlld:pubmed
pubmed-article:18053244lifeskim:mentionsumls-concept:C0017431lld:lifeskim
pubmed-article:18053244lifeskim:mentionsumls-concept:C0031797lld:lifeskim
pubmed-article:18053244lifeskim:mentionsumls-concept:C1511726lld:lifeskim
pubmed-article:18053244lifeskim:mentionsumls-concept:C0439851lld:lifeskim
pubmed-article:18053244lifeskim:mentionsumls-concept:C0806909lld:lifeskim
pubmed-article:18053244lifeskim:mentionsumls-concept:C0524865lld:lifeskim
pubmed-article:18053244lifeskim:mentionsumls-concept:C1552596lld:lifeskim
pubmed-article:18053244lifeskim:mentionsumls-concept:C1947931lld:lifeskim
pubmed-article:18053244pubmed:dateCreated2008-2-1lld:pubmed
pubmed-article:18053244pubmed:abstractTextMaximum parsimony phylogenetic tree reconstruction from genetic variation data is a fundamental problem in computational genetics with many practical applications in population genetics, whole genome analysis, and the search for genetic predictors of disease. Efficient methods are available for reconstruction of maximum parsimony trees from haplotype data, but such data are difficult to determine directly for autosomal DNA. Data more commonly is available in the form of genotypes, which consist of conflated combinations of pairs of haplotypes from homologous chromosomes. Currently, there are no general algorithms for the direct reconstruction of maximum parsimony phylogenies from genotype data. Hence phylogenetic applications for autosomal data must therefore rely on other methods for first computationally inferring haplotypes from genotypes.lld:pubmed
pubmed-article:18053244pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:18053244pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:18053244pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:18053244pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:18053244pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:18053244pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:18053244pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:18053244pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:18053244pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:18053244pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:18053244pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:18053244pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:18053244pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:18053244pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:18053244pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:18053244pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:18053244pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:18053244pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:18053244pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:18053244pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:18053244pubmed:languageenglld:pubmed
pubmed-article:18053244pubmed:journalhttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:18053244pubmed:citationSubsetIMlld:pubmed
pubmed-article:18053244pubmed:chemicalhttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:18053244pubmed:chemicalhttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:18053244pubmed:statusMEDLINElld:pubmed
pubmed-article:18053244pubmed:issn1471-2105lld:pubmed
pubmed-article:18053244pubmed:authorpubmed-author:RaviRRlld:pubmed
pubmed-article:18053244pubmed:authorpubmed-author:SchwartzRusse...lld:pubmed
pubmed-article:18053244pubmed:authorpubmed-author:LamFumeiFlld:pubmed
pubmed-article:18053244pubmed:authorpubmed-author:SridharSrinat...lld:pubmed
pubmed-article:18053244pubmed:authorpubmed-author:BlellochGuy...lld:pubmed
pubmed-article:18053244pubmed:issnTypeElectroniclld:pubmed
pubmed-article:18053244pubmed:volume8lld:pubmed
pubmed-article:18053244pubmed:ownerNLMlld:pubmed
pubmed-article:18053244pubmed:authorsCompleteYlld:pubmed
pubmed-article:18053244pubmed:pagination472lld:pubmed
pubmed-article:18053244pubmed:dateRevised2009-11-18lld:pubmed
pubmed-article:18053244pubmed:meshHeadingpubmed-meshheading:18053244...lld:pubmed
pubmed-article:18053244pubmed:meshHeadingpubmed-meshheading:18053244...lld:pubmed
pubmed-article:18053244pubmed:meshHeadingpubmed-meshheading:18053244...lld:pubmed
pubmed-article:18053244pubmed:meshHeadingpubmed-meshheading:18053244...lld:pubmed
pubmed-article:18053244pubmed:meshHeadingpubmed-meshheading:18053244...lld:pubmed
pubmed-article:18053244pubmed:meshHeadingpubmed-meshheading:18053244...lld:pubmed
pubmed-article:18053244pubmed:meshHeadingpubmed-meshheading:18053244...lld:pubmed
pubmed-article:18053244pubmed:meshHeadingpubmed-meshheading:18053244...lld:pubmed
pubmed-article:18053244pubmed:meshHeadingpubmed-meshheading:18053244...lld:pubmed
pubmed-article:18053244pubmed:meshHeadingpubmed-meshheading:18053244...lld:pubmed
pubmed-article:18053244pubmed:meshHeadingpubmed-meshheading:18053244...lld:pubmed
pubmed-article:18053244pubmed:meshHeadingpubmed-meshheading:18053244...lld:pubmed
pubmed-article:18053244pubmed:meshHeadingpubmed-meshheading:18053244...lld:pubmed
pubmed-article:18053244pubmed:meshHeadingpubmed-meshheading:18053244...lld:pubmed
pubmed-article:18053244pubmed:meshHeadingpubmed-meshheading:18053244...lld:pubmed
pubmed-article:18053244pubmed:meshHeadingpubmed-meshheading:18053244...lld:pubmed
pubmed-article:18053244pubmed:meshHeadingpubmed-meshheading:18053244...lld:pubmed
pubmed-article:18053244pubmed:meshHeadingpubmed-meshheading:18053244...lld:pubmed
pubmed-article:18053244pubmed:meshHeadingpubmed-meshheading:18053244...lld:pubmed
pubmed-article:18053244pubmed:meshHeadingpubmed-meshheading:18053244...lld:pubmed
pubmed-article:18053244pubmed:meshHeadingpubmed-meshheading:18053244...lld:pubmed
pubmed-article:18053244pubmed:meshHeadingpubmed-meshheading:18053244...lld:pubmed
pubmed-article:18053244pubmed:meshHeadingpubmed-meshheading:18053244...lld:pubmed
pubmed-article:18053244pubmed:year2007lld:pubmed
pubmed-article:18053244pubmed:articleTitleDirect maximum parsimony phylogeny reconstruction from genotype data.lld:pubmed
pubmed-article:18053244pubmed:affiliationComputer Science Department, Carnegie Mellon University, Pittsburgh, PA, USA. srinath@cs.cmu.edulld:pubmed
pubmed-article:18053244pubmed:publicationTypeJournal Articlelld:pubmed
pubmed-article:18053244pubmed:publicationTypeResearch Support, U.S. Gov't, Non-P.H.S.lld:pubmed