diff options
| author | zsloan | 2022-04-13 13:26:15 -0500 |
|---|---|---|
| committer | GitHub | 2022-04-13 13:26:15 -0500 |
| commit | 3fcc18b40d48093d589dd65e541dbafe2623ca65 (patch) | |
| tree | ebfe5e74d16cd305822570efe3dd9b080b5860ca | |
| parent | 0c69d29e2fd23fbe36c7b65efc1316938de01ae1 (diff) | |
| download | gn-gemtext-3fcc18b40d48093d589dd65e541dbafe2623ca65.tar.gz | |
Update mapping-zoom-bug.gmi
| -rw-r--r-- | issues/mapping-zoom-bug.gmi | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/issues/mapping-zoom-bug.gmi b/issues/mapping-zoom-bug.gmi index 14ca2d1..9218df7 100644 --- a/issues/mapping-zoom-bug.gmi +++ b/issues/mapping-zoom-bug.gmi @@ -9,3 +9,6 @@ From RWW: For the following trait, if you zoom into a range for a specific Chrom * keywords: bug * status: in progress * 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). |