eFMer - BoincTasks and TThrottle forum

BoincTasks For Window, Mac & Linux => Beta Testing => Topic started by: Pepo on October 29, 2010, 01:08:55 PM

Title: BT 0.84
Post by: Pepo on October 29, 2010, 01:08:55 PM
If the BT Temperature Graphics' CPU%+GPU% checkboxes and time selector would be placed above the CPU cores' and GPUs' checkboxes, then it would be possible to resize the window at the user's will to make it much thinner vertically. Now the mentioned controls get obscured and on a machine with just a few cores, there remains a lot of unused visible place above them.
And owners of a lot of cores would possibly anyway need to keep the window high to see them all...
Title: Re: BT 0.84
Post by: fred on October 29, 2010, 01:18:44 PM
Quote from: Pepo on October 29, 2010, 01:08:55 PM
If the BT Temperature Graphics' CPU%+GPU% checkboxes and time selector would be placed above the CPU cores' and GPUs' checkboxes, then it would be possible to resize the window at the user's will to make it much thinner vertically. Now the mentioned controls get obscured and on a machine with just a few cores, there remains a lot of unused visible place above them.
And owners of a lot of cores would possibly anyway need to keep the window high to see them all...
That would be an option. I didn't do that, because of the time box that moves down over the check boxes.
But why would you want a graph that small.
Title: Re: BT 0.84
Post by: Pepo on October 29, 2010, 01:26:44 PM
Quote from: fred on October 29, 2010, 01:18:44 PM
Quote from: Pepo on October 29, 2010, 01:08:55 PM
[...] it would be possible to resize the window at the user's will to make it much thinner vertically.
But why would you want a graph that small.
Sometimes I keep the TTh's graph open at the bottom of my secondary monitor for days long.
Just a wide thin stripe 1+10+2 degrees high. Observing and monitoring apps' influence on CPU temperature.
And seeing the influence of opened window to the fresh cold air ;D
Title: Re: BT 0.84
Post by: fred on October 29, 2010, 01:45:09 PM
Quote from: Pepo on October 29, 2010, 01:26:44 PM
Sometimes I keep the TTh's graph open at the bottom of my secondary monitor for days long.
Just a wide thin stripe 1+10+2 degrees high. Observing and monitoring apps' influence on CPU temperature.
And seeing the influence of opened window to the fresh cold air ;D
I could make the graph to maximize by e.g. double clicking, so you only get the graph.
Title: Re: BT 0.84
Post by: Pepo on October 29, 2010, 02:08:18 PM
Quote from: fred on October 29, 2010, 01:45:09 PM
I could make the graph to maximize by e.g. double clicking, so you only get the graph.
Nice idea, worth trying.
Title: Re: BT 0.84
Post by: Beyond on October 29, 2010, 03:12:31 PM
Hopefully this graph data won't add much overhead?  ???
Title: Re: BT 0.84
Post by: fred on October 29, 2010, 03:51:11 PM
Quote from: Beyond on October 29, 2010, 03:12:31 PM
Hopefully this graph data won't add much overhead?  ???
It doesn't on both sides.
It becomes active when the dialog is visible. At that moment there is a lot of activity, until the data is read. After that only a few bytes are read every second.
But only as long an the dialog is visible.
Title: Re: BT 0.84
Post by: Beyond on October 29, 2010, 08:06:25 PM
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 :)
Title: Re: BT 0.84
Post by: fred on October 30, 2010, 09:22:48 AM
Quote from: Beyond on October 29, 2010, 08:06:25 PM
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 :)

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>
Title: Re: BT 0.84
Post by: Corsair on October 31, 2010, 04:09:18 PM
x64 (win 7 & XP) and proper version of BT and TT installed, all machines of x64 I could shown perfectly the temperature graph, with the thing that when you point to one computer it starts from the beginning running to the actual hour to show correctly ??

in the x32 version of BT and TT same use as above, perfectly.

in both version I could not see or is not properly displayed the machine of x32.

I run one machine with XP x64 with BT (& TT), two win 7 x64 and one XP x32.

and this last I run the version of BT x32 and controlling the other computers (1 XP x64, 2 7x64)
Title: Re: BT 0.84
Post by: Beyond on November 01, 2010, 05:21:09 PM
Quote from: fred on October 30, 2010, 09:22:48 AM

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?
Title: Re: BT 0.84
Post by: Beyond on November 01, 2010, 05:24:38 PM
In BoincTasks Settings/Tasks when "Use user friendly name" is checked the full name is displayed.  Shouldn't it be the other way around?
Title: Re: BT 0.84
Post by: fred on November 01, 2010, 05:37:45 PM
Quote from: Beyond on November 01, 2010, 05:21:09 PM
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?
By setting an extremely long time?
like 2147483647
Title: Re: BT 0.84
Post by: Beyond on November 01, 2010, 05:59:08 PM
Quote from: fred on November 01, 2010, 05:37:45 PM
Quote from: Beyond on November 01, 2010, 05:21:09 PM
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...
Title: Re: BT 0.84
Post by: Beyond on November 01, 2010, 06:06:22 PM
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.
Title: Re: BT 0.84
Post by: fred on November 02, 2010, 06:58:48 AM
Quote from: Beyond on November 01, 2010, 06:06:22 PM
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)
Title: Re: BT 0.84
Post by: Beyond on November 02, 2010, 01:36:57 PM
Quote from: fred on November 02, 2010, 06:58:48 AM
Quote from: Beyond on November 01, 2010, 06:06:22 PM
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?
Title: Re: BT 0.84
Post by: fred on November 02, 2010, 01:43:10 PM
Quote from: Beyond on November 02, 2010, 01:36:57 PM
You mean it's not supposed to conform to our time format HHH:MM:SS choice in BoincTasks Settings/View?
Noted as a bug. ;D
Title: Re: BT 0.84
Post by: John McLeod VII on November 03, 2010, 11:09:28 AM
I have been having trouble with 2 major problems recently.

