-
Notifications
You must be signed in to change notification settings - Fork 33
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Browse files
Browse the repository at this point in the history
* Addresses epic #480 "Update Haplotype to CisPhasedBlock". * Addresses #481 bullet 1. * Related to #461 (comment).
- Loading branch information
Showing
8 changed files
with
73 additions
and
45 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,23 @@ | ||
.. _CisPhasedBlock: | ||
|
||
CisPhasedBlock | ||
!!!!!!!!!!!!!! | ||
|
||
The CisPhasedBlock is a set of Alleles that are found *in-cis*: occurring | ||
on the same physical molecule. The CisPhasedBlock structure is useful for | ||
representing genetic *Haplotypes*, which are commonly described with respect | ||
to locations on a gene, a set of nearby genes, or other physically proximal | ||
genetic markers that tend to be transmitted together. Unlike haplotypes, the | ||
CisPhasedBlock is not also used to convey information about genetic ancestry. | ||
|
||
.. admonition:: New in v2 | ||
|
||
In VRS v1, a class with the same computational use as the `CisPhasedBlock` | ||
was defined and named the `Haplotype` class. This term is not used to describe | ||
this concept in v2, as the use of the `Haplotype` name created confusion in the | ||
community, due to the additional semantics of the term around genetic linkage | ||
and ancestry. In practice, implmentations transitioning from v1 to v2 should | ||
find the `CisPhasedBlock` able to accommodate the same information content | ||
from v1 `Haplotypes`. | ||
|
||
.. include:: ../../def/CisPhasedBlock.rst |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters