after the first excitement of receiving my dad's result for X2b-T226C haplogroup, came
i was expecting it to be easier to find out which subdivision that belongs to, and where in the world is the highest frequency. instead it's just X2b-T226C and the migration & frequency maps are super rough (only for X). i understand tracing migration is tough, there must be room for improvement for frequency maps. anybody happier with other haplogoups? FT working on that?
another feature that would greatly improve the product, would be the result in more readable nomenclature. X2b-T226C is just redundant, since T226C actually is the b branch of X2 (http://www.phylotree.org/tree/X.htm), so X2b would be the same information. what i need is the subclade (Xb1-...?) to facilitate my research into scientific papers such as: http://www.eupedia.com/europe/Haplog...html#subclades
i was expecting it to be easier to find out which subdivision that belongs to, and where in the world is the highest frequency. instead it's just X2b-T226C and the migration & frequency maps are super rough (only for X). i understand tracing migration is tough, there must be room for improvement for frequency maps. anybody happier with other haplogoups? FT working on that?
another feature that would greatly improve the product, would be the result in more readable nomenclature. X2b-T226C is just redundant, since T226C actually is the b branch of X2 (http://www.phylotree.org/tree/X.htm), so X2b would be the same information. what i need is the subclade (Xb1-...?) to facilitate my research into scientific papers such as: http://www.eupedia.com/europe/Haplog...html#subclades
Comment