PS: there is still an issue doing a project such as Climate alongside Einstein as BOINC doesn't go from one to the other every hour (50% resources each) - I assume that BOINC looks at the deadlines for each, and as Climate is October 2006, Einstein gets first option every time ?
I should add that I DID specify one hour per project in preferences.
The next step is to try out Rosetta@home - the work units are smallish and so should see if the swopping between clients happens this time. Also I reckon the medicos could do with some support :)
One thing I did notice when hooking up with Rosetta via the BOINC wizard is that at the end of the process I was informed that the attempt to join Rosetta project had failed, but then a couple of seconds later Rosetta appeared in my list of projects anyway, and the downloads began - something a little strange there...
Gray
Gray,
Things are improving nicely for you!
As you can see from my open post (below), there may be an issue with 5.2.x not reporting completed WUs automatically. I recall reading something pertaining to this issue, but if I recall correctly, they concluded that Einstein was one project that was immune to that glitch. I'll have a better look at things with the currently processing WU, and should have an answer, one way or the other, by tomorrow morning, about 17 hours away. If you think or it, please check to see if it works on 5.2.2.
Re: Climate and/or Rosetta getting proper share time, it usually takes a few days for the manager to settle into it's routine, and forcing a project to crunch seems to confuse manager, and delay it's settling-in period. Since Climate has a year deadline, and Rosetta's is 28 days (I believe), you can comfortably allow manager time to sort things out without jeopardizing any deadlines.
Further note on swapping: Make sure that you set "Run based on preferences" instead of "Run always" in the "Commands" drop-down, or your carefully set up prefs may be overridden.
Regards,
Michael
Hello Michael
AAAAArgh - yes I had forgotten about that - I have planty of RAM and CPU power so usually set it to run always, so I can use the PC in the meantime - I think I will change how the preferences are set up - work while I am using the PC etc as that would definitely explain a lot of stuff (boy do I feel like an idiot :( )
PS: there is still an issue doing a project such as Climate alongside Einstein as BOINC doesn't go from one to the other every hour (50% resources each) - I assume that BOINC looks at the deadlines for each, and as Climate is October 2006, Einstein gets first option every time ?
I should add that I DID specify one hour per project in preferences.
The next step is to try out Rosetta@home - the work units are smallish and so should see if the swopping between clients happens this time. Also I reckon the medicos could do with some support :)
One thing I did notice when hooking up with Rosetta via the BOINC wizard is that at the end of the process I was informed that the attempt to join Rosetta project had failed, but then a couple of seconds later Rosetta appeared in my list of projects anyway, and the downloads began - something a little strange there...
Gray
Gray,
Things are improving nicely for you!
As you can see from my open post (below), there may be an issue with 5.2.x not reporting completed WUs automatically. I recall reading something pertaining to this issue, but if I recall correctly, they concluded that Einstein was one project that was immune to that glitch. I'll have a better look at things with the currently processing WU, and should have an answer, one way or the other, by tomorrow morning, about 17 hours away. If you think or it, please check to see if it works on 5.2.2.
Re: Climate and/or Rosetta getting proper share time, it usually takes a few days for the manager to settle into it's routine, and forcing a project to crunch seems to confuse manager, and delay it's settling-in period. Since Climate has a year deadline, and Rosetta's is 28 days (I believe), you can comfortably allow manager time to sort things out without jeopardizing any deadlines.
Further note on swapping: Make sure that you set "Run based on preferences" instead of "Run always" in the "Commands" drop-down, or your carefully set up prefs may be overridden.
Regards,
Michael
Hello Michael
AAAAArgh - yes I had forgotten about that - I have planty of RAM and CPU power so usually set it to run always, so I can use the PC in the meantime - I think I will change how the preferences are set up - work while I am using the PC etc as that would definitely explain a lot of stuff (boy do I feel like an idiot :( )
Will keep you uptodate
Gray
OK have changed preferences to run while I use the PC - will suspend if I need to use a graphics app, or play a cpu intensive game. Let's see how things work now
PS: there is still an issue doing a project such as Climate alongside Einstein as BOINC doesn't go from one to the other every hour (50% resources each) - I assume that BOINC looks at the deadlines for each, and as Climate is October 2006, Einstein gets first option every time ?
I should add that I DID specify one hour per project in preferences.
The next step is to try out Rosetta@home - the work units are smallish and so should see if the swopping between clients happens this time. Also I reckon the medicos could do with some support :)
One thing I did notice when hooking up with Rosetta via the BOINC wizard is that at the end of the process I was informed that the attempt to join Rosetta project had failed, but then a couple of seconds later Rosetta appeared in my list of projects anyway, and the downloads began - something a little strange there...
Gray
Gray,
Things are improving nicely for you!
As you can see from my open post (below), there may be an issue with 5.2.x not reporting completed WUs automatically. I recall reading something pertaining to this issue, but if I recall correctly, they concluded that Einstein was one project that was immune to that glitch. I'll have a better look at things with the currently processing WU, and should have an answer, one way or the other, by tomorrow morning, about 17 hours away. If you think or it, please check to see if it works on 5.2.2.
Re: Climate and/or Rosetta getting proper share time, it usually takes a few days for the manager to settle into it's routine, and forcing a project to crunch seems to confuse manager, and delay it's settling-in period. Since Climate has a year deadline, and Rosetta's is 28 days (I believe), you can comfortably allow manager time to sort things out without jeopardizing any deadlines.
Further note on swapping: Make sure that you set "Run based on preferences" instead of "Run always" in the "Commands" drop-down, or your carefully set up prefs may be overridden.
Regards,
Michael
Hello Michael
AAAAArgh - yes I had forgotten about that - I have planty of RAM and CPU power so usually set it to run always, so I can use the PC in the meantime - I think I will change how the preferences are set up - work while I am using the PC etc as that would definitely explain a lot of stuff (boy do I feel like an idiot :( )
Will keep you uptodate
Gray
OK have changed preferences to run while I use the PC - will suspend if I need to use a graphics app, or play a cpu intensive game. Let's see how things work now
Gray
In fact that would defintely explain the lack of swapping, although I think the change every 60 minutes is default under the general preferences, but maybe BOINC doesn't have that built in as well. Well I might even join Seti again while I am at it to give this a decent test - plenty of book reading coming up eh ?
There seems to be a problem with 5.2.1 reporting completed WUs. I've only now noticed this behavior because I routinely "Update" shortly after a WU is processed. In the interest of testing, I deliberately left the most recently completed WU to report on Boinc's own terms, but it had been over 7 hours, well past my "connect every..." value, which is set to 0.27 days. I exited Boinc through the system tray, and upon starting it again a short time later, the WU was successfully reported. I have the manager set to "Run based on preferences" and "Network activity always available", cable internet.
I shall allow the next WU at least 10 hours to be reported before further interference, to verify what I suspect is a bug.
Michael
Michael, 10 hours isn't long enough. Try waiting 24 hours.
The result should be reported when BOINC contacts the scheduler to request work, when the deadline approaches, when you manually "update" or 24 hours after the its uploaded (that last might be 24 hours after the workunit completes). Your "connect every..." setting doesn't make it report any earlier.
OK have changed preferences to run while I use the PC - will suspend if I need to use a graphics app, or play a cpu intensive game. Let's see how things work now
Gray
Gary,
That's how mine is set up, and if I forget to suspend Boinc while running a CPU-heavy game, Windows kicks Boinc to the curb anyway, giving it only leftover CPU cycles, because Boinc is set to lowest priority in Task Manager, automatically. Works great!
Michael
microcraft
"The arc of history is long, but it bends toward justice" - MLK
There seems to be a problem with 5.2.1 reporting completed WUs. I've only now noticed this behavior because I routinely "Update" shortly after a WU is processed. In the interest of testing, I deliberately left the most recently completed WU to report on Boinc's own terms, but it had been over 7 hours, well past my "connect every..." value, which is set to 0.27 days. I exited Boinc through the system tray, and upon starting it again a short time later, the WU was successfully reported. I have the manager set to "Run based on preferences" and "Network activity always available", cable internet.
I shall allow the next WU at least 10 hours to be reported before further interference, to verify what I suspect is a bug.
Michael
Michael, 10 hours isn't long enough. Try waiting 24 hours.
The result should be reported when BOINC contacts the scheduler to request work, when the deadline approaches, when you manually "update" or 24 hours after the its uploaded (that last might be 24 hours after the workunit completes). Your "connect every..." setting doesn't make it report any earlier.
Walt
Walt,
OK, will do. I'll allow it to simmer until tomorrow evening.
BTW, can you say what fixes/adjustments were made between 5.2.1 and 5.2.2?
Thanks for the advice, Walt, and for having a look here.
Regards,
Michael
microcraft
"The arc of history is long, but it bends toward justice" - MLK
OK have changed preferences to run while I use the PC - will suspend if I need to use a graphics app, or play a cpu intensive game. Let's see how things work now
Gray
Gary,
That's how mine is set up, and if I forget to suspend Boinc while running a CPU-heavy game, Windows kicks Boinc to the curb anyway, giving it only leftover CPU cycles, because Boinc is set to lowest priority in Task Manager, automatically.
Michael
That's great - Im going to leave it like this for a while and just keep an eye of stuff - I'll come back here over the weekend and report back again (Sat night is very probable) - having a nice quiet one for a change - not going ANYWHERE !!
There seems to be a problem with 5.2.1 reporting completed WUs. I've only now noticed this behavior because I routinely "Update" shortly after a WU is processed. In the interest of testing, I deliberately left the most recently completed WU to report on Boinc's own terms, but it had been over 7 hours, well past my "connect every..." value, which is set to 0.27 days. I exited Boinc through the system tray, and upon starting it again a short time later, the WU was successfully reported. I have the manager set to "Run based on preferences" and "Network activity always available", cable internet.
I shall allow the next WU at least 10 hours to be reported before further interference, to verify what I suspect is a bug.
Michael
Michael, 10 hours isn't long enough. Try waiting 24 hours.
The result should be reported when BOINC contacts the scheduler to request work, when the deadline approaches, when you manually "update" or 24 hours after the its uploaded (that last might be 24 hours after the workunit completes). Your "connect every..." setting doesn't make it report any earlier.
Walt
Walt,
OK, will do. I'll allow it to simmer until tomorrow evening.
BTW, can you say what fixes/adjustments were made between 5.2.1 and 5.2.2?
Thanks for the advice, Walt.
Regards,
Michael
5.2.1 has a bug where sometimes file transfers don't start. That was the result of trying to fix the way BOINC retries file transfers that failed. So they backed out the change and 5.2.2 handles retries like the older versions do.
5.2.2 creates a password file if you don't already have one and fills it with a random string as password. That won't affect anything if you only run boicnmgr on the local machine, but it will if you use BoincView or use boincmgr on another system to connect "remotely".
Some changes were made to account creation, in launching browsers and the "deferring communications...." message was changed from an error to an informational message.
[edit] The change for launching the browser is on Linux, it now displays the URL if it can't find the browser.
Because, you are also using the newest version of BOINC, you have the opportunity to help test the Beta app on a new platform. Any problems you find and report will get the attention of the software guys and fixes will follow. That won't happen if you stay with 4.79. Besides, if you help to test the Beta, your contribution to the Einstein project will be much more important than just cranking out a few WU's. Think about it.
Stick,
You have the gift of the Silver Tongue. You could sell burial plots to teenagers.
:-)
Michael
microcraft
"The arc of history is long, but it bends toward justice" - MLK
RE: RE: PS: there is
)
Hello Michael
AAAAArgh - yes I had forgotten about that - I have planty of RAM and CPU power so usually set it to run always, so I can use the PC in the meantime - I think I will change how the preferences are set up - work while I am using the PC etc as that would definitely explain a lot of stuff (boy do I feel like an idiot :( )
Will keep you uptodate
Gray
RE: RE: RE: PS: there
)
OK have changed preferences to run while I use the PC - will suspend if I need to use a graphics app, or play a cpu intensive game. Let's see how things work now
Gray
RE: RE: RE: RE: PS:
)
In fact that would defintely explain the lack of swapping, although I think the change every 60 minutes is default under the general preferences, but maybe BOINC doesn't have that built in as well. Well I might even join Seti again while I am at it to give this a decent test - plenty of book reading coming up eh ?
Gray
RE: There seems to be a
)
Michael, 10 hours isn't long enough. Try waiting 24 hours.
The result should be reported when BOINC contacts the scheduler to request work, when the deadline approaches, when you manually "update" or 24 hours after the its uploaded (that last might be 24 hours after the workunit completes). Your "connect every..." setting doesn't make it report any earlier.
Walt
RE: OK have changed
)
Gary,
That's how mine is set up, and if I forget to suspend Boinc while running a CPU-heavy game, Windows kicks Boinc to the curb anyway, giving it only leftover CPU cycles, because Boinc is set to lowest priority in Task Manager, automatically. Works great!
Michael
microcraft
"The arc of history is long, but it bends toward justice" - MLK
RE: RE: There seems to be
)
Walt,
OK, will do. I'll allow it to simmer until tomorrow evening.
BTW, can you say what fixes/adjustments were made between 5.2.1 and 5.2.2?
Thanks for the advice, Walt, and for having a look here.
Regards,
Michael
microcraft
"The arc of history is long, but it bends toward justice" - MLK
RE: RE: OK have changed
)
That's great - Im going to leave it like this for a while and just keep an eye of stuff - I'll come back here over the weekend and report back again (Sat night is very probable) - having a nice quiet one for a change - not going ANYWHERE !!
Gray
RE: RE: RE: There seems
)
5.2.1 has a bug where sometimes file transfers don't start. That was the result of trying to fix the way BOINC retries file transfers that failed. So they backed out the change and 5.2.2 handles retries like the older versions do.
5.2.2 creates a password file if you don't already have one and fills it with a random string as password. That won't affect anything if you only run boicnmgr on the local machine, but it will if you use BoincView or use boincmgr on another system to connect "remotely".
Some changes were made to account creation, in launching browsers and the "deferring communications...." message was changed from an error to an informational message.
[edit] The change for launching the browser is on Linux, it now displays the URL if it can't find the browser.
Walt
RE: Because, you are also
)
Stick,
You have the gift of the Silver Tongue. You could sell burial plots to teenagers.
:-)
Michael
microcraft
"The arc of history is long, but it bends toward justice" - MLK
To All, Version 5.2.2 of
)
To All,
Version 5.2.2 of Boinc is officially out of beta and is now the recommended client.
Available for download here.
Thanks to all of you who have tried it, tested, and posted here. You may want to continue to use this thread to discuss the new Boinc client.
Respects,
Michael
microcraft
"The arc of history is long, but it bends toward justice" - MLK