Skip to content
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

local dashboard: messages per hour and day #267

Open
g7ruh opened this issue May 11, 2024 · 9 comments
Open

local dashboard: messages per hour and day #267

g7ruh opened this issue May 11, 2024 · 9 comments

Comments

@g7ruh
Copy link

g7ruh commented May 11, 2024

Jasper, I notice that the vessel count on the messages per hour and per day "flat line" as they are too low relative to the message count.

I guess they need a scale on the RHS of the graph like you did on aiscatcher.org.
As you can see, another busy (sunny and light winds) day in The Solent:

image

Now 700 vessels!

image

Regards
Roger

@jvde-github
Copy link
Owner

Yes, the idea worked well for aiscatcher.org so will implement here as well. Like it.

@g7ruh
Copy link
Author

g7ruh commented May 11, 2024

Let me know when and I will test.

Also now you have vessels per minute in messages per minute, I guess we don't need the separate vessels per minute graph?

@jvde-github
Copy link
Owner

I tried to solve it by adding a second axis. Partially in but need to clean it up. We can now get rid of the selectste graph if needed.

it is in, but will tweak in the coming days

@g7ruh
Copy link
Author

g7ruh commented May 11, 2024

Thanks Jasper,

I will test and see what I think. The other graph takes up space and is no longer needed. For a while I have thought that and having a day or week related view on number of vessels is more informative than just per minute.

Let me know when you tweak it next and I can have a look.

Roger

@jvde-github
Copy link
Owner

You can view on your online dashboard:
image

I think the orange is a bit difficult to see (so perhaps will make a darker color) and don't like the space taken by the large numbers (so perhaps say 600K instead of 600,000)....

@g7ruh
Copy link
Author

g7ruh commented May 11, 2024

Hi Jasper,
thanks (as always) for the high speed response! Having installed the latest version....

I agree, orange is wrong, it needs to be a high contrast change from the colours of the base graph as it is different data, not directly related to that graph. It also gets lost in the other graph colours.

I would say red, but bearing in mind that a large number of the population are red-green colour blind, maybe black is good.

The black line is the other scale and colours are the message count: easy to remember and for the brain to interpret as very different, therefore the other scale.

I had a salutary experience many years ago developing prototype software for a large organisation where we showed finance changes in green for up and red for down.... the senior person in that part of the finance business said " yes very good but I am red-green colour blind so they both look " grey" to me.

I agree the scales are a bit "large" so (pun) scaling them down is better. I agree 60K or 600K is much better: it makes the graph area bigger: the whole point of a graph!

hope that helps
Roger

@Taxom
Copy link

Taxom commented May 11, 2024

You can view on your online dashboard: image

I think the orange is a bit difficult to see (so perhaps will make a darker color) and don't like the space taken by the large numbers (so perhaps say 600K instead of 600,000)....

Maybe use a science format like "1e5"

@g7ruh
Copy link
Author

g7ruh commented May 15, 2024

Maybe use a science format like "1e5"
@Taxom

Trouble is that I suspect your average butcher, baker and candlestick maker and sailor too may not understand the format but the "K" shorthand is known by lots of folks now because of exposure to things computing.

Roger

@Taxom
Copy link

Taxom commented May 16, 2024

Maybe use a science format like "1e5"
@Taxom

Trouble is that I suspect your average butcher, baker and candlestick maker and sailor too may not understand the format but the "K" shorthand is known by lots of folks now because of exposure to things computing.

Roger

Okay, well then lowercase would be more correct. 1k not 1K

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants