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

inverse log operations make no sense

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
      None

      Description

      The inverse log functions for graph tracks don't make sense.

      Is it taking the inverse of the log ? If so, its doing it wrong.
      Is it taking the log of the inverse? nope.
      What does inverse log mean?
      The user guide has no info on this.

      We an take the inverse (which does seem to working) of the log (which does seem to be working) and we get the values we expect. And these values are very different from the values generated by inverse log.

      See the instructions on the track operations release testing page.
      https://wiki.transvar.org/display/ITD/Track+Operators
      Section: Single Track Operations - part 4 - inverse logs

        Attachments

          Issue Links

            Activity

            Hide
            nfreese Nowlan Freese added a comment -

            Fixed in IGBF-2666

            Show
            nfreese Nowlan Freese added a comment - Fixed in IGBF-2666
            Hide
            nfreese Nowlan Freese added a comment -

            For clarification, the inverse log is equivalent to an antilog.

            Show
            nfreese Nowlan Freese added a comment - For clarification, the inverse log is equivalent to an antilog.

              People

              • Assignee:
                Unassigned
                Reporter:
                ieclabau Ivory Blakley (Inactive)
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: