Details
-
Type:
Task
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Labels:None
-
Story Points:0.25
-
Epic Link:
-
Sprint:Fall 5 Nov 9 - Nov 20, Fall 6 Nov 30 - Dec 11
Description
Attachments
Issue Links
Activity
| Field | Original Value | New Value |
|---|---|---|
| Epic Link |
|
| Rank | Ranked higher |
| Status | To-Do [ 10305 ] | In Progress [ 3 ] |
| Assignee | Nowlan Freese [ nfreese ] |
The Single Track Operations - part 4 - inverse logs section of the testing does not appear to be correct. Where it says that "Diff Inverse Inverse case above, these blue tracks should be all 0-values." - these numbers should not equate to zero. The inverse log operator appears to be antilog. So the inverse log2 of 4 should be 16 (which is what is shown in IGB). The log2 of 4 is 2. The inverse of 2 (1/2) is 0.5 (which is what is shown in IGB). The diff of 16 and 0.5 is not 0.
It is unclear to me what this section is trying to test, but I think it needs to be rewritten.
Tested on Linux Fedora 27 GNOME Version 3.26.2
| Assignee | Nowlan Freese [ nfreese ] |
| Status | In Progress [ 3 ] | Needs 1st Level Review [ 10005 ] |
| Status | Needs 1st Level Review [ 10005 ] | First Level Review in Progress [ 10301 ] |
| Assignee | Sai Supreeth Segu [ ssegu ] |
| Assignee | Sai Supreeth Segu [ ssegu ] |
| Status | First Level Review in Progress [ 10301 ] | Needs 1st Level Review [ 10005 ] |
| Sprint | Fall 5 Nov 9 - Nov 20 [ 108 ] | Fall 5 Nov 9 - Nov 20, Fall 6 Nov 23 - Dec 4 [ 108, 109 ] |
| Rank | Ranked higher |
| Link | This issue relates to IGBF-2653 [ IGBF-2653 ] |
| Status | Needs 1st Level Review [ 10005 ] | First Level Review in Progress [ 10301 ] |
| Assignee | Ann Loraine [ aloraine ] |
Created new issue to update testing instructions - see link. Moving to closed.
| Status | First Level Review in Progress [ 10301 ] | Ready for Pull Request [ 10304 ] |
| Status | Ready for Pull Request [ 10304 ] | Pull Request Submitted [ 10101 ] |
| Status | Pull Request Submitted [ 10101 ] | Reviewing Pull Request [ 10303 ] |
| Status | Reviewing Pull Request [ 10303 ] | Merged Needs Testing [ 10002 ] |
| Status | Merged Needs Testing [ 10002 ] | Post-merge Testing In Progress [ 10003 ] |
| Resolution | Done [ 10000 ] | |
| Status | Post-merge Testing In Progress [ 10003 ] | Closed [ 6 ] |
| Assignee | Ann Loraine [ aloraine ] | Nowlan Freese [ nfreese ] |
The order of the multi-track graph operations does not follow the testing instructions. In both 9.1.4 and 9.1.6 the first operation for the multi-graph track operation will produce a new graph of the same color as the first of the two graphs selected (if I select the green graph first then shift click to select the blue graph, create a new graph, the color of the new graph will be green). If the user then immediately clicks Go under multi-graph it will produce a new graph that is the color of whichever of the two selected graphs is on top. So the order of the selected graph only matters for the initial multi-graph operation in regards to color. Subsequent multi-graph operations graph colors are determined by which graph is on top.