Messages

Sure, I understand, it would be a lot to do it all at once.
Just an idea.

Similar to the Tasks and Projects, the Computers window could also have a context menu for the (selected) computers (and/or a toolbar) with various useful commands, like:

• snooze/suspend/resume/basedonprefs CPU activity
• snooze/suspend/resume/basedonprefs GPU activity
• suspend/resume networking
• reset STD debts
• reset LTD debts
• reset GPU debts
• shut down client
• run benchmarks
• read config file
• read local prefs file
• etc.

Currently the Computers window is just a list of computers the user can connect to (and open "their" window). Maybe, for clarification and fast overview, one more column could state, whether there is an active communication ongoing with any particular computer? (Note that there are/were folks with manymany dozens of computers, controlled by BoincView.)

Another possibility, which would IMHO better fit into current concept: I think that currently you can open a new "Combined [...][....]" window for any group of computers. Each window has then its own set of (one to n) computers and you can display their Projects, Tasks, Messages, etc. Let's add a Computers button into the Selection bar and Computers entry in the Show menu. When pressed, such window would list computers maintained by this window (and which of them are (or were recently) online) and their lines could support context menus with mentioned commands. I guess that the Operation toolbar could also get 1-2 most important options added...

A related bug:

• It is not possible to add computers to / remove from a selection using <Ctrl>+<mouseclick>.
  The <Shift>+<click>, <Shift>+<Up/Down cursor keys> and <Ctrl>+<Up/Down cursor keys>+<Space> selections work correctly.

You give me interesting problems , I added that one to the list.

My speciality is making problems

It often happens that some columns are a bit narrow and trailing parts of message / application / task / project / date / time / etc. string are "truncat..." To be able see the hidden text, it is necessary to enlarge (and then narrow back) the column.

• When hovering mouse cursor over such text, a tool tip containing the whole text could be displayed.
• Such tooltip is usally left-aligned with the original text. But if the tool tip would be displayed through the right display border (or left border for any right-to-left reading locale? OK kidding now), it's position should be shifted to the left as much as necessary to display the whole tool tip on-screen. (A good example of ignoring such situation is Boinc Manager - it has no problem to display tooltips obscured by the screen border.)

I will have to modify the gpu detection rule.
1) Will make an exception list mt, nci
2) Or will use the cpu / gpu use data. This is probably the best way to go.

Another question: Do these tasks have an empty Use column?

No, they are the only ones with non-empty Use column and display "2.00C" and "0.01C". Corresponding lines in BOINC Manager display additional trailing "(2.00 CPUs)" and "(0.01 CPUs)" texts in the Status column.

Ok I see the problem I don't catch the -1 from the GPU throttle meaning no GPU found. Probably this translates to 101. And as the GPU is not reporting a temperature there is none.
Next question: In the application column (QCN, Aqua) is there something between () the plan class for the application.

Yes there is (or are):

• "4.14 D-Wave's Adiabatic QUantum Algorithms - Multi-Threaded (mt)" - apparently combined of <user_friendly_name>D-Wave's Adiabatic QUantum Algorithms - Multi-Threaded</user_friendly_name> and <plan_class>mt</plan_class>
• "5.40 QCN Sensor (nci)" - apparently combined of <user_friendly_name>QCN Sensor</user_friendly_name> and <plan_class>nci</plan_class>

BTW, I have one more project with non-empty plan_class - BOINC multithreading test, but without any task. And a couple of projects' sched_request_***.xml files specify an empty plan_class, but neither of them shows () parentheses in the application column.

[Recieved from Server:]

Ok goto Help->Show log.
When you see a 101 %, check the "enable debug mode" for a short while until you get a line  Recieved from Server:
Give me all the text after this, so I can see what is going wrong.

I can constantly see 101%, both (non-CPU-intensive) QCN and (2 thread) Aqua.

From log: Throttle range was set to 24-100%, few seconds later I've set the maximum to 90%, a bit later to 100% (just the effective throttling started to rise from 24%).

