Uploaded image for project: 'IGB'
  1. IGB
  2. IGBF-2344

Normalize by entire genome instead of by individual chromosome

    Details

    • Type: Improvement
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
      None
    • Story Points:
      1
    • Sprint:
      Spring 7 : 13 Apr to 24 Apr, Spring 8 : 24 Apr to 8 May, Spring 8 : 11 May to 25 May

      Description

      Right now, the graph made from a BAI file is scaled, with the lowest value being 0 and the largest value being 1.

      The scaling is currently done by chromosome. That is, the y axis values appearing on the screen are a fraction of the sum of values for the chromosome being shown. For example, if the total values for a chromosome is 1000 and the value for a "bin" region on the chromosome is 100, then the y axis value for that bin would be 100/1000 = 0.1.

      Instead, let's scale by values for the entire genome.

      If we do this, then a user will be able to load the entire file and then click "genome" in the Current Sequence tab and then instantly recognize larger-scale differences in the sequenced genome versus the reference genome. This will be super-useful for helping researchers recognize when a patient (for example) has an extra copy of an entire chromosome. For example, some people with trisomy 21 (Down's Syndrome) have duplications of the entire chromosome. If we make the proposed change, then such cases will be very easy to recognize in IGB.

      Suggestion that may be useful:
      To avoid very small fractional values, multiple by a scaling factor? Or, we can leave that to the user. They can easily multiply the entire graph by a number to make a new one.

        Attachments

          Activity

          There are no comments yet on this issue.

            People

            • Assignee:
              pbole Pawan Bole (Inactive)
              Reporter:
              ann.loraine Ann Loraine
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: