You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment the coloring scheme is a bit useless. I mean it doesn't really make sense to color by columns when each row is showing something different.
E.g. if the delta is negative, bid as well as ask is red. But really ask still gives buys so in this case, it should be a really light green for ask and a more deep red for the bids to indicate that there are more bids than asks. Also for example where the row "Trades" has its maximum everything in this column is black, but this column is clearly not the maximum for both of the other rows.
Basically, my suggestion is that you should change the color calculations from columns to rows. So every row aka every statistic should have its own color selector (or maybe even two for the min and the max value). For example for "Ask" one chooses black for the min value and green for the max value. And then the whole row has a gradient between black and green based on how big the values are (so there is no red at all in this row).
This also allows for more color variation between for example "Trades", "Hight" and "Duration".
But if you can choose the color for yourself or not is actually not really important. The more important thing in my opinion is that you change the color calculations from columns to rows.
If you implement this you should connect the calculations for Bid and Ask, this means if there are a lot of buys at the moment and really low sales happening the color for the maximum amount of sales should still be a light red and not a deep red.
Example:
Ask: 5M 6M 10M 3M 8M
Bid: 12K 50K 40K 80K 20K
Gradient for Bid and Ask should be calculated based on min=12K max=10M
So even 80K which is the highest value for the bids should still be a light red (and not a deep red) this way you can fast and clearly see the discrepancy between both of them.
The text was updated successfully, but these errors were encountered:
Sebastian7700
changed the title
Cluster Statistics Improvement
Cluster Statistics Color Improvement
Feb 4, 2022
At the moment the coloring scheme is a bit useless. I mean it doesn't really make sense to color by columns when each row is showing something different.
E.g. if the delta is negative, bid as well as ask is red. But really ask still gives buys so in this case, it should be a really light green for ask and a more deep red for the bids to indicate that there are more bids than asks. Also for example where the row "Trades" has its maximum everything in this column is black, but this column is clearly not the maximum for both of the other rows.
Basically, my suggestion is that you should change the color calculations from columns to rows. So every row aka every statistic should have its own color selector (or maybe even two for the min and the max value). For example for "Ask" one chooses black for the min value and green for the max value. And then the whole row has a gradient between black and green based on how big the values are (so there is no red at all in this row).
This also allows for more color variation between for example "Trades", "Hight" and "Duration".
But if you can choose the color for yourself or not is actually not really important. The more important thing in my opinion is that you change the color calculations from columns to rows.
If you implement this you should connect the calculations for Bid and Ask, this means if there are a lot of buys at the moment and really low sales happening the color for the maximum amount of sales should still be a light red and not a deep red.
Example:
Ask: 5M 6M 10M 3M 8M
Bid: 12K 50K 40K 80K 20K
Gradient for Bid and Ask should be calculated based on min=12K max=10M
So even 80K which is the highest value for the bids should still be a light red (and not a deep red) this way you can fast and clearly see the discrepancy between both of them.
The text was updated successfully, but these errors were encountered: