Closed tadmorgan closed 2 years ago
Not yet. In progress in https://github.com/nasa/openmct/pull/4710
We have an initial version in the log-plots
and experimental-plotly-log-plots
branches. But some more work needs to be done. A few things we are thinking about:
return log(point.y)
if (point.y < 0) return -log(-point.y)
return log(point.y + (1 - n))
where n
is the point at which the log formula graph (not our log plot) crosses the X axis. A value of 0.1 which means the log formula graph will be shifted left so that the intersection point is 0.1. This allows our log plot (not log formula graph) to be useful for values above 0.1 instead of above 1.1 - n
, if (point.y < 0) return -log(-point.y + (1 - n))
return log(point.y) + n
n
value, constrained to be 0
or higher, using a slider inputUpdated playground. All plots toggled off except symmetrical log functions: https://www.desmos.com/calculator/htkxrlto3a
A better one showing symlog, scaled symlog, and scaled antisymlog, with a slider to adjust the scale value: https://www.desmos.com/calculator/2pcxvmsd6y
Good chat with @trusktr today:
Testing:
I'm seeing an issue in an overlay plot when using a sine wave generator with log mode turned on. If I turn on log mode, save, and refresh, the plot isn't displaying correctly.
I'm seeing this error:
We could be doing a better job of formatting y-axis values in log mode. Instead of showing something like this:
We should be rounding the y-axis values to the nearest whole number in this case.
@khalidadil Sounds like maybe a version of this issue - https://github.com/nasa/openmct/issues/5039?
I am also seeing this issue for what it's worth, with non-SWG telemetry points as well.
@akhenry I just checked, and autoscale was turned on for me.
Verified not fixed Testathon 04-25-22:
Log scale on
@shefalijoshi to investigate https://github.com/nasa/openmct/issues/2297#issuecomment-1109075202
I think maybe we could use toFixed(2) instead of whole numbers to solve the long ticks issue? Otherwise if the range of values is small (0-1 for instance) then all the ticks would be either all 0 or all 1 which would be odd.
Verified fixed, y-axis labels look awesome now!
NOT fixed Testathon 4-28-22. Ticks end up being duplicated when the plotted value is < 1.
After no incoming data for a period:
This intentionally restores the behavior seen in https://github.com/nasa/openmct/issues/2297#issuecomment-1109114296 which will need to be fixed in a separate issue, but does not block release.
Important note This cannot be verified with sine wave generators. SWGs have a custom formatter which will round all values to 2 decimal places. In this case the precision is already lost before the log plots format the values.
This change appears to be fixed in testathon 05/02. On inspecting an overlay plot with log scale enabled, the scale values do not repeat and instead show values without clipping the # of decimal places (increasing precision).
Verified fixed.
Confirmed Fixed 05/02. Seeing the same behavior as Michael.
Is it possible to set a plot axis to logarithmic scale?