1)  BT 0.84 and a few previous versions occasionally post an Öut of Memory" warning.  Several of these are posted and the program then crashes.
2)  Random crashes.

I am willing to try to help debug the problem.
Title: Re: BT 0.84
Post by: Pepo on November 03, 2010, 12:41:23 PM
Quote from: John McLeod VII on November 03, 2010, 11:09:28 AM
1)  BT 0.84 and a few previous versions occasionally post an "Out of Memory" warning.  Several of these are posted and the program then crashes.

I am willing to try to help debug the problem.
Have yo maybe noticed the real/maximum memory requirements of the process at the moment? (Task Manager or Process Explorer or the like?) Whether it really tried to allocate that much...
Title: Re: BT 0.84
Post by: Corsair on November 03, 2010, 02:23:19 PM
Quote from: John McLeod VII on November 03, 2010, 11:09:28 AM
I have been having trouble with 2 major problems recently.

1)  BT 0.84 and a few previous versions occasionally post an Öut of Memory" warning.  Several of these are posted and the program then crashes.
2)  Random crashes.

I am willing to try to help debug the problem.

same has happened to me since some versions ago, mainly in x32 version,
but seen twice or three times in x64 too.

about temperature graphic in x32 version, same updated TT to version 3.0
(all computers x32 & x64), vertical scale and temperature graph not available
for the x32 machine.
Title: Re: BT 0.84
Post by: fred on November 03, 2010, 04:47:55 PM
Quote from: John McLeod VII on November 03, 2010, 11:09:28 AM
I have been having trouble with 2 major problems recently.

1)  BT 0.84 and a few previous versions occasionally post an Öut of Memory" warning.  Several of these are posted and the program then crashes.
2)  Random crashes.

I am willing to try to help debug the problem.
Memory handling is done by the OS, when there is not enough memory, the program will halt/crash.
What is:
OS type,  32/64bit , memory, BOINC version.
I'm implementing some changes in V 0.85 to address some suspected issues.
But this may leave 0.85, more alpha than beta. As I already made hundreds of small changes from one type to another. Any small mistake I make, may result in a crash.... ;D
Title: Re: BT 0.84
Post by: fred on November 03, 2010, 04:51:50 PM
Quote from: Corsair on November 03, 2010, 02:23:19 PM
about temperature graphic in x32 version, same updated TT to version 3.0
(all computers x32 & x64), vertical scale and temperature graph not available
for the x32 machine.
It's a BT problem, I think, it may be resolved in V 0.85. If not.... an extra debugging flag should give me some more info, about what's going on.
Title: Re: BT 0.84
Post by: glennaxl on November 04, 2010, 04:38:05 AM
Waiting to run tasks is showing cpu %. Shouldn't this be null (-), as its not running?

Also if you suspend this waiting to run task, its still showing cpu %.
Title: Re: BT 0.84
Post by: fred on November 04, 2010, 07:20:30 AM
Quote from: glennaxl on November 04, 2010, 04:38:05 AM
Waiting to run tasks is showing cpu %. Shouldn't this be null (-), as its not running?

Also if you suspend this waiting to run task, its still showing cpu %.
It will go to the average cpu% known. When I change that to 0, you get no info at all, about how a the CPU % was.
Title: Re: BT 0.84
Post by: glennaxl on November 04, 2010, 07:28:37 AM
Quote from: fred on November 04, 2010, 07:20:30 AM
Quote from: glennaxl on November 04, 2010, 04:38:05 AM
Waiting to run tasks is showing cpu %. Shouldn't this be null (-), as its not running?

Also if you suspend this waiting to run task, its still showing cpu %.
It will go to the average cpu% known. When I change that to 0, you get no info at all, about how a the CPU % was.
How about hiding it by a simple color change  ;) maching the background.
Title: Re: BT 0.84
Post by: glennaxl on November 04, 2010, 08:45:18 AM
another one:

