I received 7 new 'Albert' WU's and processed them all in about 4 hours ie approximately 35 minutes each. This exceeded my daily allotment of WUs and the server locked that machine out becuase it 'exceeded daily quota of 8.' You may need to review your settings for fast machines when 'Albert' becomes prime time(if these WUs are in fact 'real' and not just test WUs)....Cheers, Rog.
PS...the only way I could get more WUs was to detach and rejoin the project.
BTW: The WUs differ a bit in length depending on the frequency. The longer ones should take about the same time than the previous ones, but at lower frequencies we have some that take down to 1/4 of the time.
BM
Are we still using the big data files that the individual results are analysing? If so, does the big data file contain WU’s with about the same crunch time, or are there a mix of all possible crunch times within the same big data file?
If possible, it would be nice if the shorter WU’s could be sent out to “slower� hosts.
Then you're really interested in a subject, there is no way to avoid it. You have to read the Manual.
I have one puter that updated to the new albert, but my other one wont update... its still 4.79 version... ive manually asked it to update but its not finding that update to the new albert. any sugestions.
I have one puter that updated to the new albert, but my other one wont update... its still 4.79 version... ive manually asked it to update but its not finding that update to the new albert. any sugestions.
Today one of my machines received 4 Albert WUs, and all 4 WUs returned "Client error". This machine doesn't have the latest version of BOINC (5.2.13), but some older version (I think it is 5.2.8, will be able to check it tomorrow). Could that be the reason of those "Client errors"? Does Albert requires latest version of BOINC (5.2.13)? Any other reasons why those "Client errors" could occure? This machine processed Einstein WUs without any problem.
A glitch in networking,firewall,powersurge.. you name it ;)
Not really sure but I read this like the Albert app itself is corrupted.
Does it download a new one if you erase it manually?
BEWARE,I don't know if this works.. I just trying to think. :P
edit: Or you could read it like App tries to download WU but fails.
(in that case deleting the app doesn't work.)
I received 7 new 'Albert' WU's and processed them all in about 4 hours ie approximately 35 minutes each. This exceeded my daily allotment of WUs and the server locked that machine out becuase it 'exceeded daily quota of 8.' You may need to review your settings for fast machines when 'Albert' becomes prime time(if these WUs are in fact 'real' and not just test WUs)....Cheers, Rog.
PS...the only way I could get more WUs was to detach and rejoin the project.
FYI regarding 'Albert' processing times......we've processed 9 so far: 2 that processed in approx. 5 hours and the 7 noted above (35mins). Processing was done on a machine that took about 7 hours on the old (Einstein) WUs. It is running BOINC 5.2.13 and WinXP on an AMD 1.8 Duron. The 'Albert' apps process fine......just address the problem of daily quotas re. shorter processing times and we are good to go!.....Cheers, Rog
Thanks Sharky. I will have to check it tomorrow as I don't have access to this machine all the time. This machine is behind firewall. Not sure if Albert requires different setups for machines behind firewalls than Einstein app.
Is there any other way I can submit this error to get answer from developers?
I received 7 new 'Albert'
)
I received 7 new 'Albert' WU's and processed them all in about 4 hours ie approximately 35 minutes each. This exceeded my daily allotment of WUs and the server locked that machine out becuase it 'exceeded daily quota of 8.' You may need to review your settings for fast machines when 'Albert' becomes prime time(if these WUs are in fact 'real' and not just test WUs)....Cheers, Rog.
PS...the only way I could get more WUs was to detach and rejoin the project.
RE: BTW: The WUs differ a
)
Are we still using the big data files that the individual results are analysing? If so, does the big data file contain WU’s with about the same crunch time, or are there a mix of all possible crunch times within the same big data file?
If possible, it would be nice if the shorter WU’s could be sent out to “slower� hosts.
Then you're really interested in a subject, there is no way to avoid it. You have to read the Manual.
I have one puter that updated
)
I have one puter that updated to the new albert, but my other one wont update... its still 4.79 version... ive manually asked it to update but its not finding that update to the new albert. any sugestions.
RE: I have one puter that
)
Yes. Read the post by Bruce.
Michael
Team Linux Users Everywhere
Today one of my machines
)
Today one of my machines received 4 Albert WUs, and all 4 WUs returned "Client error". This machine doesn't have the latest version of BOINC (5.2.13), but some older version (I think it is 5.2.8, will be able to check it tomorrow). Could that be the reason of those "Client errors"? Does Albert requires latest version of BOINC (5.2.13)? Any other reasons why those "Client errors" could occure? This machine processed Einstein WUs without any problem.
WUs in question are:
http://einsteinathome.org/workunit/3079145
http://einsteinathome.org/workunit/3104925
http://einsteinathome.org/workunit/3104928
http://einsteinathome.org/workunit/3104929
Thanks.
Edo: Looks like transfer
)
Edo:
Looks like transfer errors to me.
5.2.13
app_version download error: couldn't get input files:
albert_4.37_windows_intelx86.exe
-120
signature verification failed
Eh.. It says 5.2.13..?
Thanks Sharky. What could
)
Thanks Sharky. What could cause those transfer errors?
Edo
A glitch in
)
A glitch in networking,firewall,powersurge.. you name it ;)
Not really sure but I read this like the Albert app itself is corrupted.
Does it download a new one if you erase it manually?
BEWARE,I don't know if this works.. I just trying to think. :P
edit: Or you could read it like App tries to download WU but fails.
(in that case deleting the app doesn't work.)
RE: I received 7 new
)
FYI regarding 'Albert' processing times......we've processed 9 so far: 2 that processed in approx. 5 hours and the 7 noted above (35mins). Processing was done on a machine that took about 7 hours on the old (Einstein) WUs. It is running BOINC 5.2.13 and WinXP on an AMD 1.8 Duron. The 'Albert' apps process fine......just address the problem of daily quotas re. shorter processing times and we are good to go!.....Cheers, Rog
Thanks Sharky. I will have to
)
Thanks Sharky. I will have to check it tomorrow as I don't have access to this machine all the time. This machine is behind firewall. Not sure if Albert requires different setups for machines behind firewalls than Einstein app.
Is there any other way I can submit this error to get answer from developers?
Cheers.