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

---

Offically yes: http://setiweb.ssl.berkeley.edu/sah_status.html.
;-)

---

WARR - Wissenschaftliche Arbeitsgemeinschaft für Raketentechnik und Raumfahrt
(WARR - scientific working group for rocket technology and space travel)

Well it still states as pending?

Also can someone explain why i received these two WU's.

http://setiweb.ssl.berkeley.edu/workunit.php?wuid=3300713
http://setiweb.ssl.berkeley.edu/workunit.php?wuid=3300712

I don't want to reset, but it is pointless doing the one that has already got credited, and the other has been sent to 4 comps to crunch.

---

> Well it still states as pending?
>
> Also can someone explain why i received these two WU's.
>
> http://setiweb.ssl.berkeley.edu/workunit.php?wuid=3300713
> http://setiweb.ssl.berkeley.edu/workunit.php?wuid=3300712
>
> I don't want to reset, but it is pointless doing the one that has already got
> credited, and the other has been sent to 4 comps to crunch.
>
>

The 1st was sent to 3 users, but 2 of them missed deadline so 2 new "results" was made and sent out. One of them missing the deadline have later returned his result, but since you don't know if the 4th user currently crunching this wu will return it or not it's just to keep crunching.

The 2nd was again 2 users (actually the same) that missed their deadline, so sent out to two other users. Here one of the users missing deadline has now returned the result, while the other new user also has returned the result and wu validated. But as long as a wu is "active", meaning either a result still not "reported" or met deadline, is waited on by BOINC so you will get credit if you crunches correctly and returns before your deadline.

Thanks Ingleside (thumb up)

---

I've got a result with three "successful" results returned that's sitting as pending, too, but I've returned another one since then and gotten credit immediately.

Here's the pending one:
http://setiweb.ssl.berkeley.edu/workunit.php?wuid=3884831

And the next one that I returned:
http://setiweb.ssl.berkeley.edu/workunit.php?wuid=3884832

Makes no sense to me...

---

I was wondering the same thing. I currently have 56 results pending. This is my oldest.

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

---

> I was wondering the same thing. I currently have 56 results pending. This is
> my oldest.
>
> http://setiweb.ssl.berkeley.edu/workunit.php?wuid=823212

God only knows why things like this appear, could be waiting for validation.... could be stuck in limbo and forgotten, could need another valid result because 2 sent out never came back. Not enough documentation on the full journey of a single WU to make ny type of prediction why. Unless a project administrator comments?

New credits are flowing, seems faster than ever too. Maybe it will be validated soon, who knows.

---

> I've got a result with three "successful" results returned that's sitting as
> pending, too, but I've returned another one since then and gotten credit
> immediately.
>
> Here's the pending one:
> http://setiweb.ssl.berkeley.edu/workunit.php?wuid=3884831
>
> And the next one that I returned:
> http://setiweb.ssl.berkeley.edu/workunit.php?wuid=3884832
>
> Makes no sense to me...


3884832 has gotten credit... maybe you should post some more and they might go through validation quicker:-p

---

>
> 3884832 has gotten credit... maybe you should post some more and they might go
> through validation quicker:-p
>

3884832 was the one that I referred to earlier in my post that got credit instantly, while 3884831 was returned earlier and has yet to receive credit though having 3 successful returns...shoulda been more clear. I'm sure it will come in time. Things have been running pretty smoothly lately...

On a random side note: I had a result that was pending from late June where my comp had (obviously) returned it as an error, since it reported 0 seconds of proc time, but just this week its status changed and it was re-sent (much to the joy of those other two people waiting for credit since June, I'm sure). Mmmmm, DB maintenance...

---