16:05:58 ---- Recieved from Server: <TThrottle><PV 1.73><AC 1><TC 67><TG 14864664><DC 100><DG -1><CT0 65.0><CT1 67.0>
16:06:06 ---- Recieved from Server: <TThrottle><PV 1.73><AC 1><TC 67><TG 14864664><DC 100><DG -1><CT0 65.0><CT1 67.0>
16:06:13 ---- Recieved from Server: <TThrottle><PV 1.73><AC 1><TC 67><TG 14864664><DC 100><DG -1><CT0 65.0><CT1 67.0>
16:06:21 ---- Recieved from Server: <TThrottle><PV 1.73><AC 1><TC 67><TG 14864664><DC 100><DG -1><CT0 65.0><CT1 66.9>
16:06:29 ---- Recieved from Server: <TThrottle><PV 1.73><AC 1><TC 67><TG 14864664><DC 100><DG -1><CT0 65.0><CT1 67.0>
16:06:36 ---- Recieved from Server: <TThrottle><PV 1.73><AC 1><TC 67><TG 14864664><DC 100><DG -1><CT0 65.0><CT1 67.0>
16:06:44 ---- Recieved from Server: <TThrottle><PV 1.73><AC 1><TC 67><TG 14864664><DC 100><DG -1><CT0 65.0><CT1 66.9>
16:06:51 ---- Recieved from Server: <TThrottle><PV 1.73><AC 1><TC 67><TG 14864664><DC 100><DG -1><CT0 65.0><CT1 67.0>
16:06:59 ---- Recieved from Server: <TThrottle><PV 1.73><AC 1><TC 67><TG 14864664><DC 100><DG -1><CT0 65.0><CT1 67.0>
16:07:07 ---- Recieved from Server: <TThrottle><PV 1.73><AC 1><TC 67><TG 14864664><DC 100><DG -1><CT0 65.0><CT1 67.0>
16:07:14 ---- Recieved from Server: <TThrottle><PV 1.73><AC 1><TC 67><TG 14864664><DC 100><DG -1><CT0 65.0><CT1 67.0>
16:07:22 ---- Recieved from Server: <TThrottle><PV 1.73><AC 1><TC 67><TG 14864664><DC 100><DG -1><CT0 65.0><CT1 67.0>
16:07:30 ---- Recieved from Server: <TThrottle><PV 1.73><AC 1><TC 67><TG 14864664><DC 100><DG -1><CT0 65.0><CT1 67.0>
16:07:37 ---- Recieved from Server: <TThrottle><PV 1.73><AC 1><TC 67><TG 14864664><DC 100><DG -1><CT0 65.0><CT1 66.9>
16:07:45 ---- Recieved from Server: <TThrottle><PV 1.73><AC 1><TC 67><TG 14864664><DC 100><DG -1><CT0 65.0><CT1 67.0>
16:07:53 ---- Recieved from Server: <TThrottle><PV 1.73><AC 1><TC 67><TG 14864664><DC 100><DG -1><CT0 65.0><CT1 67.0>
16:08:00 ---- Recieved from Server: <TThrottle><PV 1.73><AC 1><TC 67><TG 14864664><DC 100><DG -1><CT0 65.0><CT1 67.0>
16:08:08 ---- Recieved from Server: <TThrottle><PV 1.73><AC 1><TC 67><TG 14864664><DC 100><DG -1><CT0 65.0><CT1 67.0>
16:08:15 ---- Recieved from Server: <TThrottle><PV 1.73><AC 1><TC 66><TG 14864664><DC 90><DG -1><CT0 65.0><CT1 66.9>
16:08:23 ---- Recieved from Server: <TThrottle><PV 1.73><AC 1><TC 67><TG 14864664><DC 90><DG -1><CT0 64.9><CT1 66.6>
16:08:31 ---- Recieved from Server: <TThrottle><PV 1.73><AC 1><TC 67><TG 14864664><DC 90><DG -1><CT0 64.8><CT1 66.7>
16:08:38 ---- Recieved from Server: <TThrottle><PV 1.73><AC 1><TC 67><TG 14864664><DC 90><DG -1><CT0 64.6><CT1 66.7>
16:08:46 ---- Recieved from Server: <TThrottle><PV 1.73><AC 1><TC 67><TG 14864664><DC 90><DG -1><CT0 64.6><CT1 66.7>
16:08:54 ---- Recieved from Server: <TThrottle><PV 1.73><AC 1><TC 66><TG 14864664><DC 90><DG -1><CT0 64.1><CT1 66.6>
16:09:01 ---- Recieved from Server: <TThrottle><PV 1.73><AC 1><TC 66><TG 14864664><DC 90><DG -1><CT0 63.8><CT1 66.5>
16:09:09 ---- Recieved from Server: <TThrottle><PV 1.73><AC 1><TC 66><TG 14864664><DC 90><DG -1><CT0 64.2><CT1 66.4>
16:09:17 ---- Recieved from Server: <TThrottle><PV 1.73><AC 1><TC 67><TG 14864664><DC 90><DG -1><CT0 63.6><CT1 66.3>
16:09:24 ---- Recieved from Server: <TThrottle><PV 1.73><AC 1><TC 67><TG 14864664><DC 90><DG -1><CT0 63.7><CT1 66.1>
16:09:32 ---- Recieved from Server: <TThrottle><PV 1.73><AC 1><TC 67><TG 14864664><DC 90><DG -1><CT0 63.8><CT1 66.0>
16:09:39 ---- Recieved from Server: <TThrottle><PV 1.73><AC 1><TC 66><TG 14864664><DC 90><DG -1><CT0 63.3><CT1 65.9>
16:09:47 ---- Recieved from Server: <TThrottle><PV 1.73><AC 1><TC 67><TG 14864664><DC 95><DG -1><CT0 64.1><CT1 66.3>
16:09:55 ---- Recieved from Server: <TThrottle><PV 1.73><AC 1><TC 66><TG 14864664><DC 95><DG -1><CT0 64.2><CT1 66.2>
16:10:02 ---- Recieved from Server: <TThrottle><PV 1.73><AC 1><TC 66><TG 14864664><DC 24><DG -1><CT0 64.4><CT1 66.4>
16:10:10 ---- Recieved from Server: <TThrottle><PV 1.73><AC 1><TC 62><TG 14864664><DC 54><DG -1><CT0 61.3><CT1 62.3>
16:10:18 ---- Recieved from Server: <TThrottle><PV 1.73><AC 1><TC 62><TG 14864664><DC 84><DG -1><CT0 61.8><CT1 64.0>
16:10:25 ---- Recieved from Server: <TThrottle><PV 1.73><AC 1><TC 66><TG 14864664><DC 100><DG -1><CT0 62.7><CT1 65.7>
16:10:33 ---- Recieved from Server: <TThrottle><PV 1.73><AC 1><TC 66><TG 14864664><DC 100><DG -1><CT0 63.0><CT1 66.0>
16:10:41 ---- Recieved from Server: <TThrottle><PV 1.73><AC 1><TC 66><TG 14864664><DC 100><DG -1><CT0 63.0><CT1 66.0>
16:10:48 ---- Recieved from Server: <TThrottle><PV 1.73><AC 1><TC 66><TG 14864664><DC 100><DG -1><CT0 63.3><CT1 66.0>
16:10:56 ---- Recieved from Server: <TThrottle><PV 1.73><AC 1><TC 66><TG 14864664><DC 100><DG -1><CT0 64.6><CT1 66.2>
16:11:03 ---- Recieved from Server: <TThrottle><PV 1.73><AC 1><TC 67><TG 14864664><DC 100><DG -1><CT0 63.8><CT1 66.4>
16:11:11 ---- Recieved from Server: <TThrottle><PV 1.73><AC 1><TC 66><TG 14864664><DC 100><DG -1><CT0 64.7><CT1 66.2>

