2017-10-27, 09:15
Hi All, We need to define what we each mean by "efficiency" and agree on a common definition? 
In the case of:-
https://www.meteomelin.be/staticfiles/bl...egion=1&id=
Would it be possible to develop this tool slightly more and have an average accumulated total for various longer periods, updating every five minutes and only giving the results for the last hour, whilst very useful, does not go far enough. One day, One week, One month?
This need not be "real-time" for the historic data and would show the affects over time, especially if several graphs could be seen on the same screen at the same time for comparison.
This "pattern" might also help with the station stats pages, i.e. more variable periods of time rather than just the last 24 hours, or the total stored data since the station started.
This would help in "optimising" our stations and reduce the overall load on the servers.
A better explanation of how the auto functions work, some basic instructions and improving their working, would make it easier for people who do not have a lot of time to fully monitor and manage their stations?
Information and education should be part of running a station, if we don't know what we are doing, or what the overall aim of the network is, then different stations are going to have different goals and this will lead to less network efficiency.
Maybe the LP filters could also be managed by the server to allow for wider bandwidth at times of low noise?
I know that I have maybe drifted off the main topic of "Efficiency," but surely these and some of the other suggestions made in these recent posts are inter-related.
Brian.
In the case of:-
https://www.meteomelin.be/staticfiles/bl...egion=1&id=
Would it be possible to develop this tool slightly more and have an average accumulated total for various longer periods, updating every five minutes and only giving the results for the last hour, whilst very useful, does not go far enough. One day, One week, One month?
This need not be "real-time" for the historic data and would show the affects over time, especially if several graphs could be seen on the same screen at the same time for comparison.
This "pattern" might also help with the station stats pages, i.e. more variable periods of time rather than just the last 24 hours, or the total stored data since the station started.
This would help in "optimising" our stations and reduce the overall load on the servers.
A better explanation of how the auto functions work, some basic instructions and improving their working, would make it easier for people who do not have a lot of time to fully monitor and manage their stations?
Information and education should be part of running a station, if we don't know what we are doing, or what the overall aim of the network is, then different stations are going to have different goals and this will lead to less network efficiency.
Maybe the LP filters could also be managed by the server to allow for wider bandwidth at times of low noise?
I know that I have maybe drifted off the main topic of "Efficiency," but surely these and some of the other suggestions made in these recent posts are inter-related.
Brian.
Stations: