jmeier64 / open-hardware-monitor

Automatically exported from code.google.com/p/open-hardware-monitor
0 stars 0 forks source link

Plotting of sensors other than temperature #139

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
It would be nice if I could select other sensors, not just temperature ones 
(CPU/GPU load, fan speeds) for plotting.

Original issue reported on code.google.com by lrdxgm on 15 Nov 2010 at 8:16

GoogleCodeExporter commented 9 years ago
This should been a feature request, only I didn't find any way to file it 
different type than "Defect"

Original comment by lrdxgm on 15 Nov 2010 at 8:17

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
That might be worth discussing, as I myself also have plotted temperature 
against fan speeds when first benchmarking a new videocard.

And fixed the type for ya ;)

Original comment by paulwere...@gmail.com on 22 Nov 2010 at 1:29

GoogleCodeExporter commented 9 years ago
Issue 228 has been merged into this issue.

Original comment by moel.mich on 29 May 2011 at 1:25

GoogleCodeExporter commented 9 years ago
Yep, would be much appreciated. I too want to plot fan speeds vs gpu/cpu core 
temperatures. 

Original comment by mkn...@gmail.com on 29 Jun 2011 at 3:58

GoogleCodeExporter commented 9 years ago
I have uploaded an alpha build with the new plotting implementation (based on 
OxyPlot). 

http://openhardwaremonitor.org/files/openhardwaremonitor-v0.5.1.11-alpha.zip

Let me know if there are any problems with the new plotting.

Original comment by moel.mich on 2 Jun 2013 at 5:10

GoogleCodeExporter commented 9 years ago
I have just checked it, and.. it's interesting :)

I thought of having all plots on the same bar area, using the same vertical 
area, just with different scale, not voltage/temp/etc. having an own part. I'm 
not saying it is bad (heck, lot better than without this feature), just unusual.

If you stick with this design, then there should be a way to adjust/reset the 
vertical scales, with this beta I could screw up the scales after 15 sec by 
just scrolling out over the bar area (got 10000000% on the load scale...), and 
only deleting the .config helped (but that killed my settings also..)

Original comment by lrdxgm on 2 Jun 2013 at 10:32

GoogleCodeExporter commented 9 years ago
You can double-click anywhere on the plot to auto-adjust the range for all axes 
(this includes the time axis). Double-clicking on an individual axis 
auto-adjusts only that axis (and keeps it in auto-adjust mode). You can pan 
(click and move) or zoom (mouse wheel) individual axes or the whole plot as 
well, depending where you apply the operation.

Would adding constraints on all axes help in general? Like the time is 
currently constraint to 0 - 24h, you can't go outside that. For load one could 
add constraints at 0 and 100%.

It might be possible to have all axes stacked over the same space, but I feared 
that it might get too confusing with lots of curves and axes. But I will see if 
I can make it an optional feature.

Original comment by moel.mich on 2 Jun 2013 at 10:43

GoogleCodeExporter commented 9 years ago
Oh nice, that is quite a powerful control over the ranges then.

Constraints would definitely help - I would put 0-max_value as a general 
constraint to value axes.

For the graphs, it's quite hard to see where one type ends and another starts 
(e.g. voltage and temperature) - please add some border between. I'd still 
welcome stacking everything together, but you can put that to low priority.

Original comment by lrdxgm on 3 Jun 2013 at 12:23

GoogleCodeExporter commented 9 years ago
A constraint to [minValue, maxValue] is too strict in general. If a fan is 
running at [999, 1020] RPM for some time, you don't want to limit the plot to 
just that range. I would prefer a range e.g. [900, 1200] there for example. 
Besides, when you start the application the interval [minValue, maxValue] has 
zero length (at first the min and max are the same), so it would mess up all 
axes.

A black line to separate the subplots is something that is really missing. I 
haven't added this so far because it is not supported by OxyPlot:

http://oxyplot.codeplex.com/workitem/10029

I will look into adding that to OxyPlot.

Original comment by moel.mich on 3 Jun 2013 at 7:17

GoogleCodeExporter commented 9 years ago
I have added the option to plot all sensors in the same space. For the subplot 
variant I have added a line to separate the plots. You can find the latest 
alpha version here:

http://openhardwaremonitor.org/files/openhardwaremonitor-v0.5.1.14-alpha.zip

Considering this issue fixed (unless some major problem shows up).

Original comment by moel.mich on 9 Jun 2013 at 5:59

GoogleCodeExporter commented 9 years ago
Issue 288 has been merged into this issue.

Original comment by moel.mich on 30 Jun 2013 at 5:44