One more possibly importand thing: Neither QCN nor Aqua task lines show the temperature, just 101% throttling. If I suspend Aqua, then e.g. two SETIs are running, no throttling and with temperature (68 degrees) displayed. Additionally there is my QCN with 101% and still no temperature.

And just the combined window is showing the values from TThrottle, a single computer window has both Throttle and Temperature columns empty. (I've missed whether this is by design.)

• Second, the application is continuously communicating with USB sensor and is consuming its fraction of CPU.
• Third, my QCN application is excluded from being throttled. another reason for the throttling state to be displayed as 0%. (BTW, currently my CPU temp is that low, that no apps are throttled. Just the (excluded) QCN...)

[...] I've paused one Seti to let the Aqua MT app (a "2.00 CPU" class app on my computer) go - it took over both cores and - surprise - got throttled by 101%.

2) USB  sensor? Not TThrottle.
3) Goto the BOINC tab and check if the QCN project is there. Check "Show All" and see if the QCN exe is in the list.

2) Well, off course the QCN app is accessing the USB device, not TThrottle I just wanted to show that it is actively doing somenthing and consuming some more than -1% of CPU cycles
3) In the BOINC tab, both Aqua and QCN projects are listed. With "Show All", all QCN-related apps are displayed prefixed with (at least one) '$' sign. Aquas are not prefixed.
   On the Programs tab, Aqua is listed among other apps, QCN is not there.

After removing QCN from the list of excluded apps, it appeared in the Programs list. But BoincTasks still shows the same 101%.



