search

rcrum003 / HiveControl

Alternative software for use with HiveTool suite of software.
GNU General Public License v2.0
25 stars 13 forks source link

Time Range Slider Enhancement #19

Closed NapaOgden closed 5 years ago

NapaOgden commented 8 years ago

Here I go again.... Would it be too much to ask to add the time scale slider as seen on Highstock trend objects? Is there a better place to add feature requests, I see the catagory but can only find issues entry field? Ref. http://www.highcharts.com/stock/demo/compare/dark-unica

rcrum003 commented 8 years ago

After awhile, the slider had to process too much data and doesn't render well in mobile browsers because of the memory.

Sent from my iPhone

On Apr 2, 2016, at 12:03 PM, NapaOgden notifications@github.com wrote:

Here I go again.... Would it be too much to ask to add the time scale slider as seen on Highstock trend objects? Is there a better place to add feature requests, I see the catagory but can only find issues entry field? Ref. http://www.highcharts.com/stock/demo/compare/dark-unica

— You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub

NapaOgden commented 8 years ago

Would a workaround be feasible? Maybe only reading & displaying daily average values when the range exceeds some critical size like 60 days so as to limit the processing & memory use? I don't think detail would be sacrificed if, considering a screen resolution of perhaps 1366X768 (27% of all web dev).

An example of ten 5 minute samples over 24 hours = 2880 data points X 60 days =17,280 data points read or 1,728 horizontal points per pen imaged. I'm comparing lines resolution to data points which may be a bad comparison? 1 year would be 10,511 data points if all daily average values were displayed. How much processing would this involve?

Would this be doable? Is the task too complex for the benefit of flexibility? I think we need to log midnight to midnight daily averages (mean) anyway. In this way we can display daily gain/loss, a needed enhancement.

Adrian

rcrum003 commented 8 years ago

You can currently zoom in, without the sliders, that is already supported..

On Apr 2, 2016, at 12:40 PM, NapaOgden notifications@github.com wrote:

Would a workaround be feasible? Maybe only reading & displaying daily average values when the range exceeds some critical size like 60 days so as to limit the processing & memory use? I don't think detail would be sacrificed if, considering a screen resolution of perhaps 1366X768 (27% of all web dev).

An example of ten 5 minute samples over 24 hours = 2880 data points X 60 days =17,280 data points read or 1,728 horizontal points per pen imaged. I'm comparing lines resolution to data points which may be a bad comparison? 1 year would be 10,511 data points if all daily average values were displayed. How much processing would this involve?

Would this be doable? Is the task too complex for the benefit of flexibility? I think we need to log midnight to midnight daily averages (mean) anyway. In this way we can display daily gain/loss, a needed enhancement.

Adrian

— You are receiving this because you commented. Reply to this email directly or view it on GitHub https://github.com/rcrum003/HiveControl/issues/19#issuecomment-204755664

NapaOgden commented 8 years ago

Could day, week, month - backward / forward be easily added

On Sat, Apr 2, 2016 at 10:19 AM, Ryan notifications@github.com wrote:

You can currently zoom in, without the sliders, that is already supported..

On Apr 2, 2016, at 12:40 PM, NapaOgden notifications@github.com wrote:

Would a workaround be feasible? Maybe only reading & displaying daily average values when the range exceeds some critical size like 60 days so as to limit the processing & memory use? I don't think detail would be sacrificed if, considering a screen resolution of perhaps 1366X768 (27% of all web dev).

An example of ten 5 minute samples over 24 hours = 2880 data points X 60 days =17,280 data points read or 1,728 horizontal points per pen imaged. I'm comparing lines resolution to data points which may be a bad comparison? 1 year would be 10,511 data points if all daily average values were displayed. How much processing would this involve?

Would this be doable? Is the task too complex for the benefit of flexibility? I think we need to log midnight to midnight daily averages (mean) anyway. In this way we can display daily gain/loss, a needed enhancement.

Adrian

— You are receiving this because you commented. Reply to this email directly or view it on GitHub < https://github.com/rcrum003/HiveControl/issues/19#issuecomment-204755664>

— You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub https://github.com/rcrum003/HiveControl/issues/19#issuecomment-204760366

rcrum003 commented 8 years ago

Also, don't forget, we should be logging into the DB the actual values. Anything like daily average, etc, should be left to code that analyzes the DB. If you look at the detail chart page, we show you daily average and other summary type stats.

NapaOgden commented 8 years ago

Good point, are the daily averages derived from 24 hour midnight to midnight values or the preceding rolling 24 hours? I suggest midnight to midnight as rolling will differ depending on when queried.

On Sat, Apr 2, 2016 at 10:43 AM, Ryan notifications@github.com wrote:

Also, don't forget, we should be logging into the DB the actual values. Anything like daily average, etc, should be left to code that analyzes the DB. If you look at the detail chart page, we show you daily average and other summary type stats.

— You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub https://github.com/rcrum003/HiveControl/issues/19#issuecomment-204764817

rcrum003 commented 5 years ago

This is now supported on HiveControl.org for individual hives.