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
Michael,
I guess I missed my calling.
BTW: Since it's now "official", I have installed 5.2.2 on my laptop (the Dell).
I know this is not the place to report this (and if it doesn't correct itself soon, I'll post it on the BOINC site). But, having just installed 5.2.2, I have come across my first "strange experience" with it. It finished it's first Seti unit about an hour ago (which was probably started under 4.45). The unit is listed under the "Work" tab as "Ready to report". However, it is not listed under the "Transfers" tab. And, when I look under the "Messages" tab, it shows that, after three "Temporarily failed upload" sequences, it uploaded successfully on the fourth try. The Seti site stills shows the WU as "In Progess", however.
BTW: Since it's now "official", I have installed 5.2.2 on my laptop (the Dell).
Stick
Stick,
I'm about to go that route, too, despite my serious misgivings about the phony in-process To Completion calcs. I mean, that isn't a bug, just a designed-in annoyance. It's easy enough to calculate for myself (CPU time/%complete)*99 = total time. (I know, that's not the same as To Completion, but it's easy enough to subtract). Might even finish the equation and write a macro for it.
I might be going retro on the Einstein app, though, to 4.19, to pump up the granted credit. Yeah, I know about the quorum moderating that and all. The simple fact is that right now, I am the mean value in the quorum an unproportionate % of the time. On average, you'd expect me to be the mean value on ~30% of the WUs, given that I'm Very seldom the 4th to turn in a result. However, checking my results today, my claim value turned out to be the granted value on an astounding 63% of my completed and credited WUs! That's 24 times out of 38 total. So if I go with 4.19 and it's inherent higher claim, granted credit will be increased on at least 63% of WUs I crunch.
Michael
microcraft
"The arc of history is long, but it bends toward justice" - MLK
I know this is not the place to report this (and if it doesn't correct itself soon, I'll post it on the BOINC site). But, having just installed 5.2.2, I have come across my first "strange experience" with it. It finished it's first Seti unit about an hour ago (which was probably started under 4.45). The unit is listed under the "Work" tab as "Ready to report". However, it is not listed under the "Transfers" tab. And, when I look under the "Messages" tab, it shows that, after three "Temporarily failed upload" sequences, it uploaded successfully on the fourth try. The Seti site stills shows the WU as "In Progess", however.
Stick,
Sending the results is a two step process. First the result data is uploaded to the upload server, and while thats happening you'll see it in the transfer tab. Afterwords the result will be "waiting to report", which it'll do the next time BOINC contacts the scheduler. Reporting is where it sends the administrative details about the result - exit status, CPU time, error messages, things like that.
Some earlier versions of BOINC had a bug where it reported results right after uploading. That was fixed in 5.2. Now it'll contact the scheduler to report if it reaches the deadline or 24 hours after the workunit finishes. If BOINC contacts the scheduler for some other reason, it'll report the results then. Like if you manually "update" the project or BOINC requests more work.
Idea is to reduce the times BOINC contacts the scheduler to report work or request it, and this way it combines several requests into one contacts. With a short "connect every" interval it'll report the previous result when it requests a new workunit. With a longer interval it can report several workunits either after 24 hours have passed or when it requests more work.
And even though a result gets uploaded, the server won't show it as complete until its reported. And it'll use that as the "completion" time, even though the result had already been uploaded.
Just a quick report back - as you know the "run based on preferences" is selected, in which I have said to change every hour - the idea being to rotate between the projects. Granted it is early days still and BOINC may still be settling in as it were, however Einstein is still grabbing total time. I admit that the deadlines for Einstein are a mere 11 days away, while Rosetta is only due mid November and Climate is due October 2006, so that might be the problem right there - BOINC is deciding what work units to do based purely on deadlines, rather than on preferences that I choose. I am not sure if this is by design or not. It would appear that I may have to physically suspend a project to get the other projects for the meantime until this is either changed or the devs state clearly that this is by design.
I know this is not the place to report this (and if it doesn't correct itself soon, I'll post it on the BOINC site). But, having just installed 5.2.2, I have come across my first "strange experience" with it. It finished it's first Seti unit about an hour ago (which was probably started under 4.45). The unit is listed under the "Work" tab as "Ready to report". However, it is not listed under the "Transfers" tab. And, when I look under the "Messages" tab, it shows that, after three "Temporarily failed upload" sequences, it uploaded successfully on the fourth try. The Seti site stills shows the WU as "In Progess", however.
Stick,
The data upload and the report are 2 different events, and do not occur simultaneously. I believe that if you click the "Update" button, you'll then see the result reported, the Wu gone from the "Work" screen, and SETI site showing the result completed.
Your friend,
Michael
EDIT: I see that Walt has already explained this much more eloquently.
Thanks again, Walt, for looking things over here.
microcraft
"The arc of history is long, but it bends toward justice" - MLK
Just a quick report back - as you know the "run based on preferences" is selected, in which I have said to change every hour - the idea being to rotate between the projects. Granted it is early days still and BOINC may still be settling in as it were, however Einstein is still grabbing total time. I admit that the deadlines for Einstein are a mere 11 days away, while Rosetta is only due mid November and Climate is due October 2006, so that might be the problem right there - BOINC is deciding what work units to do based purely on deadlines, rather than on preferences that I choose. I am not sure if this is by design or not. It would appear that I may have to physically suspend a project to get the other projects for the meantime until this is either changed or the devs state clearly that this is by design.
Gray
Gray,
No other deadlines are anywhere close to imminent, so you have at least a week to defer suspending a project.
Let me know what your load is, how many Rosetta, Einstein WUs are on the table. I know you can't have a fistful of Climate WUs there.
Michael
microcraft
"The arc of history is long, but it bends toward justice" - MLK
I might be going retro on the Einstein app, though, to 4.19, to pump up the granted credit. Yeah, I know about the quorum moderating that and all. The simple fact is that right now, I am the mean value in the quorum an unproportionate % of the time. On average, you'd expect me to be the mean value on ~30% of the WUs, given that I'm Very seldom the 4th to turn in a result. However, checking my results today, my claim value turned out to be the granted value on an astounding 63% of my completed and credited WUs! That's 24 times out of 38 total. So if I go with 4.19 and it's inherent higher claim, granted credit will be increased on at least 63% of WUs I crunch.
Michael
Michael,
(I am about to go into "Silver-tongued" mode - so be forewarned.)
I am surprised at you! Why would you even consider such a thing? You are too valuable on the "cutting edge" side of things to go "retro". You provide excellent feedback to the developers (even if you might overdo it every now and then). ;-). And, all because of the idea you might be "losing ground" in the "silly little game" of "counting up credits". Come on, go the other way, run the Beta and help to improve the next version of Einstein. In the "BIG" scheme, "credits" don't mean squat.
(Now back to "normal mode".) I think the granted credit/qourum process is pretty bogus (although it doesn't bother me enough to complain about). And, I am not too crazy about the claimed credit/benchmarhing thing either; but, again, it doesn't bother me. However, if you are "into" the credit counting "thing", why don't you start a thread on "Wish List" about the process. I might even throw in "my two cents worth".
Just a quick report back - as you know the "run based on preferences" is selected, in which I have said to change every hour - the idea being to rotate between the projects. Granted it is early days still and BOINC may still be settling in as it were, however Einstein is still grabbing total time. I admit that the deadlines for Einstein are a mere 11 days away, while Rosetta is only due mid November and Climate is due October 2006, so that might be the problem right there - BOINC is deciding what work units to do based purely on deadlines, rather than on preferences that I choose. I am not sure if this is by design or not. It would appear that I may have to physically suspend a project to get the other projects for the meantime until this is either changed or the devs state clearly that this is by design.
Gray
Gray,
No other deadlines are anywhere close to imminent, so you have at least a week to defer suspending a project.
Let me know what your load is, how many Rosetta, Einstein WUs are on the table. I know you can't have a fistful of Climate WUs there.
Michael
Hi Michael
Yep agreed - no immediate need for a suspension of a project. This was just an observation. A fistful of Climate WUs: yipe !! Perish the thought at 2 months a WU I don't want to go THAT route !!! Rosetta is quite a lot erm (counting...)... around 48 WUs, but as I say, the deadline is well away and quite within the bounds of possibility considering that I can do around 5 or 6 a day (supossedly just under 4 hours per WU. Einstein is an easy 4 untouched and working on number 5 - all Einstein WUs deadlined for the 31st. I think I will finish off Einstein and then suspend it and run Rosetta until that finishes and then finally go to Climate - unless the devs release an update that sorts the problem. This is not a project issue but rather one for the BOINC devs, as when I suspended Einstein and ran Rosettta for a while, BOINC would not alternate between Rosetta and Climate either.
Thank you for the response(s)! I guess I just came across a new "feature" and didn't recognize it as such. It's definitely a difference from the way 4.45 works.
Quote:
Quote:
I know this is not the place to report this (and if it doesn't correct itself soon, I'll post it on the BOINC site). But, having just installed 5.2.2, I have come across my first "strange experience" with it. It finished it's first Seti unit about an hour ago (which was probably started under 4.45). The unit is listed under the "Work" tab as "Ready to report". However, it is not listed under the "Transfers" tab. And, when I look under the "Messages" tab, it shows that, after three "Temporarily failed upload" sequences, it uploaded successfully on the fourth try. The Seti site stills shows the WU as "In Progess", however.
Stick,
Sending the results is a two step process. First the result data is uploaded to the upload server, and while thats happening you'll see it in the transfer tab. Afterwords the result will be "waiting to report", which it'll do the next time BOINC contacts the scheduler. Reporting is where it sends the administrative details about the result - exit status, CPU time, error messages, things like that.
Some earlier versions of BOINC had a bug where it reported results right after uploading. That was fixed in 5.2. Now it'll contact the scheduler to report if it reaches the deadline or 24 hours after the workunit finishes. If BOINC contacts the scheduler for some other reason, it'll report the results then. Like if you manually "update" the project or BOINC requests more work.
Idea is to reduce the times BOINC contacts the scheduler to report work or request it, and this way it combines several requests into one contacts. With a short "connect every" interval it'll report the previous result when it requests a new workunit. With a longer interval it can report several workunits either after 24 hours have passed or when it requests more work.
And even though a result gets uploaded, the server won't show it as complete until its reported. And it'll use that as the "completion" time, even though the result had already been uploaded.
RE: RE: Because, you are
)
Michael,
I guess I missed my calling.
BTW: Since it's now "official", I have installed 5.2.2 on my laptop (the Dell).
Stick
I know this is not the place
)
I know this is not the place to report this (and if it doesn't correct itself soon, I'll post it on the BOINC site). But, having just installed 5.2.2, I have come across my first "strange experience" with it. It finished it's first Seti unit about an hour ago (which was probably started under 4.45). The unit is listed under the "Work" tab as "Ready to report". However, it is not listed under the "Transfers" tab. And, when I look under the "Messages" tab, it shows that, after three "Temporarily failed upload" sequences, it uploaded successfully on the fourth try. The Seti site stills shows the WU as "In Progess", however.
RE: BTW: Since it's now
)
Stick,
I'm about to go that route, too, despite my serious misgivings about the phony in-process To Completion calcs. I mean, that isn't a bug, just a designed-in annoyance. It's easy enough to calculate for myself (CPU time/%complete)*99 = total time. (I know, that's not the same as To Completion, but it's easy enough to subtract). Might even finish the equation and write a macro for it.
I might be going retro on the Einstein app, though, to 4.19, to pump up the granted credit. Yeah, I know about the quorum moderating that and all. The simple fact is that right now, I am the mean value in the quorum an unproportionate % of the time. On average, you'd expect me to be the mean value on ~30% of the WUs, given that I'm Very seldom the 4th to turn in a result. However, checking my results today, my claim value turned out to be the granted value on an astounding 63% of my completed and credited WUs! That's 24 times out of 38 total. So if I go with 4.19 and it's inherent higher claim, granted credit will be increased on at least 63% of WUs I crunch.
Michael
microcraft
"The arc of history is long, but it bends toward justice" - MLK
RE: I know this is not the
)
Stick,
Sending the results is a two step process. First the result data is uploaded to the upload server, and while thats happening you'll see it in the transfer tab. Afterwords the result will be "waiting to report", which it'll do the next time BOINC contacts the scheduler. Reporting is where it sends the administrative details about the result - exit status, CPU time, error messages, things like that.
Some earlier versions of BOINC had a bug where it reported results right after uploading. That was fixed in 5.2. Now it'll contact the scheduler to report if it reaches the deadline or 24 hours after the workunit finishes. If BOINC contacts the scheduler for some other reason, it'll report the results then. Like if you manually "update" the project or BOINC requests more work.
Idea is to reduce the times BOINC contacts the scheduler to report work or request it, and this way it combines several requests into one contacts. With a short "connect every" interval it'll report the previous result when it requests a new workunit. With a longer interval it can report several workunits either after 24 hours have passed or when it requests more work.
And even though a result gets uploaded, the server won't show it as complete until its reported. And it'll use that as the "completion" time, even though the result had already been uploaded.
Walt
Hello Michael Just a quick
)
Hello Michael
Just a quick report back - as you know the "run based on preferences" is selected, in which I have said to change every hour - the idea being to rotate between the projects. Granted it is early days still and BOINC may still be settling in as it were, however Einstein is still grabbing total time. I admit that the deadlines for Einstein are a mere 11 days away, while Rosetta is only due mid November and Climate is due October 2006, so that might be the problem right there - BOINC is deciding what work units to do based purely on deadlines, rather than on preferences that I choose. I am not sure if this is by design or not. It would appear that I may have to physically suspend a project to get the other projects for the meantime until this is either changed or the devs state clearly that this is by design.
Gray
RE: I know this is not the
)
Stick,
The data upload and the report are 2 different events, and do not occur simultaneously. I believe that if you click the "Update" button, you'll then see the result reported, the Wu gone from the "Work" screen, and SETI site showing the result completed.
Your friend,
Michael
EDIT: I see that Walt has already explained this much more eloquently.
Thanks again, Walt, for looking things over here.
microcraft
"The arc of history is long, but it bends toward justice" - MLK
RE: Hello Michael Just a
)
Gray,
No other deadlines are anywhere close to imminent, so you have at least a week to defer suspending a project.
Let me know what your load is, how many Rosetta, Einstein WUs are on the table. I know you can't have a fistful of Climate WUs there.
Michael
microcraft
"The arc of history is long, but it bends toward justice" - MLK
RE: I might be going retro
)
Michael,
(I am about to go into "Silver-tongued" mode - so be forewarned.)
I am surprised at you! Why would you even consider such a thing? You are too valuable on the "cutting edge" side of things to go "retro". You provide excellent feedback to the developers (even if you might overdo it every now and then). ;-). And, all because of the idea you might be "losing ground" in the "silly little game" of "counting up credits". Come on, go the other way, run the Beta and help to improve the next version of Einstein. In the "BIG" scheme, "credits" don't mean squat.
(Now back to "normal mode".) I think the granted credit/qourum process is pretty bogus (although it doesn't bother me enough to complain about). And, I am not too crazy about the claimed credit/benchmarhing thing either; but, again, it doesn't bother me. However, if you are "into" the credit counting "thing", why don't you start a thread on "Wish List" about the process. I might even throw in "my two cents worth".
Stick
RE: RE: Hello
)
Hi Michael
Yep agreed - no immediate need for a suspension of a project. This was just an observation. A fistful of Climate WUs: yipe !! Perish the thought at 2 months a WU I don't want to go THAT route !!! Rosetta is quite a lot erm (counting...)... around 48 WUs, but as I say, the deadline is well away and quite within the bounds of possibility considering that I can do around 5 or 6 a day (supossedly just under 4 hours per WU. Einstein is an easy 4 untouched and working on number 5 - all Einstein WUs deadlined for the 31st. I think I will finish off Einstein and then suspend it and run Rosetta until that finishes and then finally go to Climate - unless the devs release an update that sorts the problem. This is not a project issue but rather one for the BOINC devs, as when I suspended Einstein and ran Rosettta for a while, BOINC would not alternate between Rosetta and Climate either.
Gray
Walt (and Michael), Thank
)
Walt (and Michael),
Thank you for the response(s)! I guess I just came across a new "feature" and didn't recognize it as such. It's definitely a difference from the way 4.45 works.