Details
-
Type:
Task
-
Status: Open (View Workflow)
-
Priority:
Major
-
Resolution: Unresolved
-
Labels:None
-
Epic Link:
Description
This story was created to serve as a a reminder for the task of testing Genome View in IGB to determine flaws.
This code may be rewritten/refactored in the near future and we should figure out what issues there are and the limitations/bottlenecks of genome view.
Things to check:
1) Bottlenecks of Genome View while loading several "chromosomes" (this may be related to available RAM)
2) Find "traps" in Genome View and create JIRA stories for what needs to be fixed/optimized.
3) What are the ways in which Genome View is used and how can it be optimized?
*Place additional notes here or in comments below.
Attachments
Activity
Field | Original Value | New Value |
---|---|---|
Epic Link | IGBF-526 [ 15589 ] |
Issue Type | Bug [ 1 ] | Task [ 3 ] |
Status | Open [ 1 ] | Needs Testing [ 10002 ] |
Sprint | Sprint 16 [ 21 ] |
Sprint | Sprint 17 [ 22 ] |
Rank | Ranked higher |
Sprint | Sprint 17 [ 22 ] |
Sprint | Sprint 18 [ 23 ] |
Rank | Ranked higher |
Epic Link | IGBF-526 [ 15589 ] | IGBF-497 [ 15559 ] |
Sprint | Sprint 18 [ 23 ] |
Sprint | Sprint 19 [ 24 ] |
Rank | Ranked higher |
Sprint | Sprint 19 [ 24 ] |
Rank | Ranked lower |
Rank | Ranked higher |
Issues found:
-Thick Start and Stop visualization issues
-Selection info coordinates system (using genome coordinates or chromosome coordinates)