Messages

[01d,01:40:42 (03d,19:03:24)]

History tab view does not honor the chosen time format, "Elapsed Time" still shows some times like : 
AQUA@home    1.14 IQUANA (mt1)    iq64A2_281006a_2_164_0    01d,01:40:42 (03d,19:03:24)    10-31-10  02:36    10-31-10  02:38    4.00C    Reported: OK (u)

Feature request:  Configurable column placement in the History tab.

This is not a time format:  01d,01:40:42 (03d,19:03:24)

You mean it's not supposed to conform to our time format HHH:MM:SS choice in BoincTasks Settings/View?

[01d,01:40:42 (03d,19:03:24)]

History tab view does not honor the chosen time format, "Elapsed Time" still shows some times like : 
AQUA@home    1.14 IQUANA (mt1)    iq64A2_281006a_2_164_0    01d,01:40:42 (03d,19:03:24)    10-31-10  02:36    10-31-10  02:38    4.00C    Reported: OK (u)

Feature request:  Configurable column placement in the History tab.

After a bit of fiddling I set up a nice set of global warnings.  When I set up a longer warning only for a particular project it still includes the global warnings.  Is there a way to exclude a project from the global checkpoint warnings?

By setting an extremely long time?
like 2147483647

Tried that but all that happens is that the global settings are still enforced plus the longer time warning is added for that project.  I've tried adding the project, adding the application name, adding both: still acts the same.  Maybe I'm doing something wrong...

In BoincTasks Settings/Tasks when "Use user friendly name" is checked the full name is displayed.  Shouldn't it be the other way around?

1) Noted, a specific project of any.
2) The checkpoint warning can be adjusted, to about anyway you can think off.
Place it in a file called config.xml and place it next to the BT exe
You can set the warning to a specific project or a specific application.

<config>
   <checkpoint>
      <project>world%20community%20grid</project>
      <application></application>
      <seconds>3600</seconds>
      <red>255</red>
      <green>0</green>
      <blue>0</blue>
   </checkpoint>
   <checkpoint>
      <project></project>
      <application></application>
      <seconds>0</seconds>
      <red>o</red>
      <green>255</green>
      <blue>0</blue>
   </checkpoint>
</config>

Thanks Fred, guess I should have checked the FAQs

After a bit of fiddling I set up a nice set of global warnings.  When I set up a longer warning only for a particular project it still includes the global warnings.  Is there a way to exclude a project from the global checkpoint warnings?

Some checkpointing problems:

1) All single tasks that are "Waiting to run" show a deadline warning if Filter (combine) is set to on.

2) Warning time is too short (2 minutes).  About 1/2 of my tasks show a checkpoint warning at any given time.  A much longer time for the warning would be preferable (5 - 10 minutes) or better, a configurable time

Hopefully this graph data won't add much overhead? 

MW doesn't checkpoint much. I see the GPU version not checkpointing at all. Or not reporting it.

Correct, the MW app for GPU does not checkpoint.  For newer GPUs the WUs are so short it's not an issue.  Not sure about the CPU version as I wouldn't think of running it.

The GPU doesn't checkpoint but does store the results, so it resumes after a suspend.

On all my machines the GPU WUs start over from the beginning after a suspend.

MW doesn't checkpoint much. I see the GPU version not checkpointing at all. Or not reporting it.

Correct, the MW app for GPU does not checkpoint.  For newer GPUs the WUs are so short it's not an issue.  Not sure about the CPU version as I wouldn't think of running it.

Could be user defined the decimal part of:

• Progress, sometimes looks like that 2 decimals are enough
• CPU %; same as above sometimes enough with only one
• Temperature: same as above enough with one, but if somebody likes 2

from my side should be enough with user defined of Progress and CPU %.

Added to the list.
The temperature isn't possible, as it's accurate to 1 degree anyway.

My preference is for:
Progress = 3 decimal places
CPU % = 2 or less decimal places
Temp = 1 decimal place

3 decimal places in Progress is very useful for long running WUs.

• I've updated 0.81 -> 0.82 with BT's autostart afterwards. As soon as BT's tray icon appeared, I've clicked on it to open it, but BT immediately crashed.

