On my account, there are 41 WUs listed as "Validation pending", and all are v7. Would it be correct to surmise that this group will never be validated and time out b/c v7 is in the history books? Or, will they timeout and be resent for validation?

On my account, there are 41 WUs listed as "Validation pending", and all are v7. Would it be correct to surmise that this group will never be validated and time out b/c v7 is in the history books? Or, will they timeout and be resent for validation?

While not new SETI@home v7 MB tasks may be created the ones currently out will still follow the process to be completed.
Currently for v7 MB we are looking at:
Results out in the field 959,603
Results returned and awaiting validation 1,086,421

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

They'll time out and be resent. Even after the next Lunatics installer is released, and more people move on to v8 processing, it will still contain applications compatible with v7 precisely to pick up these waifs and strays on re-release.

Thanks gents. I should have viewed the Server Status page.
I did find something odd though. On one of the Validation Pending WUs on my account, this one https://setiathome.berkeley.edu/workunit.php?wuid=1994343051 is listed as "In progress" on this host https://setiathome.berkeley.edu/show_host_detail.php?hostid=7575901. The odd part is that out of the 241 WUs listed as "In progress", virtually all of them were sent on 12/08/15. Is this the result of the host deselecting the running of v7?

Thanks gents. I should have viewed the Server Status page.
I did find something odd though. On one of the Validation Pending WUs on my account, this one https://setiathome.berkeley.edu/workunit.php?wuid=1994343051 is listed as "In progress" on this host https://setiathome.berkeley.edu/show_host_detail.php?hostid=7575901. The odd part is that out of the 241 WUs listed as "In progress", virtually all of them were sent on 12/08/15. Is this the result of the host deselecting the running of v7?

It is more likely that since the v8 app is new the estimated run times would be very high. Which will cause BOINC to process them first. As it thinks there isn't enough time to get them done before their deadline. Once that host has a good estimated completion time or finishes all of its v8 tasks it should get back to running FIFO and push out all of the v7 tasks.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

That sort of thing happens every now and then. It may be that there was a server glitch just as the tasks were on their way and have never reached the client resulting in a large number of "ghosts".

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

With just over 1,018,000 results out in the field by my calculations there is currently 128,997 results that need to be recent at some point. I will do my best to get some resends on my 970 GPU

---

Resends are good.

---

Resends are good.

Yes for 2 reasons wonder we are helping clean out the database and 2 we get credit quicker. I am completely aware it is not all about the credit it is about the science.

Edit = while I was writing I picked up one resend. It had been out in the field since November all returned and credited

---

Wait a minute. I've always had CPU tasks running on SETI because the system could never keep my systems supplied with GPU units. Are you saying the hundreds of hours of CPU processing time my files are showing as "Pending" are basically worthless and are just simply going to be redistributed?

WTF CHUCK!

Wait a minute. I've always had CPU tasks running on SETI because the system could never keep my systems supplied with GPU units. Are you saying the hundreds of hours of CPU processing time my files are showing as "Pending" are basically worthless and are just simply going to be redistributed?

WTF CHUCK!

Not worthless, my friend.
May take a LONG time to come back, but eventually all v7 wus should be validated.
There shall be many out in the field for months to come, so don't wait for the impending validations to arrive.
I am in WU hell right now, as almost all of the v7 tasks I have remaining are CPU tasks.........including APs, and they take a LONNNNNNNNNNNNNNNNNNNNNG time to do on a CPU.

No worries. GPU apps are coming soon, and then things shall start to slide upwards.

v8 vrooooooooooooooooooooooom say the kitties.

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

I have 8 v8 tasks in validation pending on my Linux laptop, not a fast machine, plus two with validation inconclusive on a Linux guest on the Windows 10 host.with one still processing. Of the two v7 tasks, one was aborted on the Windows 10, it took too much time, and the other is pending on a Linux host. 9 pending on a total of 14, all CPU.
Tullio

---

I hope you're correct. As I said, this program has never been able to keep my GPUs busy, so I've always run CPU tasks to keep my multiple, multi-core CPU systems busy, and the stuff that has been showing as pending is now getting quite old, and represents hundreds of CPU hours. I would be highly disappointed to find out that work was all for not.

I've always had CPU tasks running on SETI because the system could never keep my systems supplied with GPU units.

Other than a few system outages & the weekly outages others haven't had any issues keeping their GPUs busy with Seti work.

---

Grant
Darwin NT

I've always had CPU tasks running on SETI because the system could never keep my systems supplied with GPU units.

Other than a few system outages & the weekly outages others haven't had any issues keeping their GPUs busy with Seti work.

Yep, until the seti V8 app changeover they've kept my GPU's fed 99% of the time.

But ATM those GPU's are doing a backup project of mine for the mean time until an optimized installer is released (I can wait). ;-)

Cheers.

I hope you're correct. As I said, this program has never been able to keep my GPUs busy, so I've always run CPU tasks to keep my multiple, multi-core CPU systems busy, and the stuff that has been showing as pending is now getting quite old, and represents hundreds of CPU hours. I would be highly disappointed to find out that work was all for not.

I've estimated the total run time for the 17-odd SETI@home v7 tasks on your three machines that are either pending or inconclusive, and it comes to about 12 hours of computing time.

They will eventually be validated, but it could take many weeks, months even, for the last few to be processed and cleared. (SETI@home v6 took from 24 July to 7 December 2013 to decrease from 16,903 to 0 outstanding results. The last 1,000 results took from 31 August 2013 to clear.)

---

I hope you're correct. As I said, this program has never been able to keep my GPUs busy, so I've always run CPU tasks to keep my multiple, multi-core CPU systems busy, and the stuff that has been showing as pending is now getting quite old, and represents hundreds of CPU hours. I would be highly disappointed to find out that work was all for not.

I've estimated the total run time for the 17-odd SETI@home v7 tasks on your three machines that are either pending or inconclusive, and it comes to about 12 hours of computing time.

They will eventually be validated, but it could take many weeks, months even, for the last few to be processed and cleared. (SETI@home v6 took from 24 July to 7 December 2013 to decrease from 16,903 to 0 outstanding results. The last 1,000 results took from 31 August 2013 to clear.)

They seem to be complaining only about their pending v7 CPU tasks. The run time for their 5 pending CPU tasks do add up.... to exactly 39173.94 seconds or about 10.88 hours.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[