The J-L24-Y-DNA Haplogroup Project
- Results
20 April 2011 Fluxus Network Tree of the L70-Beta cluster
07 October 2010: Map of J-L24 Variance in the world (Middle East, North Africa and Europe)
22 November 2009: Fluxus Diagramfull size
This diagram represents a theoretical spread of the J-L25 (J2a4h) subclade based on STR properties.
The Blue names in the diagram represent clusters created by Project administrator Al Aburto. Two or three clusters were not placed because of their location on the diagrams (i.e. L70 Beta was in an area with too many haplotypes). Discussions of these clusters appears in the project news section.
The red L series SNPs generally point out regions and/or branches where these SNPs are known to exist. All haplotypes in the diagram should carry the L24 and L25 SNPs.
Some individuals might notice their placement has moved with new revisions. This is because Fluxus Network creates its branching based on STR properties. In one version, based on the data provided, it may, for example create a branch based on a slow marker like DYS565. In a revision, as data is added, seeing more variance at that marker, the new diagram may not create such a branch but use the same marker to create only a sub-branch. For this reason some haplotypes, which show properties of multiple clusters, may move around. The program tries to find the most likely scenario for branching but ultimately only UEPs and SNPs can, more definitively, determine the phylogenetic structure.
The STRs which define the root branching remain DYS445 and DYS511. From there, various markers are used by Fluxus Network to create branching such as DYS487, DYS395S1, DYS557, DYS391, DYS565, DYS444 and DYS446. Values at these particular markers in themselves do not represent unique events but taken as a whole, looking at full 67 marker haplotypes, they tend to identify clustering and branching created by the Fluxus Network diagram.
The Fluxus Network diagrams correspond to the clustering created by Project Administrator Al Aburto. Almost all of his clusters in the project data show up clustered in the diagrams.
Lastly, the modal haplotype does not necessarily represent the ancestral common haplotype. It could, but generally speaking the L25*(10) group shows more variance and seems to be older than L25*(6) and L70. The modal haplotype shows up where the largest number of haplotypes are located. In our case most of the haplotypes are in the L25*(10) and L70 groups and the modal haplotype shows up between them near the L25*(6) group.
26 May 2009: J2a4h Fluxus Nework DiagramFull Size
 The Fluxus Network Software looked at the projects 67 marker haplotypes and generated an automated tree based on the haplotypes and the patterns it picks up with various marker values. We believe the software correctly identified the clusters within J-L-24 and that it has done a good job of providing a theorized branching of our subclade but we think that more data and/or more research could, in the future, alter the theorized structure as shown.
17 April 2009: We are in a primary data accumulation mode at this time.
30 March 2009: No project results ATT.
|