Messages

Hi all,

marvellous,

"Extra" ---> "Auto start-up with" not translated.

"CPU% long time average" a little explanation, in English, about, on that way I could translate correctly.

What's in a sentence, I had some problems with the wording myself.
CPU % in that mode (checked) takes the time over the entire period from start to finish. So the CPU % is measured over an ever increasing time period.
So it's the average over a long period of time.
The other (not checked) mode uses a shorter time period of about 10 refresh cycles back.

The extra menu text that is not translated is on the bug list.

Worked immediately.

Could the checkbox please apply also to the Gadget miniWindow? It is showing the long-time average regardless of the "CPU % Long-time average" settings.

Oeps forgot that one, next release.

Occasionally Boinc WU tasks get "stuck" and make no progress for several hours.
Could BoincTasks "Warnings" be adapted to flag a task that makes no progress for a specified period in minutes?
The CPU% column still shows 100% for these even though they are actually consuming 0% CPU according to Windows Task manager.

Give V 0.40 a try. Extra -> BoincTasks settings: Tab Tasks: Remove the check before "CPU % Long", this should resolve the 100% problem.

V 0.40

-(ADD) A snooze function from the taskbar menu.
-(ADD) Suspend/resume network communication.
-(ADD) In the BoincTasks settings dialog -> general tab: A hot key to show and hide BoincTasks.
-(ADD) A new option for the CPU %, a fast mode that also supports older clients, always showing 100%. This mode will respond faster to changes and warnings should appear quicker.
-(CHANGED) The gadget window now doesn't show any tasks on a computer that is snoozing (suspended by user).
-(CHANGED) The view immediately updates when restored from minimized or iconic (hidden) state.
-(CHANGED) When multiple tasks of the same project/computer are selected, execute project operations like refresh/resume/pause only once.
-(CHANGED) The minimum height for the Gadget Window is now reduced to 1 line.
-(FIXED) When updated from a version before 0.39 an incorrect selected language was shown in the logging (but not actually selected).
-(FIXED) The menu Help->Update is grayed out in all views except the Tasks view.
-(FIXED) a state of 20001 now shows as Ready to start.

Hi Fred, it's done.

Final: BoincTasks_DEU.btlang_v0.39_v0.3.

Diff to original: BoincTasks_v0.39_german.lang_v0.3_to_original.html.

Thanks also to aendgraend and Saenger.

Nice work, as I'm ready for 0.40 as well, the next version will follow soon.
0.40 will have a lot less new text, so it should be quite easy.

The CPU % column displays the percentage between the wall clock and the time the project task runs.
100% = the task runs 100% of the time.

CPU

Cpu tasks mostly run close to 100% of the time. But the computer does other things besides BOINC and the value will likely be less than 100%.
And of course using the build in throttle, or better TThrottle, will can cause the percentage to be a lot less.

GPU

Gpu tasks mostly run a lot less than 100% as the Gpu is doing additional work.

Check: "CPU % Long time average"

When this check is enabled BoincTasks will take the whole time period, from the start, to measure the CPU %.
Disabling this check, BoincTasks will take a shorter interval to measure the CPU %. This will better recognize stuck tasks, when the warning is enabled.

Always 100%

BoincTasks versions before 0.40 sometimes only gave 100%, mostly on older BOINC clients.
Go to Extra -> Settings BoincTasks, tab Tasks: Remove the check before "CPU % Long time average".
This will measure the CPU % over a shorter period of time and will enable the automatic 100% detection mode. The last will detect 100% and use a different method to obtain the CPU %.

Hello to all;

I'm definately a newb since it's been soooo long ago I helped in the seti project prior to BT so be kind hehe.   

I noticed there was a post a while back about the "Transfer Tab" being on the wishlist. Since mine not showing any data I surmise it to still be a wishlist item?  And if so is there a tentative date for the version release containing this? 


Thanks for your time. 

The transfer tab is mostly empty when there are no transfers.