Not a big deal but it would be nice to not have the "Launch BoincTasks" and "WWW BoincTasks" checked by default on the last installation screen every time we install it (or remember the state from the previous install).  BTW, the "Tasks" window is freezing up MUCH less since v0.81.  Of course the problem child FreeHAL has been down for much of that time...

Interesting is that this slowed state persists just as long as the BTs are connected to the particular client.

Maybe I've got it? I've just seen that the History tab's status bar constantly displays  "Updating..." without the usual 30 second countdown. I've seen something like this in the past when observing a task approaching its finish. A look into the Tasks tab: One FreeHal@home pseudo-nCi task was claiming being progressed to some couple of hundreds or thousands %...
I've aborted the task, updated project - as the task disappeared, BT was suddenly working as usual.. After downloading a new FreeHal@home task and starting it, in a while (around 141.756% seems to be enough) BT was sluggish again
Suspending the task seems to be enough to heal the sluggishness.

So, the idea was that maybe the high progress percentage triggers BT to go into "superfast history fetching" mode for a task approaching its end? The task contains sometimes no ETA, or "Estimated time remaining      -", sometimes just a few seconds...

BTW, what about displaying the weird progress percentage? BOINC Manager displays no (0.000%) Fraction done for the task, the same is true for BT's task properties window. But the Tasks tab often displays a strange value. Is it somehow computed? I suspect that the strange application generates no fraction_done, among other things it also generates no boinc_task_state.xml file in its slot...

I'm also running FreeHAL on all 9 clients and can confirm when one or more nears completion BT starts locking up far more often.  The History tab behavior you describe also happens here.  When no FreeHAL WU is within 20% of completion the BT Tasks window updates much more reliably.

<SNIP>
The location:C:\Users\username\AppData\Roaming\eFMer\BoincTasks\crash
you can mail me at fred at efmer dot com
If possible one of a recent BT copy 0.78 or 0.79.
What BOINC version are you using?

OMG!!  There are 95 dump files there!!  from 85mb thru 142mb in size.

I will zip up one each from 79 and 78 (Both are from today).   Lemme know if the zip files arrives ok.  My ISP may not let it thru.
I am running boinc 6.10.65 and 6.10.66 on 3 windows and 5 ubuntu systems.

They revealed nothing at all.
But I'm getting suspicious about the BOINC alpha versions. Maybe they changed something that causes these problems.

I'm currently using v6.11.6 and 6.11.9 but the vast majority of my 152 dump files were from v6.10.58 and before.  Could we possibly have an option for limiting or not generating these at all?  They came close to filling the partition where BT is installed.

<SNIP>
The location:C:\Users\username\AppData\Roaming\eFMer\BoincTasks\crash
you can mail me at fred at efmer dot com
If possible one of a recent BT copy 0.78 or 0.79.
What BOINC version are you using?

OMG!!  There are 95 dump files there!!  from 85mb thru 142mb in size.

I will zip up one each from 79 and 78 (Both are from today).   Lemme know if the zip files arrives ok.  My ISP may not let it thru.
I am running boinc 6.10.65 and 6.10.66 on 3 windows and 5 ubuntu systems.

Thought I'd check too.  I have 152 *.dmp files in the crash directory for a total of 14.1 GB...

I have the same thing happening (not BT version specific) except that I'm running 6 Win 7-64 and 3 Win XP-64 machines.  Two are attached by wireless lan and I'm thinking that they may have something to do with the problem.  Sometimes things run well for a while then the updating problems start again.  Often have to close BT and restart it to get the Tasks tab to update.  History updates fine and the other tabs don't seem to be as much of a problem, just Tasks.

Tasks is also the one with most of the data.
1 The wireless lan is on a static IP address?
2 When this happens is the history tab still counting down and updating and counting down again?

1) My lan was using DHCP but the wireless IPs kept jumping around causing problems with BT, so I switched everything over to static IPs.  The BT situation improved but it's still not updating the Tasks tab reliably.

2) The History tab keeps updating.  Many WUs scroll by while the Tasks tab is still trying to update.  (I run MW on 8 GPUs so there's a WU completing on the average of every 25 seconds there alone.)