-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Linlog cuts off extremes #9
Comments
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:
|
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.
The text was updated successfully, but these errors were encountered: