Index  | Recent Threads  | Unanswered Threads  | Who's Active  | Guidelines  | Search
 

Quick Go »
No member browsing this thread
Thread Status: Active
Total posts in this thread: 5
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 3457 times and has 4 replies Next Thread
jonathandl
Advanced Cruncher
Joined: Nov 12, 2007
Post Count: 106
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
BOINC 6.10.17 question

I have noticed two changes in BOINC 6.10.17, as compared with BOINC 6.2.18:

  • the "accessible" view no longer seems to exist. I actually think this view was better-looking than the full version of the advanced view.
  • If no work is available (for example, if you are enrolled in "intermittent" projects, such as Discovering Dengue Drugs Together, only) then 6.2.18 would tell you how long it was waiting before it would request more work on its own (Communication deferred mm:ss). 6.10.17 does not display this (it displays "communication deferred" only for short deferrals, under 10 minutes). (So the only way to predict when the next fetch will be is to request it manually, by clicking on "update.") And, if you are enrolled in intermittent projects only, it seems to request new work less often.

Why were these changes made? Is there any way to at least restore the "communication deferred" screen so I know when it will request work next? Thank you.
[Sep 14, 2010 12:49:26 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Dataman
Ace Cruncher
Joined: Nov 16, 2004
Post Count: 4865
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: BOINC 6.10.17 question

Questions about "why" BOINC does anything are best posted in the BOINC forum at Berkeley. WCG does not make these changes. Your options are to fall back to 6.2.18 if you like that better, keep 6.10.17 or upgrade to 6.10.58 (which would be my recommendation).

Cheers and thanks for crunching ... coffee

cowboy
----------------------------------------


[Sep 14, 2010 1:20:21 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Ingleside
Veteran Cruncher
Norway
Joined: Nov 19, 2005
Post Count: 974
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: BOINC 6.10.17 question

I have noticed two changes in BOINC 6.10.17, as compared with BOINC 6.2.18:

  • the "accessible" view no longer seems to exist. I actually think this view was better-looking than the full version of the advanced view.
  • If no work is available (for example, if you are enrolled in "intermittent" projects, such as Discovering Dengue Drugs Together, only) then 6.2.18 would tell you how long it was waiting before it would request more work on its own (Communication deferred mm:ss). 6.10.17 does not display this (it displays "communication deferred" only for short deferrals, under 10 minutes). (So the only way to predict when the next fetch will be is to request it manually, by clicking on "update.") And, if you are enrolled in intermittent projects only, it seems to request new work less often.

Why were these changes made? Is there any way to at least restore the "communication deferred" screen so I know when it will request work next? Thank you.

Don't exactly know, but atleast for the 1st. my guess is it's removed since it's redundant, the "normal" view now also works for anyone needing to use magnifyer or any other accessible-options, so keeping & supporting an extra view just for a few users that doesn't like the "normal" view doesn't make much sence.

For the 2nd... just a guess here, but they possibly didn't like lines along the lines of: "Communication to project is deferred for XXX seconds, to CPU for YYY minutes, for Nvidia for ZZZ minutes, for Ati for NNN minutes".
Even the 1st. has been confusing for many users, since they think there's a problem, and they also is confused when client doesn't connect then reached zero.

The info for when next can connect shows-up if you select a project and hits "Properties".
----------------------------------------


"I make so many mistakes. But then just think of all the mistakes I don't make, although I might."
[Sep 14, 2010 4:47:19 AM]   Link   Report threatening or abusive post: please login first  Go to top 
jonathandl
Advanced Cruncher
Joined: Nov 12, 2007
Post Count: 106
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: BOINC 6.10.17 question

User:Ingleside wrote:

For the 2nd... just a guess here, but they possibly didn't like lines along the lines of: "Communication to project is deferred for XXX seconds, to CPU for YYY minutes, for Nvidia for ZZZ minutes, for Ati for NNN minutes".
Even the 1st. has been confusing for many users, since they think there's a problem, and they also is confused when client doesn't connect then reached zero.

Thank you for the tip about using the "properties" button. With earlier versions of the client, there was only a single countdown timer; I have never seen lines along the lines of "Communication to project is deferred for XXX seconds, to CPU for YYY minutes, for Nvidia for ZZZ minutes, for Ati for NNN minutes."

And yes, I have been confused when the client does not connect after the countdown timer reaches zero; however, I have only seen that happen with 6.10.17... with 6.2.18 as well as with 5.x, it connects immediately when the timer reaches zero.

Anyway, I think the behavior of the earlier versions should be restored....
[Sep 15, 2010 2:44:01 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Sekerob
Ace Cruncher
Joined: Jul 24, 2005
Post Count: 20043
Status: Offline
Reply to this Post  Reply with Quote 
Re: BOINC 6.10.17 question

I'm looking forward to testing the first 6.12.xx Alpha/Beta whatever it will be labeled with and all the "user-friendlier communication" that is in the pipeline.

As for the counter running to zero and not connecting, well allot happens in the scheduler on a continues basis, so the need may have expired to connect... now I picture someone sitting front of the screen and the counter getting aborted when the connection requirement has become redundant. Certainly hitting Update kills them, or sets off a new one ;>)
----------------------------------------
WCG Global & Research > Make Proposal Help: Start Here!
Please help to make the Forums an enjoyable experience for All!
[Sep 15, 2010 9:20:28 AM]   Link   Report threatening or abusive post: please login first  Go to top 
[ Jump to Last Post ]
Post new Thread