I've missed its run, it is already Ready to report after just 25:41 minutes, deadline in 7 days I'd not expect HP here, but, well, I'm not BOINC

Unluckily I've not copied the task's line (pease please add to wish list: "Copy selected/all lines from Tasks or Projects window into clipboard") with estimated Remaining time and do not want to calculate them manually from my client_state.xml 

High priority mode is not for us to understand, but new, downloading , ready to start, waiting to run and running can have the HP state.
I add the copy to the wish list.

BT now use values from the BOINC client, but only the "newer" clients do report the cpu run time, so you get something else than 100%
And this way the CPU % can take a looong time to respond to changes.
What I can do is Delta = runtime Now - Runtime Previous. Delta = 57:51 - 58:35 = 44 Sec. Wall clock = 60 Sec,  CPU % = 44/60 = 73%
Do it every refresh cycle, instead of over a minute and middle it a bit over time, to smooth things out.
This way there should be a more immediate response and it works with older clients as well.   

I connect to the World Community Grid Project - accepting all their WU's.
I have several machines running BOINC 6.2.28 or 5.10.45 on Windows XP or 2008 R2, also occasionally on Ubuntu.
This "stuck" condition is fixed by stoppng and re-starting the remote client. It has happened on FAAH and HFCC once or twice in the past month and from reading WCG posts it is not exactly common but is also not unheard of. The WU's eventually error-out if they are not noticed, but it can take many hours.
I am trying to migrate from Boincview to BoincTasks but find that BoincTasks does not tell me when all CPU's are busy doing BOINC work
When an application (WU) is in this state Boincview shows 0.000 in CPU Efficiency - BoincTasks still shows CPU% as 100% for that WU.  (I realize from other posts that I may not understand what CPU% is intended to report - I don't have any GPU's)
I think if BT could report actual CPU% being used I could trigger a warning (which is what I do in BoincView) when it is below a threshhold.

The problem is with the older clients that will always show 100%, the newer BOINC client versions will report a percentage.
It is not necessarily a GPU thing. It's the difference between the clock time and the task run time. It should work with the latest stable BOINC release.
But I added this request to the Wish list.

A related function is added in the Extra menu, Suspend network communications, available for all computers. It will suspend indefinably.

Suspend+Resume. For "all" computers in the combined window at once, or for any of the computers, or the computer with topmost single-client window?

Added to the list

0.40 is ready for release, I will wait until Monday for release 25-1.

The CPU% column still shows 100% for these even though they are actually consuming 0% CPU according to Windows Task manager.

I remember having seen cases, when

• regular CPU-intensive application is not consuming any CPU in the running state (this is not the case of non-CPU-intensive apps like e.g. 0.01 CPUs QCN or DepSpid, they do progress regardless of the CPU used), do not progress %-wise and never reach a checkpoint (to be automatically preempted), this case is already catched by the existing builtin CPU warning.
  The usual solution is to notice the case temporarily suspend ot kill such application or restart the client,
• regular CPU-intensive application is consuming the usual nearly full CPU in the running state, but progress the % rarely or even just when finished, it could be that such application does neither chechkpoint, nor progress the % during a many hours long run. The only solution is to wait and pray to not loose electricity.
  I have no idea what would BT display in such case.

Added it to the wish list

My unstarted PrimeGrid Sophie Germail Prime Search (LLR) 5.1 task LLR_SGS_42720474_1 is currently in "20001-state:" (according to BT), BoincManager shows just Ready to start.

What does it mean?

IIRC I've already seen such uncommon state in the past.

Means Ready to start high priority. Will probably go into HP mode when running.
Fixed in V 0.40

Occasionally Boinc WU tasks get "stuck" and make no progress for several hours.
Could BoincTasks "Warnings" be adapted to flag a task that makes no progress for a specified period in minutes?
The CPU% column still shows 100% for these even though they are actually consuming 0% CPU according to Windows Task manager.

What BOINC version are you using?
The project?