Open MarcelWaldvogel opened 2 years ago
In the first graph, there are two problems, correct?:
Second graph:
It might be helpful with a dataset that reproduces the issues.
Yes, that seems to be about it.
I have put the files (state: UTC midnight) into https://gpstime.trifence.ch/statistics.{GPS,200.160.7.197}. I hope they help (and thousand thanks for looking into it!)
In case the result is gnuplot-dependent: V5.4 patchlevel 1 on Debian bullseye (Raspberry Pi).
I wanted to change the percentile of the linear range to tune some graphs and I noticed two things:
linscalelimit
seems to assume a one-sided graph (from 0 to some +x), however, for two-sided graphs (-y to +x) it might be useful to have a lower and upper linscalelimit (maybe even symmetric around y=0)
I like the linlog layout, thanks @inkdot7!
However, it should ensure that a ytic beyond the maximum is set, to make the value visible. For example, in the following graph, the downward peak goes to -16 seconds (the time it took for the Raspi to reboot/resync time).
In the next graph, the ±RTT/2 lines are not visible at all and entirely cut off.
I expect that the outermost part becomes logarithmic; RTT/2 is ~100 ms.
It would be really great if these minor glitches could be improved.