I wonder why almost 2/3 of my WUs get not validated even though some have got 3 succsessful returns...

Any idea and are these credits lost?

Kind regards,
CC

---

No, credits won't be lost. A couple of the units I checked in your list had "checked - but no consensus yet" as the message. That may have to do with the validators being a bit stressed at this time over at Seti proper. (this project runs through the same servers there)

But it may have to do with computers asking consistently low credits, not in the range the others ask. Or that the consensus here is at least 5 units with about the same credit. Or something else.

I hope I don't have to explain you're on a beta project, so that you shouldn't pin yourself on getting credits? ;)

---

I hope I don't have to explain you're on a beta project, so that you shouldn't pin yourself on getting credits? ;)

Careful! Last time I mentioned that, I got yelled at. :D

No, credits won't be lost. A couple of the units I checked in your list had "checked - but no consensus yet" as the message. That may have to do with the validators being a bit stressed at this time over at Seti proper. (this project runs through the same servers there)

But it may have to do with computers asking consistently low credits, not in the range the others ask. Or that the consensus here is at least 5 units with about the same credit. Or something else.

I hope I don't have to explain you're on a beta project, so that you shouldn't pin yourself on getting credits? ;)

"Checked - but no consensus yet" means there's enough "success"-results and have been tried validated, but the results was too different from eachother so didn't pass validation. In this case the system will either wait on any currently active results to be reported, or generate another result and send out. Well, if too many "success"-results but still fails validation, the wu will error-out...

Not sure if they uses the exact same validator, but atleast in the public project the validator doesn't care whatever your claimed credits are before after results is validated, it's only looking on the signals.


Being a beta-project, some wu is cancelled and bugs can mean many wu isn't passing validation.

Careful! Last time I mentioned that, I got yelled at. :D

No correlation. We just yell at you on principal. ;)

---

Just take a look at our results list. What the hell is going on here? I don't see what the hell I'm wasting cycles for here. Maybe somebody could tell me what's actually going on here and what if anything is being accomplished? As a BETA participant it would be nice to know what our donation of time etc. is actually doing. I'll keep helping out but what am I helping out for?

---

Sed quis custodiet ipsos Custodes?

I wonder why almost 2/3 of my WUs get not validated even though some have got 3 succsessful returns...

Any idea and are these credits lost?

Kind regards,
CC

All but your last 2 WU's have been canceled. Same for just about every WU I looked at that was sent out before 8-9 July(but they may just be getting started). I am GUESSING this all has to do with the different apps. There was a bug in 4.00/4.11-opt app that was fixed and then these same WU's were released at 4.02/4.02-opt and the two apps did not validate against each other. Also, many people continued to use the 4.11-opt on 4.02 and they will not validate. 4.03 was out briefly then pulled.

Now we have 4.04 which is compatible with 4.02-opt but again there are still 4.11-opt out there. Some of the older WU's were still being sent out because they did not have a quorum yet, but would never validate anyway with the new app. Of course this is just me speculating, and I could be wrong-except for the part about WU's being canceled-they have been.

---

Credits? I don't care.... I've got a slow puter I just try to help out any projects... I've got like 4 WUs returned that are pending... but then under Errors: it shows Cancelled... I figure they don't need the WU or what was being checked for was found and don't need the WU either...

http://setiweb.ssl.berkeley.edu/beta/workunit.php?wuid=99208

--

Here on this WU it was made 10 times, 9 were sent out, and 2 were successful the rest either errored out or client errors ..etc.. and that one was Cancelled without credit...

http://setiweb.ssl.berkeley.edu/beta/workunit.php?wuid=48934

So the validator is working / not working so what... as long as the little I do helps I don't care when/if I get credit.... that's what Alpha/Beta means... you test to find out problems... besides I don't think the credit will carry forward to when this moves to public, if it does great.. if not... fine no loss to me I could stay at the bottom of then long list of Top Users for the entire project and its no skin off my teeth.

* just My two cent soapbox worth *

---

Mark

Credits? I don't care....

... as long as the little I do helps I don't care when/if I get credit.... that's what Alpha/Beta means... you test to find out problems... besides I don't think the credit will carry forward to when this moves to public, if it does great.. if not... fine no loss to me I could stay at the bottom of then long list of Top Users for the entire project and its no skin off my teeth.

* just My two cent soapbox worth *

Agreed, if you are doing alpha/beta and are too concerned about credit, you are in the wrong project.

---

It would help though to have the quota penalty removed.
Each time I reset here, one or more files will be reset as well, them timing out to past their deadline, which will put me back to a quota of 1/day. That won't go up until I turn in another unit, and with these things being so long in crunching (20 hours+), it's never a nice message to see that "quota for the day reached".

Heck, I've finally clawed myself back up to 2 units/day. That will go down again twice in a row because of missing units on the 23rd and 25th.

So when we then get an app that is crunching fast, or a unit that is crunching faster than these, I'm stuck at 1 a day. Not much testing going on then.

---

I'd be impressed if you could complete more than 2 WU's a day anyway! :)
You could always roll back to an earlier standard release core client version that doesn't have the WU quota bug.

---

It's not the client that is imposing the quota. It's resetting a project, thereby dumping workunits which stay in the list and eventually time out (deadline reached). Due to a bug in the server software, the quota isn't deducted by one unit for every unit failed to crunch before the deadline, but is set to one no matter what.

So in the old days, you'd start with a quota of 100/day. (I just checked you, David. You're at 500/day)
Not reach the deadline for 3 units meant you had a quota of 97/day. (497)
Now you are immediately at 1/day. (1)

Capice? ;)

---

Ah, I'd only heard people running development version 4.7x report this bug so far. I assumed it was releated to the core client. That's an ugly bug that should demand a pretty high priority then. :(

---

A couple of people running 4.45 reported the same thing happening to them. So be a good boy and always eat your vege... err crunch your units. ;)

---

No correlation. We just yell at you on principal. ;)

Ah, good. :)

Ah, I'd only heard people running development version 4.7x report this bug so far. I assumed it was releated to the core client. That's an ugly bug that should demand a pretty high priority then. :(

I just saw on Seti proper that they have it fixed there. So maybe, hopefully, it is fixed here as well. :)

---

News
July 26, 2005
In case you were wondering, yes, you will be getting credit for all those results you sent that got an error or failed to validate.

I read this news but still most of my WU credits are pending...
So what's up with this??

Greetings,
CC

---

Us around here on a beta program don't care much about woos (pron. of WUs). Are you? ;)

---

Are you? ;)

I would have to assume the answer is yes, hence his/her posting about it. ;)

Heaps of mine are doing this too.
Usually due to excess loss of heartbeats

---

Join BOINC Synergy