Correct. I went to no new work just prior to it because I had a feeling that something like this was going to happen.
Quote:
Then again, there are no S5R1 and S5RI results anymore, but for a couple of resents, so what do you want? To have the big group of Einstein's volunteer crunchers to wait around for that other smaller group of volunteer crunchers to Beta test S5R2? ;-)
In my opinion, yes. Alternatively the project could do something like what SETI Classic did and simply reissue some of the S5RI work. S5R2 has what was being defined as "brand new coding" (paraphrase). Just that simple statement in and of itself should've called for an open beta. They have done so in the past for other releases.
S5R2 is a beta product. The project team apparently made the decision to go anyway, apparently based on something that I sense that you're echoing; that "some work being done is better than having a couple of weeks with no work".
Jord, seriously, look around. There are immediate crashes. A project developer has plainly stated that things look bad right now. Prior to release another project developer stated that they were taking care of "showstoppers" in the 3-5 day window before the app was sent out to the public. S5R2 is beta. If you would like to explain how I am incorrect, then feel free to do so, but please, don't just try to use the "no one is forcing you" line again.
After sometime I terminated the first unit with S5R2.
I need a long time, about 12 hours (51.900 sec). So I needed about 5,4 times
more than normal. So I am a little bit disapointed that I get only 113 points.
The double of the normal units.
I've just started my first S5R2 WU. It's behaving like Rosetta, i.e. the "time remaining" increments along with the CPU time. Is this to be expected. The estimated time for the WU was around 12 hours. It's done 3.33 hours (16%) but the "to completion" time is showing 11:17:43...all OK? I think not!!
On all 3 of my systems the DCF has gone up between s5r1 and s5r2. That is to say that at the transition point your ETA for completing a WU is too low. Boinc appears to be adjusting this value during the running of a single WU and is adjusting the ETAs as a result. MY PCs have all stabilized around the new correct value after a half dozenish WUs.
Correct. I went to no new work just prior to it because I had a feeling that something like this was going to happen.
Quote:
Then again, there are no S5R1 and S5RI results anymore, but for a couple of resents, so what do you want? To have the big group of Einstein's volunteer crunchers to wait around for that other smaller group of volunteer crunchers to Beta test S5R2? ;-)
In my opinion, yes. Alternatively the project could do something like what SETI Classic did and simply reissue some of the S5RI work. S5R2 has what was being defined as "brand new coding" (paraphrase). Just that simple statement in and of itself should've called for an open beta. They have done so in the past for other releases.
S5R2 is a beta product. The project team apparently made the decision to go anyway, apparently based on something that I sense that you're echoing; that "some work being done is better than having a couple of weeks with no work".
Jord, seriously, look around. There are immediate crashes. A project developer has plainly stated that things look bad right now. Prior to release another project developer stated that they were taking care of "showstoppers" in the 3-5 day window before the app was sent out to the public. S5R2 is beta. If you would like to explain how I am incorrect, then feel free to do so, but please, don't just try to use the "no one is forcing you" line again.
Thanks,
Brian
This whole turnover seemed kind of last minute to me, which is interesting because the estimated time that S5R1 was to be completed was known months in advance. We sort of assume I guess that a big project like this perhaps has its own internal bureaucracies and everything takes longer as opposed to a smaller project team.
At any rate, perhaps they alternatively could have said something like "the whole project is going to Beta for the next few weeks, we are looking for........ If you do not wish to participate, please come back an see us in a few weeks!"
That would at least have given people a "heads up" to know what to expect.
Jord is right...no one is forcing anyone to process S5R2. Our AMD machines will crunch elsewhere until all this is resolved...CU later(hopefully)....Cheers, Rog.
At any rate, perhaps they alternatively could have said something like "the whole project is going to Beta for the next few weeks, we are looking for........ If you do not wish to participate, please come back an see us in a few weeks!"
That would at least have given people a "heads up" to know what to expect.
At any rate, just my 2 cents.
As in:
Quote:
We therefore will set up S5R2 as a short, experimental run that limits the search to parts of the parameter space where the overhead is well under control. During this short run we will improve the Application in various aspects. The results will also help us tuning the parameters for the next, larger run (probably named S5R3).
-from the OP at the start of this very thread. Sounds like a pretty good "heads up" to me.
S5R2 is a beta product. The project team apparently made the decision to go anyway, apparently based on something that I sense that you're echoing; that "some work being done is better than having a couple of weeks with no work".
I haven't seen S5R2 being in test, to be honest, so yes, your anaolgy could be correct. Then again, the same thing happened for S5RI ... :-)
And the credit thing is explained: EAH was asking too much.
Since credits are now set server side, it doesn't matter much. Can you even compare it to S5R1 (and RI)?
Please read this complete
)
Please read this complete thread...
As Dr. Bruce Allen has said here:
So is it normal and OK? Yep, for now it is.
RE: No one is forcing you
)
Correct. I went to no new work just prior to it because I had a feeling that something like this was going to happen.
In my opinion, yes. Alternatively the project could do something like what SETI Classic did and simply reissue some of the S5RI work. S5R2 has what was being defined as "brand new coding" (paraphrase). Just that simple statement in and of itself should've called for an open beta. They have done so in the past for other releases.
S5R2 is a beta product. The project team apparently made the decision to go anyway, apparently based on something that I sense that you're echoing; that "some work being done is better than having a couple of weeks with no work".
Jord, seriously, look around. There are immediate crashes. A project developer has plainly stated that things look bad right now. Prior to release another project developer stated that they were taking care of "showstoppers" in the 3-5 day window before the app was sent out to the public. S5R2 is beta. If you would like to explain how I am incorrect, then feel free to do so, but please, don't just try to use the "no one is forcing you" line again.
Thanks,
Brian
RE: RE: RE: After
)
On all 3 of my systems the DCF has gone up between s5r1 and s5r2. That is to say that at the transition point your ETA for completing a WU is too low. Boinc appears to be adjusting this value during the running of a single WU and is adjusting the ETAs as a result. MY PCs have all stabilized around the new correct value after a half dozenish WUs.
RE: RE: No one is
)
This whole turnover seemed kind of last minute to me, which is interesting because the estimated time that S5R1 was to be completed was known months in advance. We sort of assume I guess that a big project like this perhaps has its own internal bureaucracies and everything takes longer as opposed to a smaller project team.
At any rate, perhaps they alternatively could have said something like "the whole project is going to Beta for the next few weeks, we are looking for........ If you do not wish to participate, please come back an see us in a few weeks!"
That would at least have given people a "heads up" to know what to expect.
At any rate, just my 2 cents.
RE: RE: No one is forcing
)
Jord is right...no one is forcing anyone to process S5R2. Our AMD machines will crunch elsewhere until all this is resolved...CU later(hopefully)....Cheers, Rog.
RE: At any rate, perhaps
)
As in:
-from the OP at the start of this very thread. Sounds like a pretty good "heads up" to me.
Einstein@Home has a beta test
)
Einstein@Home has a beta test page from the beginning of the project.
As far as i know it's open for everybody. S5R2 code was tested on it.
RE: -from the OP at the
)
Were S5R2 units then sent out only to those individuals who read that post?
Are fora read by all users?
RE: Einstein@Home has a
)
I never once saw it listed Akos... If you are correct, I will revise my strong opinion, but I can say that I personally never saw it...
RE: S5R2 is a beta product.
)
I haven't seen S5R2 being in test, to be honest, so yes, your anaolgy could be correct. Then again, the same thing happened for S5RI ... :-)
And the credit thing is explained: EAH was asking too much.
Since credits are now set server side, it doesn't matter much. Can you even compare it to S5R1 (and RI)?