I'd like to ask some volunteer running any GPU application (which are usually not a 1.00 CPU apps) to check how much are they being throttled (according to the BT's Throttle column).

Again my non-CPU-intensive QCN. BT is showing it being throttled by 101%, which is a double or triple nonsense

• First, nothing can be throttled by more than 100% (except the CPU would unwind previously executed code instructions).
• Second, the application is continuously communicating with USB sensor and is consuming its fraction of CPU.
• Third, my QCN application is excluded from being throttled. another reason for the throttling state to be displayed as 0%. (BTW, currently my CPU temp is that low, that no apps are throttled. Just the (excluded) QCN...)

The application is marked as an "0.01 CPU" class app, maybe the wrong throttle status is displayed because of this?

As an excercise, I've set the throttling range to 24-90% - suddenly the two running SETIs are throttled by (expected) 10%. QCN stays at (incorrect) 101%. Then I've paused one Seti to let the Aqua MT app (a "2.00 CPU" class app on my computer) go - it took over both cores and - surprise - got throttled by 101%.

So there is apparently some bug with displaying 101% throttling for any application, which does not belong to the usual 1.00 CPU class.

The beginning of the throttling line seems to be started stright up from somewhere around 45% to 100% during maybe just one second (can't zoom anymore, I've noticed it after 100 minutes) - this is surely no slow de-throttling, which happens slowly, possibly some throttling variable was used to display throttling value with an initial value of 0%?
[...]
(My throttling range is set to 24-100%, which is matching the displayed area and possibly the reason for low initial throttling value was somewhere else - I'll try to remember to keep my eye on in the next time I'll reboot (usually once in a couple of weeks )).

As far as I can check TThrottle always starts with the minimum value, 24% in this case and works it way up.
When you scale to a longer period the values are middled out so it may be that some peaks are not shown but are actually there.

Well, you are right, I should've tried this too - just to start TThrottle once again. It behaves (zoomed to 1-5 minutes) just as you write - slowly, deterministically rising from the lower to the upper limit - a secure behaviour, and (zoomed to 12 hours) looks just as I've described it 

OK, I'm taking my complaint back - It happens correctly, per purpose and is displaying the truth!

I've restarted my system, not touching TTh settings. Prior to the reboot, the CPU temperature (dual-core) was by some 5-7 degree lower than the throttling threshold. After the reboot, the beginning of the graph shows cores' temperatures rising from -12 to -7 degrees below the limit. So I'd assume there should be no reason for throttling.

The beginning of the throttling line seems to be started stright up from somewhere around 45% to 100% during maybe just one second (can't zoom anymore, I've noticed it after 100 minutes) - this is surely no slow de-throttling, which happens slowly, possibly some throttling variable was used to display throttling value with an initial value of 0%?

Although being just an optical glitch, the graphs (especially 12h+24h ones, for a long time) are unnecessarily scaled to show 19-102 area, while a better zoomed 59-102 would be displayed instead

(My throttling range is set to 24-100%, which is matching the displayed area and possibly the reason for low initial throttling value was somewhere else - I'll try to remember to keep my eye on in the next time I'll reboot (usually once in a couple of weeks )).

One more wish:

• To all time selector popup menus, add some value into the large gap between 1 and 12 hours - maybe 3 or 4 hours.

In the history, what does the "Reported: Ok (u)" mean?

malariacontrol.net   6.24 malariacontrol.net   wu_65_30_251913_0_1259177407   08:55:50 (04:51:09)   26.11.2009 5:51:26   26.11.2009 5:51:38   Reported: Ok (u)

I'm running a non-CPU-intensive QCN. BT is showing it being throttled by 101%. A bit off 100% should be enough, it even consumed some 36 seconds over the last 3 days - approx. 0.01%, so the throttling should not exceed 99.993...% 
OK, I've excluded the QCN apps from throttling, so ti should be a round 100% or 0%. Left to be explained.

I'll check it a few hours ago after connecting it to the quake sensor, it should be then consuming a few CPU%.

I've not managed to let my BT 0.30 show any temperature or throttle states in their columns. How to set the communication up? In TThrottle, BT checkbox is enabled.

http://www.efmer.eu/boinc/boinc_tasks/manual.html Check the chapter TThrottle and let me know if it enough to get things working.

I've somehow overlooked the "Extra->Settings -> general tab -> Connect to TThrottle" checkbox.
Thanks.

I've not managed to let my BT 0.30 show any temperature or throttle states in their columns. How to set the communication up? In TThrottle, BT checkbox is enabled.