Uploaded image for project: 'Deep Backlog'
  1. Deep Backlog
  2. DB-97

Color by score threshold sensitivity (edge case)

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Labels:
      None

      Description

      Overview: I believe it is an issue with some of the initial triangles since newer ones don't always exhibit this behavior? Maybe a integer comparator used? It may be using Integer or doing some sort of decimal rounding causing unintuitive behavior.

      To Reproduce: Open attached file. Insert 'chr3:21,503,023-21,513,023' into "Quick Search". Click "Load Data". You should now see two reads. Right click on the "track title" choose "Color by..." choose "Score" and click "Edit". At the top of the heat-map gradient chooser you should see 4 triangles. Delete the 3rd one. Click the second one (YOU MUST CLICK IT OR TEXT ENTRY GOES NOWHERE!) Set the second one to 68.28 using the "Attribute Value" text entry. Hit return to set it (YOU MUST HIT RETURN TO SEE IT RENDER. This is not a problem here when we only have one threshold but when you have multiples you must always remember to hit return!). You should now have a screen like the screenshot [See attachment] Click "OK"

      Observe: The threshold is 68.28 making anything above this white. Yet 68.29 is still black.

      Conclusion: Behavior is unintuitive to an analyst that is purposely setting thresholds to make max scoring reads stick out.

      Found on IGB 8.0.2 (16020)

        Attachments

          Activity

          kyle Kyle Suttlemyre (Inactive) created issue -
          kyle Kyle Suttlemyre (Inactive) made changes -
          Field Original Value New Value
          Attachment AP1_admin_BindingSites.bed [ 12367 ]
          kyle Kyle Suttlemyre (Inactive) made changes -
          Description Overview: I believe it is an issue with some of the initial triangles since newer ones don't always exhibit this behavior? Maybe a integer comparator used? It may be using Integer or doing some sort of decimal rounding causing unintuitive behavior.


          To Reproduce: Open attached file. Insert 'chr3:21,503,023-21,513,023' into "Quick Search". Click "Load Data". You should now see two reads. Right click on the "track title" choose "Color by..." choose "Score" and click "Edit". At the top of the heatmap gradient chooser you should see 4 triangles. Delete the 3rd one. Click the second one (YOU MUST CLICK IT OR TEXT ENTRY GOES NOWHERE!) Set the second one to 68.28 using the "Attribute Value" text entry. Hit return to set it (YOU MUST HIT RETURN TO SEE IT RENDER. This is not a problem here when we only have one threshold but when you have multiples you must always remember to hit return!). You should now have a screen like the screenshot [See attachment] Click "OK"


          Observe: The threshold is 68.28 making anything above this white. Yet 68.29 is still black.

          Conclusion: Behavior is unintuitive to an analyst that is purposely setting thresholds to make max scoring reads stick out.
          Overview: I believe it is an issue with some of the initial triangles since newer ones don't always exhibit this behavior? Maybe a integer comparator used? It may be using Integer or doing some sort of decimal rounding causing unintuitive behavior.


          To Reproduce: Open attached file. Insert 'chr3:21,503,023-21,513,023' into "Quick Search". Click "Load Data". You should now see two reads. Right click on the "track title" choose "Color by..." choose "Score" and click "Edit". At the top of the heat-map gradient chooser you should see 4 triangles. Delete the 3rd one. Click the second one (YOU MUST CLICK IT OR TEXT ENTRY GOES NOWHERE!) Set the second one to 68.28 using the "Attribute Value" text entry. Hit return to set it (YOU MUST HIT RETURN TO SEE IT RENDER. This is not a problem here when we only have one threshold but when you have multiples you must always remember to hit return!). You should now have a screen like the screenshot [See attachment] Click "OK"


          Observe: The threshold is 68.28 making anything above this white. Yet 68.29 is still black.

          Conclusion: Behavior is unintuitive to an analyst that is purposely setting thresholds to make max scoring reads stick out.

          Found on IGB 8.0.2 (16020)
          ann.loraine Ann Loraine made changes -
          Project IGB 8.1 [ 10640 ] IGB 8.2 [ 10840 ]
          Key IGBE-106 IGBF-3
          kyle Kyle Suttlemyre (Inactive) made changes -
          Assignee Ann Loraine [ aloraine ]
          dcnorris David Norris (Inactive) made changes -
          Workflow classic default workflow [ 14296 ] Loraine Lab Workflow [ 14596 ]
          dcnorris David Norris (Inactive) made changes -
          Rank Ranked lower
          mason Mason Meyer (Inactive) made changes -
          Epic Link IGBF-497 [ 15559 ]
          mason Mason Meyer (Inactive) made changes -
          Rank Ranked lower
          mason Mason Meyer (Inactive) made changes -
          Rank Ranked higher
          mason Mason Meyer (Inactive) made changes -
          Rank Ranked higher
          mason Mason Meyer (Inactive) made changes -
          Project IGB [ 10840 ] Deep Backlog [ 11041 ]
          Key IGBF-3 DB-97
          Workflow Loraine Lab Workflow [ 14596 ] jira [ 16804 ]
          Reporter Kyle Suttlemyre [ kyle ] Mason Meyer [ mason ]

            People

            • Assignee:
              Unassigned
              Reporter:
              mason Mason Meyer (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated: