Very good step to place Graphs' Computers and Projects selection side-by-side instead vertically! Saves a lot of (opposite) scrolling among projects. (Tasks Graphs might follow it.)
However, I'm still missing the meaning of "Expanded selection box".
I personally like the new "tube-skinned" stripes more than the former alternating ones - they were changing the underlying colors too much, differently for similar tasks. Now equally highlighted tasks also share the same color. (However they are possibly a bit too dark in the middle of rows.)
Tasks a day/week: the majority of my projects show 26/day + 235/33/week, others have 0 + 0/0. Mostly projects with no tasks on board show 0 + 0/0 and those with any tasks show 26 + 235/33, but it is not an absolute pattern, exceptionally CPDN beta with 1/0 tasks has 0+0/0.
GPU throttle graph in BT is again correct (BT 1.17 + TTh 4.30). (Maybe a longer time already, I've been using 4.20 until today.)
Quote from: Pepo on August 19, 2011, 12:25:45 PM
1) Very good step to place Graphs' Computers and Projects selection side-by-side instead vertically! Saves a lot of (opposite) scrolling among projects. (Tasks Graphs might follow it.)
However, I'm still missing the meaning of "Expanded selection box".
2)I personally like the new "tube-skinned" stripes more than the former alternating ones - they were changing the underlying colors too much, differently for similar tasks. Now equally highlighted tasks also share the same color. (However they are possibly a bit too dark in the middle of rows.)
3)Tasks a day/week: the majority of my projects show 26/day + 235/33/week, others have 0 + 0/0. Mostly projects with no tasks on board show 0 + 0/0 and those with any tasks show 26 + 235/33, but it is not an absolute pattern, exceptionally CPDN beta with 1/0 tasks has 0+0/0.
4) GPU throttle graph in BT is again correct (BT 1.17 + TTh 4.30). (Maybe a longer time already, I've been using 4.20 until today.)
1) The check box "Expanded" is to override the side by side. It's automatically selected, depending on the nr of computers/projects. E.g. with one computer you probably get the old one.
2) The color gradient depends on the color and is slightly different on a other monitor. (depends on the color resolution of the actual LCD, that may be less than 255 / color. The gradient is only 20 in the middle.
I switched off the alternating by default.
3) The number in day should be about the same as the second number in week.
4) The GPU throttle was fixed some time ago.
The venue is, surprise, also available in the latest BOINC release on some projects, with the later server software.
Quote from: fred on August 19, 2011, 03:10:53 PM
Quote from: Pepo on August 19, 2011, 12:25:45 PM
1) Very good step to place Graphs' Computers and Projects selection side-by-side instead vertically! [...] However, I'm still missing the meaning of "Expanded selection box".
3)Tasks a day/week: the majority of my projects show 26/day + 235/33/week, others have 0 + 0/0. Mostly projects with no tasks on board show 0 + 0/0 and those with any tasks show 26 + 235/33, but it is not an absolute pattern, exceptionally CPDN beta with 1/0 tasks has 0+0/0.
1) The check box "Expanded" is to override the side by side. It's automatically selected, depending on the nr of computers/projects. E.g. with one computer you probably get the old one.
3) The number in day should be about the same as the second number in week.
1) I have here 3 computers defined. Mostly just 1 is connected (as is also now) with currently 29 projects. "Expanded" seems to have no effect in this configuration - stil 2 boxes side-by-side.
3) It approximately is. But I do not understand at all, what do the columns try to tell me ??? That the number of tasks flowing through the majority of my projects is the same (26 daily)? And what does "235/33 a week" mean?
Quote from: Pepo on August 19, 2011, 03:24:12 PM
1) I have here 3 computers defined. Mostly just 1 is connected (as is also now) with currently 29 projects. "Expanded" seems to have no effect in this configuration - stil 2 boxes side-by-side.
3) It approximately is. But I do not understand at all, what do the columns try to tell me ??? That the number of tasks flowing through the majority of my projects is the same (26 daily)? And what does "235/33 a week" mean?
1) Needs a BT restart.
3) Day = total number of tasks you got in the the last 24 hours.
4) Week = same but in a week the second number is week/7 ;D.
All of the % bars are completely filled in no matter what percentage is used.
Projects: Share %, Tasks: Progress % and CPU %, Transfers: Progress %
Here are 2 screenshots to compare in Tasks view: one for v1.16 and one for v1.17
v1.16 (http://s135.photobucket.com/albums/q133/rahicks13/?action=view¤t=ProgressBars_v116.jpg)
v1.17 (http://s135.photobucket.com/albums/q133/rahicks13/?action=view¤t=ProgressBars_v117.jpg)
Quote from: fred on August 19, 2011, 03:27:13 PM
Quote from: Pepo on August 19, 2011, 03:24:12 PM
1) I have here 3 computers defined. Mostly just 1 is connected (as is also now) with currently 29 projects. "Expanded" seems to have no effect in this configuration - stil 2 boxes side-by-side.
3) It approximately is. But I do not understand at all, what do the columns try to tell me ??? That the number of tasks flowing through the majority of my projects is the same (26 daily)? And what does "235/33 a week" mean?
1) Needs a BT restart.
3) Day = total number of tasks you got in the the last 24 hours.
4) Week = same but in a week the second number is week/7 ;D.
1) Got it. (Still, the Tasks Graphs might follow it, it is an useful option.)
3) The Tasks Graph displays 13 single-height-spikes and 6 double-spikes for the 1 day, which sums up to 25 - maybe after moving the borders of the first and last spike interval it might match the (now already) 27/day.
It also displays 108 1-spikes + 43 2-spikes for a 7 day interval, which sums up to 194 - does not compare as nicely to 237/33.
But still, if these numbers would exactly match, why does each project display the same overall sums for the whole client? I'd rather expect the columns filled with something like 1 + 11/1.5 for Einstein, 6 + 40/5.7 for FreeHAL, 0 + 4/0.5 for MilkyWay, 1 + 7/1.0 for QCN, 2 + 10/1.4 for Rosetta, 1 + 34/4.8 for SETI, etc. (including the (optional?) one decimal number, for low-tasks-volumers like me
;)) - i.e. each project his/her own counts.
Quote from: BobCat13 on August 19, 2011, 03:42:47 PM
All of the % bars are completely filled in no matter what percentage is used.
Projects: Share %, Tasks: Progress % and CPU %, Transfers: Progress %
No idea, works correctly for me (BT 1.17 + BOINC 6.12.34) also displays all bars fully filled. (I was blind I suppose.)
Quote from: BobCat13 on August 19, 2011, 03:42:47 PM
All of the % bars are completely filled in no matter what percentage is used.
Noted, probably a typo. :o
Quote from: Pepo on August 19, 2011, 03:57:56 PM
Quote from: BobCat13 on August 19, 2011, 03:42:47 PM
All of the % bars are completely filled in no matter what percentage is used.
Projects: Share %, Tasks: Progress % and CPU %, Transfers: Progress %
No idea, works correctly for me (BT 1.17 + BOINC 6.12.34) also displays all bars fully filled. (I was blind I suppose.)
Yes I also noted that (BT 1.17 + BOINC 6.12.33) the progress /% bars are not progressive.
me too, progress bar always filled (BT 1.17 + BOINC 6.12.33 + W7x64SP1) no matter what progress is done.
as you could understand it's not easy for me to see it as have to do a remote connection to computer at home, and with the marvellous speed that I've sometimes the screen / network refresh mades me some tricks ;-)
I think as stated in some messages below, progress bar, CPU % and not checked another all then completely filled.
With newer versions of BT (at least 1.16 & 1.17) TThrottle temps don't always show in BT (TT 4.30) . They often phase in & out every few updates. The missing temps happen for the local machine only.
Quote from: Beyond on August 21, 2011, 06:16:43 PM
With newer versions of BT (at least 1.16 & 1.17) TThrottle temps don't always show in BT (TT 4.30) . They often phase in & out every few updates. The missing temps happen for the local machine only.
Can you tell me more, show me a graph from BT an TThrottle for example.
You are missing parts or is it just taken longer.
Quote from: fred on August 22, 2011, 06:49:42 AM
Quote from: Beyond on August 21, 2011, 06:16:43 PM
With newer versions of BT (at least 1.16 & 1.17) TThrottle temps don't always show in BT (TT 4.30) . They often phase in & out every few updates. The missing temps happen for the local machine only.
Can you tell me more, show me a graph from BT an TThrottle for example. You are missing parts or is it just taken longer.
The graph in TT shows correctly on the localhost. The TT temp window always shows fine on the localhost. For some reason the temp and also sometimes the TT version number (in the Computers window) is being picked up erratically by BT. This only happens for the localhost. I've had the problem that occasionally a remote machine temp will stop being reported but closing & restarting TT always solves the issue. For the localhost it's different. The temps in the BT temp column come and go. Restarting TT seems to fix it for a short time but then the temps start phasing in and out again, generally more out than in.
Edit: Also if I bring up the BT graph and the TT graph on the local machine and set them for instance at 5 minutes, they both match and show the temps properly with no gaps. While I'm doing this the localhost temps are still phasing in and out in the BT Tasks window. One machine is using BT 1.16 and the other BT 1.17. Happens the same in both.
Quote from: Beyond on August 22, 2011, 02:50:45 PM
Also if I bring up the BT graph and the TT graph on the local machine and set them for instance at 5 minutes, they both match and show the temps properly with no gaps. While I'm doing this the localhost temps are still phasing in and out in the BT Tasks window. One machine is using BT 1.16 and the other BT 1.17. Happens the same in both.
1) To get thing clear, are you missing parts of the graph, so no gaps on the localhost?
2) The thing you see is that the Tasks window show the temperature intermittently. in other words show it, shows it not , shows it.
3) What is the refresh rate of the Tasks window.
Quote from: fred on August 22, 2011, 04:57:13 PM
Quote from: Beyond on August 22, 2011, 02:50:45 PM
Also if I bring up the BT graph and the TT graph on the local machine and set them for instance at 5 minutes, they both match and show the temps properly with no gaps. While I'm doing this the localhost temps are still phasing in and out in the BT Tasks window. One machine is using BT 1.16 and the other BT 1.17. Happens the same in both.
1) To get thing clear, are you missing parts of the graph, so no gaps on the localhost?
No missing parts, no gaps.
Quote2) The thing you see is that the Tasks window show the temperature intermittently. in other words show it, shows it not , shows it.
Exactly. Show it not is more frequent than show it :)
Quote3) What is the refresh rate of the Tasks window.
Counter at bottom starts counting down at 7 seconds. Maximum update time is set to 240 seconds.
Again this intermittent reading ONLY happens for the localhost in BT. The reading on the little TT graphic strip always works.
I don't know if this a bug or not, but here goes...
On each machine, I have two different types of WU, call them TypeA and TypeB, running and filter them so that in BT I can see
TypeA [9 Tasks], double click to expand
TypeB [6 Tasks], double click to expand
If I dbl-click on TypeA, the filter is removed and I now see 9 lines of info OK SO FAR
However, if I then dbl-click on TypeB line, instead of those tasks opening up to list the WUs in for that type, TypeA then goes back to being a filtered view. (My reason for wanting to do this is that I have found BT is now very good at helping me micromanage from time to time and sometimes I might want to suspend one particular WU type in order to process another which has a shorter deadline).
i.e. dbl-clicking on a different type of WU on the same machine is being treated as if I had dbl-clicked on the same type of WU.
My question is whether you intended BT dbl-clicking action was intended to do this or if it is a bug.
Quote from: coolstream on August 23, 2011, 01:12:05 PM
i.e. dbl-clicking on a different type of WU on the same machine is being treated as if I had dbl-clicked on the same type of WU.
On one machine I have suspended several WUs of 3 different projects: Moo!, RNA and Yoyo. Double clicking on one expands all 3. Double clicking on any off the expanded WUs collapses them all, 3 projects worth.
Here's a relatively less important visual anomaly: if I put the "Toolbar graphic", "Toolbar selection" & "Selection bar" on the same line to save screen space, the button heights vary slightly which causes gaps at the bottom of some of the buttons. It would be nice if they had the same number of pixels vertically. Not a real big deal... :)
Quote from: Beyond on August 23, 2011, 01:56:33 PM
Here's a relatively less important visual anomaly: if I put the "Toolbar graphic", "Toolbar selection" & "Selection bar" on the same line to save screen space, the button heights vary slightly which causes gaps at the bottom of some of the buttons. It would be nice if they had the same number of pixels vertically. Not a real big deal... :)
I increased the height of the selector a bit, was slightly smaller.
Quote from: fred on August 23, 2011, 02:28:17 PM
I increased the height of the selector a bit, was slightly smaller.
Oh oh, that fix took almost 32 minutes ;D
Quote from: Beyond on August 23, 2011, 03:34:28 PM
Quote from: fred on August 23, 2011, 02:28:17 PM
I increased the height of the selector a bit, was slightly smaller.
Oh oh, that fix took almost 32 minutes ;D
Maybe, the problem is the height depends on a lot of things. If you set the font to 125% in Win 7, you get a higher selection bar.
It has to fit the larger font.
Selecting other fonts may cause similar problems and not to forget different OS.
So this is something, that may not be fixable.
Quote from: Beyond on August 23, 2011, 01:38:53 PM
Quote from: coolstream on August 23, 2011, 01:12:05 PM
i.e. dbl-clicking on a different type of WU on the same machine is being treated as if I had dbl-clicked on the same type of WU.
On one machine I have suspended several WUs of 3 different projects: Moo!, RNA and Yoyo. Double clicking on one expands all 3. Double clicking on any off the expanded WUs collapses them all, 3 projects worth.
I am only processing one project but in that project there are different applications being run.
I have just checked and behaviour is the same in BT 1.18
Quote from: coolstream on August 24, 2011, 12:18:53 PM
I am only processing one project but in that project there are different applications being run.
But this happens only with suspended tasks?
Quote from: fred on August 24, 2011, 12:35:22 PM
Quote from: coolstream on August 24, 2011, 12:18:53 PM
I am only processing one project but in that project there are different applications being run.
But this happens only with suspended tasks?
In my case it happens only with "suspended by user" tasks. It does NOT happen with suspended projects. Try suspending a number of tasks from different projects, then double click on one of them and watch what happens.
Quote from: Beyond on August 24, 2011, 01:07:17 PM
In my case it happens only with "suspended by user" tasks. It does NOT happen with suspended projects. Try suspending a number of tasks from different projects, then double click on one of them and watch what happens.
On the bug list.
Quote from: fred on August 24, 2011, 12:35:22 PM
Quote from: coolstream on August 24, 2011, 12:18:53 PM
I am only processing one project but in that project there are different applications being run.
But this happens only with suspended tasks?
NO. I am talking about WUs with 'Ready to start' status.
Sorry for taking so long to reply.
Quote from: coolstream on August 25, 2011, 02:32:39 PM
NO. I am talking about WUs with 'Ready to start' status.
Hmm, I don't see that happen with my projects.
Do you have a specific project, not to obscure that I can try. Something I can reproduce.
The only project I am running is World Community Grid (http://www.worldcommunitygrid.org/index.jsp). Presently I have started to work exclusively on only one type of task, but if you need me to, I could get one machine to process a second type and then I could send you a video screen capture.
Quote from: coolstream on August 27, 2011, 12:49:11 PM
The only project I am running is World Community Grid (http://www.worldcommunitygrid.org/index.jsp). Presently I have started to work exclusively on only one type of task, but if you need me to, I could get one machine to process a second type and then I could send you a video screen capture.
That would be nice, that lets me setup the same projects.
OK, I'll get onto it. FYI, the tasks are HCC and HFCC but I have also observed the same behaviour with beta WUs.
OK, here is the video as promised
http://www.youtube.com/watch?v=5977JNNWmr8
I hope it helps.
Good ;D
The reason I tried dual selection twice was to show that the outcome is the same no matter which permutation you try.
Micromanagement from a distance is still possible but could be made easier if all WU types could be opened without going through the process at least twice.
Quote from: coolstream on August 28, 2011, 01:44:32 PM
The reason I tried dual selection twice was to show that the outcome is the same no matter which permutation you try.
What will be impossible is removing the filter for more than one group. Way too much overhead.
If you want to remove the filter for more than one, you have to remove the filter entirely.
What I will do, if you click on another group, is closing the other one and applying the filter to the new one.
Quote from: fred on August 28, 2011, 01:52:27 PMWhat will be impossible is removing the filter for more than one group. Way too much overhead.
If you want to remove the filter for more than one, you have to remove the filter entirely.
What I will do, if you click on another group, is closing the other one and applying the filter to the new one.
I had a feeling you might say that and was going to say that this would mean having to go into | Extra | BoincTasks settings | :(
As a compromise, I was about to suggest another option (suppplemental to double clicking a filtered view) to be able to right-click and make a filter/unfilter toggle, so I tried it and realised that that feature is already available. (I had forgotten about my recent discovery of it).
I realise that my question merits an *advanced* feature, but am glad that you had already anticipated it. Accordingly, a small donation has been sent!
Quote from: coolstream on August 29, 2011, 11:04:19 AM
I had a feeling you might say that and was going to say that this would mean having to go into | Extra | BoincTasks settings | :(
What about right mouse key->Filter->Select the item.
Another thing that's simple, is add Ctrl double click, that releases all filters for a specific type, like Ready to start. For the selected computer only.
Quote from: fred on August 29, 2011, 11:46:52 AMWhat about right mouse key->Filter->Select the item.
Yes. That is what I referring to when I said that I remembered about the quick access to filter settings. ;)
QuoteAnother thing that's simple, is add Ctrl double click, that releases all filters for a specific type, like Ready to start. For the selected computer only.
I am uncertain how the outcome would differ from what I was requesting. but to clarify, when you say 'is add Ctrl double click' you are referring to a proposed update new feature?
Quote from: coolstream on August 29, 2011, 01:55:37 PM
I am uncertain how the outcome would differ from what I was requesting. but to clarify, when you say 'is add Ctrl double click' you are referring to a proposed update new feature?
That would be something new. It would do the same as removing the filter check, but only on the selected computer.
OK, I understand now.
I guess the purpose of CTRL is to add a second filter to that specific machine's view. It is basically what I requested, isn't it? (because dbl-clicking on a filtered view only changes the view for that specific machine anyway).
I look forward to seeing and being able to test this.