| Summary: | Adaptive automatic Y data range as separate option | ||
|---|---|---|---|
| Product: | [Applications] plasma-systemmonitor | Reporter: | nttkde <watisthispoo> |
| Component: | general | Assignee: | KSysGuard Developers <ksysguard-bugs> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | wishlist | CC: | ahiemstra, kdedev, nate, plasma-bugs-null |
| Priority: | NOR | ||
| Version First Reported In: | 5.22.0 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | weird systemp and cpufan charts | ||
I'm sorry we weren't able to address this before now. The system monitor has had a lot of work since this request was opened. I'm not seeing the buggy behavior you described after setting up the same sensors on git-master on my system. Can you let us know if this is still an issue with Plasma 6.3.5 or later? Thanks! 🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone! 🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME. |
Created attachment 139263 [details] weird systemp and cpufan charts Would be nice to have the automatic adaptive range (like in the network line chart on History page or old ksysguard) as a third user-selectable option, in addition to the now-default automatic fixed range from a sensor and manual fixed range. -Some sensors seem to have the limits missing or incorrect and probably not all can be easily fixed. That results in some weird-looking graphs that require user action to be corrected. (Maybe automatic adaptation/range adjustment could be done when an actual value doesn't fit into the sensor limits, though that doesn't help if the limit is too large.) -User can then of course set a fixed manual range, but for that they need to know the maximum. Eg. I can't remember what's the max speed of my CPU fan without finding and googling its model number. Would be easier to just enable the adaptive range than guessing/googling. -I was quite okay with the adaptive range in ksysguard for sensors that usually vary within a smallish range compared to the total possible range. It kind of "zooms in" a bit. The extra 'empty space' on top isn't always necessary in my opinion. I might prefer adaptive range when it's more important to know how the value changes in relation to itself than what percentage it is of the absolute maximum. Might be also cool to have the manual fixed range with options for auto adaptation if value over/undershoots it; to zoom at a specific value range when possible. ------------------------------- Just as an example of some buggy predefined min&max values, below is an excerpt from 'sensors' command, and a corresponding System Monitor screenshot is attached too. temp1 (SYS Temp) somehow has high value of 2C, so that overshoots a bit... fan2 (CPU Fan) chart doesn't really work. If I've understood right the fan min value is rather related to the monitoring chip resolution than the actual rpm that depends on the fan itself. Should fans be on adaptive scale by default? w83627dhg-isa-0a10 Adapter: ISA adapter Vcore: 1.40 V (min = +0.00 V, max = +1.74 V) in1: 1.82 V (min = +0.00 V, max = +0.07 V) ALARM AVCC: 3.25 V (min = +2.98 V, max = +3.63 V) +3.3V: 3.25 V (min = +2.98 V, max = +3.63 V) in4: 1.10 V (min = +1.02 V, max = +0.00 V) ALARM in5: 880.00 mV (min = +0.02 V, max = +0.00 V) ALARM in6: 1.56 V (min = +1.02 V, max = +0.00 V) ALARM 3VSB: 3.25 V (min = +2.98 V, max = +3.63 V) Vbat: 3.20 V (min = +2.70 V, max = +3.63 V) fan1: 0 RPM (min = 659 RPM, div = 128) ALARM fan2: 847 RPM (min = 21093 RPM, div = 8) ALARM fan3: 0 RPM (min = 1318 RPM, div = 128) ALARM fan4: 4687 RPM (min = 168750 RPM, div = 8) ALARM fan5: 0 RPM (min = 10546 RPM, div = 128) ALARM temp1: +43.0°C (high = +2.0°C, hyst = +0.0°C) ALARM sensor = thermistor temp2: +29.0°C (high = +80.0°C, hyst = +75.0°C) sensor = CPU diode temp3: +63.0°C (high = +117.0°C, hyst = +117.0°C) sensor = thermistor cpu0_vid: +0.000 V intrusion0: ALARM