diff options
| author | zsloan | 2022-04-13 13:26:39 -0500 |
|---|---|---|
| committer | GitHub | 2022-04-13 13:26:39 -0500 |
| commit | 948f134353dab810a0d6acd22f0f35bcd8582871 (patch) | |
| tree | 17c566b306d9084ccab7baa3ec7670739620ba2a /issues | |
| parent | 3fcc18b40d48093d589dd65e541dbafe2623ca65 (diff) | |
| download | gn-gemtext-948f134353dab810a0d6acd22f0f35bcd8582871.tar.gz | |
Update mapping-zoom-bug.gmi
Diffstat (limited to 'issues')
| -rw-r--r-- | issues/mapping-zoom-bug.gmi | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/issues/mapping-zoom-bug.gmi b/issues/mapping-zoom-bug.gmi index 9218df7..f4b3d0a 100644 --- a/issues/mapping-zoom-bug.gmi +++ b/issues/mapping-zoom-bug.gmi @@ -11,4 +11,4 @@ From RWW: For the following trait, if you zoom into a range for a specific Chrom * priority: high This issue appears to be caused by marker namees being duplicated. If a marker name appears in an earlier chromosome, it ends up displayed first in the GEMMA results for a later chromosome. -For example, if rs0000000071 is in both chromosome 1 and chromosome 7, it will show up first in the chromosome 7 result file even if it's position is 122Mb. This causes a problem in the mapping display code, since the loop is set to break when the marker position is > the end position set by the user (in this case by selecting a specific Mb interval). +For example, if rs0000000071 is in both chromosome 1 and chromosome 7, it will show up first in the chromosome 7 result file even if its position is 122Mb. This causes a problem in the mapping display code, since the loop is set to break when the marker position is > the end position set by the user (in this case by selecting a specific Mb interval). |