when a tasks is suspended and you abort it, status still says suspended.
Title: Re: BT 0.84
Post by: Pepo on November 04, 2010, 09:59:33 AM
Quote from: glennaxl on November 04, 2010, 07:28:37 AM
Quote from: fred on November 04, 2010, 07:20:30 AM
Quote from: glennaxl on November 04, 2010, 04:38:05 AM
Waiting to run tasks is showing cpu %. Shouldn't this be null (-), as its not running?
Also if you suspend this waiting to run task, its still showing cpu %.
It will go to the average cpu% known. When I change that to 0, you get no info at all, about how a the CPU % was.
How about hiding it by a simple color change  ;) maching the background.
I vote for keeping the average% visible - the task's Status and optional whole row highlighting is about whether it runs.
Title: Re: BT 0.84
Post by: fred on November 04, 2010, 04:21:59 PM
Quote from: glennaxl on November 04, 2010, 08:45:18 AM
when a tasks is suspended and you abort it, status still says suspended.
Interesting, on the bug list.
Title: Re: BT 0.84
Post by: Beyond on November 04, 2010, 04:42:39 PM
Quote from: fred on November 04, 2010, 04:21:59 PM
Quote from: glennaxl on November 04, 2010, 08:45:18 AM
when a tasks is suspended and you abort it, status still says suspended.
Interesting, on the bug list.
Just tried this on 0.84 and it aborts properly for me.  Doesn't always show the aborted WU in History however.
Title: Re: BT 0.84
Post by: fred on November 04, 2010, 04:52:41 PM
Just tried this on 0.84 and it aborts properly for me.  Doesn't always show the aborted WU in History however.
[/quote]
It may just as well be a BOINC bug. If it's reproducible I will give it a try.
When a WU is gone within the scanning period it may not be noticed.
Title: Re: BT 0.84
Post by: Pepo on November 04, 2010, 09:37:01 PM
Quote from: Beyond on November 04, 2010, 04:42:39 PM
Quote from: fred on November 04, 2010, 04:21:59 PM
Quote from: glennaxl on November 04, 2010, 08:45:18 AM
when a tasks is suspended and you abort it, status still says suspended.
Interesting, on the bug list.
Just tried this on 0.84 and it aborts properly for me.  Doesn't always show the aborted WU in History however.
Possibly if the task was not running yet?
Title: Re: BT 0.84
Post by: glennaxl on November 06, 2010, 10:59:48 PM
Quote from: Pepo on November 04, 2010, 09:37:01 PM
Quote from: Beyond on November 04, 2010, 04:42:39 PM
Quote from: fred on November 04, 2010, 04:21:59 PM
Quote from: glennaxl on November 04, 2010, 08:45:18 AM
when a tasks is suspended and you abort it, status still says suspended.
Interesting, on the bug list.
Just tried this on 0.84 and it aborts properly for me.  Doesn't always show the aborted WU in History however.
Possibly if the task was not running yet?
The problem is not with the abort but rather with the status that BT is showing.

In recent BT versions, History doesn't update in real time. Give it a minute, for sure it will show up there.
Title: Re: BT 0.84
Post by: glennaxl on November 06, 2010, 11:01:00 PM
Computer name sorting is incorrect.

If you have numbers in name, "10" is sorted as after "1".

eg
(computers tab):
1-pc
10-pc
2-pc
3-pc
4-pc

(sidebar computer selection):
10-pc
1-pc
2-pc
3-pc


Can it be sorted like "10" is after "9" and so on?
Title: Re: BT 0.84
Post by: John McLeod VII on November 06, 2010, 11:51:47 PM
Quote from: glennaxl on November 06, 2010, 11:01:00 PM
Computer name sorting is incorrect.

If you have numbers in name, "10" is sorted as after "1".

eg
(computers tab):
1-pc
10-pc
2-pc
3-pc
4-pc

(sidebar computer selection):
10-pc
1-pc
2-pc
3-pc


Can it be sorted like "10" is after "9" and so on?
The sort should be a string sort.  Attempting to find the numbers and sort on that is going to be problematic.

If you want it to sort correctly, try naming the computers:

01-pc
02-pc
...
10-pc
Title: Re: BT 0.84
Post by: JStateson on November 07, 2010, 01:23:03 PM
What is the purpose of the Task "Count" in the Projects Tab?

For example, Milkyway is listed in three places under the "Tasks Tab" as ..
Ready to report: 0.05c + 1ATI ..and..
Running: 0.05c + 1ATI ..and..
20[Tasks]: Ready to start

however, under the "Projects Tab" I see only
Tasks:  0/21

It should be 0/22 or better yet:  1/21
or even better to show all 4 possible states
(done/waiting/running/ready) : 1/0/1/20

The tasks counts are either  0/n or they are n/0 (or 0/0)  ie: the zero is either before or after the non-zero number and a tool tip for the Tasks column header to explain the difference would be nice.

Thanks for looking!


Title: Re: BT 0.84
Post by: fred on November 07, 2010, 04:15:48 PM
Quote from: BeemerBiker on November 07, 2010, 01:23:03 PM
What is the purpose of the Task "Count" in the Projects Tab?
It's identical to the data in the computer gadget. The count is the work to do.
But it can take up to 2 minutes for the data to be entirely accurate.
It's intended for large amounts of WU's, to get an impression, of how much work there is on a computer.
In your case it should read 1/20.
It takes a lot of resources especially on computers in the 1000+ range to get a read time reading. It will slow down things noticeable.