It appears that the percentage of load on any of the CPU meters is affected by the update interval. In my opinion this should not be the case. The percentage of load should not be affected by the update interval, only be updated more frequently. If I set the update interval to 3 or more seconds, the meter stays mostly at 100%. Whereas, when I set the interval to 0.1 seconds, the load is shown as 0-10%. Setting the interval to 1 second appears to show a more correct percentage of load (around 40-50% with some CPU intensive things running for testing).
After digging a bit deeper I found the following line in the API source code:
Quote:
#load = int(load / .update_interval)
I'm sure there's a good reason why this was disabled here, and I think perhaps it was not updated in the RingSensorsScreenlet.py merely by accident. I changed the following line in RingSensorsScreenlet.py and it appears to be working correctly, at any update interval.
Quote:
I found out that the nvidia GPU core sensor name always changes depending on its current temperature e.g nvidia GPU core: 75C . The problem arise when user restarted the pc and RingSensor setting RingSensor.ini couldn't find the right sensor which the name had changed (because temperature changed). Do you have any fix for this?
- Ubuntu Hardy Heron LTS 64-bit
- nvidia 8400M GS
- RingSensors v0.3
Thanks...
It's fixable, you need to fix the screenlets.sensors python library.
The version 0.3 I'm using, I was able to remove the temperature by modifying line 871, in the sensors_get_sensors_list method, where it's doing output.append.
There are a whole bunch of problems with that code, it should be rewritten with a structured set of classes in mind, instead of the higgled, mangle of functions it currently is.
In the meanwhile, I solved a similar problem I had on my ubuntu box, manually adding this line:
sensor=acpi temperature THRM
at the end of my Ringsensors.ini file.
Hope this can be useful to someone else.
Those screenlets are really great! But I have A problem with the CPU temperature. Here is the link of a screenshot to realise what the problem is.
http://img218.imageshack.us/img218/9691/screenshotkr1.png
And here is the output of the sensors command:
CPU Temp: +42.5°C (high = +80.0°C, hyst = +75.0°C) sensor = thermistor
I cant get the wifi ring to work, constantly shows 100%. Tried other sensors, they worked fine. When i do iwconfig my signal is about 60/100...
Restarting screenlet didnt help either.
my wireless conf: http://pastebin.com/m1ff2dcf
Absolutely love these sensors, as-well as the ClockRing, looks beautiful.
When I set a ring to wlan0 it doesn't give any signal details, just stuck at 100% (which unfortunately isn't true...) - is there something I can edit in the RingSensors5.ini to get signal details?
Thanks again for these awesome Screenlets.
... okay, stupid me. I simply restarted all the screenlets and it was working just fine.
... as i'm already posting though - is there any way you could put the date in the middle of the ClockRing in kinda the same format as the SensorRings?
Thanks
Hello. Thank you so much for creating ring sensors! How do I prevent certain ring sensors that I opened previously from starting on every launch? Thanks in advance! :)
Ratings & Comments
17 Comments
It appears that the percentage of load on any of the CPU meters is affected by the update interval. In my opinion this should not be the case. The percentage of load should not be affected by the update interval, only be updated more frequently. If I set the update interval to 3 or more seconds, the meter stays mostly at 100%. Whereas, when I set the interval to 0.1 seconds, the load is shown as 0-10%. Setting the interval to 1 second appears to show a more correct percentage of load (around 40-50% with some CPU intensive things running for testing). After digging a bit deeper I found the following line in the API source code: Quote:#load = int(load / .update_interval)
I'm sure there's a good reason why this was disabled here, and I think perhaps it was not updated in the RingSensorsScreenlet.py merely by accident. I changed the following line in RingSensorsScreenlet.py and it appears to be working correctly, at any update interval.
Quote:self.load = int((self.new_cpu - self.old_cpu) / self.update_interval)
Hi,in the drop down list i see no option for my temperature sensors,i have a nvidia 8600M GT Ubuntu x64 9.04
Hi, how can I enable WiFi screenlet? I have only this sensors for choice... http://img223.imageshack.us/img223/3537/snmekobrazovkyringsensoty8.png
I found out that the nvidia GPU core sensor name always changes depending on its current temperature e.g nvidia GPU core: 75C . The problem arise when user restarted the pc and RingSensor setting RingSensor.ini couldn't find the right sensor which the name had changed (because temperature changed). Do you have any fix for this? - Ubuntu Hardy Heron LTS 64-bit - nvidia 8400M GS - RingSensors v0.3 Thanks...
It's fixable, you need to fix the screenlets.sensors python library. The version 0.3 I'm using, I was able to remove the temperature by modifying line 871, in the sensors_get_sensors_list method, where it's doing output.append. There are a whole bunch of problems with that code, it should be rewritten with a structured set of classes in mind, instead of the higgled, mangle of functions it currently is.
In the meanwhile, I solved a similar problem I had on my ubuntu box, manually adding this line: sensor=acpi temperature THRM at the end of my Ringsensors.ini file. Hope this can be useful to someone else.
I don't understand why there are 3 CPU (CPU0/1/2) all of which show some load when my CPU only has 2 cores, is there something I'm missing here????
CPU0 shows the average usage, CPU1 the usage of the first core and the CPU2 the usage of the second core. Any ideas about my problem I wrote above?
Are you sure? If I show enable all three sensors it doesn't seem that 0 is the average of 1 and 2...
Those screenlets are really great! But I have A problem with the CPU temperature. Here is the link of a screenshot to realise what the problem is. http://img218.imageshack.us/img218/9691/screenshotkr1.png And here is the output of the sensors command: CPU Temp: +42.5°C (high = +80.0°C, hyst = +75.0°C) sensor = thermistor
I cant get the wifi ring to work, constantly shows 100%. Tried other sensors, they worked fine. When i do iwconfig my signal is about 60/100... Restarting screenlet didnt help either. my wireless conf: http://pastebin.com/m1ff2dcf
Absolutely love these sensors, as-well as the ClockRing, looks beautiful. When I set a ring to wlan0 it doesn't give any signal details, just stuck at 100% (which unfortunately isn't true...) - is there something I can edit in the RingSensors5.ini to get signal details? Thanks again for these awesome Screenlets.
... okay, stupid me. I simply restarted all the screenlets and it was working just fine. ... as i'm already posting though - is there any way you could put the date in the middle of the ClockRing in kinda the same format as the SensorRings? Thanks
Loving these just what i was after. How can i add other sensors, would love a full set of these network clock
Looks good :)
:)
Hello. Thank you so much for creating ring sensors! How do I prevent certain ring sensors that I opened previously from starting on every launch? Thanks in advance! :)