[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #11389 [Globe]: Graphs should start/end at the same position
#11389: Graphs should start/end at the same position
-----------------------------+------------------
Reporter: rndm | Owner: rndm
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: Globe | Version:
Resolution: | Keywords:
Actual Points: | Parent ID:
Points: |
-----------------------------+------------------
Comment (by karsten):
So, your first variant displays `[min(x_start), max(x_end)]`.
And your second variant shows `[max(x_start), min(x_end)]`, right?
I think the first variant has the downside that there are missing values
to the left, which might confuse relay/bridge operators, because their
relay/bridge operator was running and submitting data at that time. This
is probably not as bad with missing values to the right, because operators
understand more quickly that their relay/bridge did not report that
specific type of data to display yet.
Your second variant indeed has the problem that the displayed period does
not match what the user selected.
How about a mix of the two: `[max(x_start), max(x_end)]`?
Those graphs will cover the selected period (under the assumption that the
relay/bridge was running long enough), and it will only have missing
values to the right.
Regarding calculating the average: with sliders this is not an issue,
because users will understand that the average is calculated for the full
graph, not just for the currently visible part. (And they sure wouldn't
expect that the average gets updated when they use the slider.) But once
you put these graphs into Globe-node which doesn't have sliders (IIUC),
you should only include data in the averages that is displayed in the
graph. So, maybe leave it as is and put in a TODO note for Globe-node?
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/11389#comment:1>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs