The Top GPU models list has been fixed already.

Thanks to Joe for preventing me making a fool of myself by reporting the Beta status page again...

Any new AP's before tomorrows outage?
Yes or No? :-)

Take a guess.

I asked my magic 8 ball.

---

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

Any new AP's before tomorrows outage?
Yes or No? :-)

Take a guess.

The right guess, would have been YES, since new AP WU's are being split now.

Very new. 02se14aa, less than six weeks since recording.

http://setiweb.ssl.berkeley.edu/beta/server_status.php is the fixed version, and it is linked from the front page at SETI Beta. I also had a local bookmark to the old page and had to edit it after others said the status had been fixed.

There is still one minor problem at Beta, at least for me using non-US regional settings but using English as language:

Notice: Undefined variable: PROJECT in /disks/carolyn/b/home/boincadm/projects/beta/html/languages/compiled/pl.po.inc on line 216

I got rid of this message in Seti@Home by switching language EN -> FI -> EN but somehow I don't see that option in S@H Beta... Or mayby I'm just blind? :)

---

"Please keep Your signature under four lines so Internet traffic doesn't go up too much"

- In 1992 when I had my first e-mail address -

Any new AP's before tomorrows outage?
Yes or No? :-)

Take a guess.

The right guess, would have been YES, since new AP WU's are being split now.

Very new. 02se14aa, less than six weeks since recording.

Wow, that's almost like picking up ET's call on the first ring. :^)

Well, I have an AP from the 23rd that's still waiting for the validator to notice that 2 hosts have completed it, but that's a special case, due to a validation black hole that seemed to develop between about 23:41 and 23:51 UTC on the 23rd. I've also got 99 MB tasks in limbo from that same window. I reported the situation in several posts in the earlier Panic Mode (89) thread, but nobody else (other than my wingmen on those tasks) seemed to get caught up in it (or perhaps nobody else has noticed yet).

At least the current AP validation issue that everyone's so concerned about seems to be more about the validator just limping along, or starting and stopping, but at least still slowly getting the job done, rather than having a whole bunch of WUs missing the validation queue altogether. I'm just keeping my fingers crossed that Richard's right about those WUs getting another chance at validation as their original deadlines come due over the next several weeks.

Just a quick update to my AP validation issue from September 23. It appears that Richard was correct (no surprise there) about the validator taking another look at tasks that it missed the first time around, when the original deadline is reached. I had 42 MB shorties from that September 23 black hole finally validate successfully last night, when they hit their deadlines. Only 57 more MBs (most not due until November) and one AP to go!

Onwards to celebrating my first Ap V7, woohoo!!

---

rOZZ
Music
Pictures

There is still one minor problem at Beta, at least for me using non-US regional settings but using English as language:

Notice: Undefined variable: PROJECT in /disks/carolyn/b/home/boincadm/projects/beta/html/languages/compiled/pl.po.inc on line 216

I got rid of this message in Seti@Home by switching language EN -> FI -> EN but somehow I don't see that option in S@H Beta... Or mayby I'm just blind? :)

Just mix Main and Beta URLs a bit :)

http://setiweb.ssl.berkeley.edu/beta/language_select.php

edit: Maybe the project needs to recompile the translations to really get rid of that message.

edit edit: Nope, it's the Polish translation that needs updating. (It shouldn't have the $PROJECT in it.)

Well.. I've just started my offline testing of the two CPU apps for APv7.. x86_AVX and x64_SSE3. Seeing as the same WU was just finished by r557 AVX and reported, I now have a time to compare it to. 5.87% blanking on that WU. I guess one with zero blanking should have been used, but I'm still interested to see which version finishes faster on my CPU. I'll find out in 11-12 hours (or more, maybe).

Annnnd.. done.

Results:

r557 AVX SSE2: 39,734 seconds
r2692 x86 AVX: 34,558 seconds
r2692 x64 SSE3: 34,417 seconds

All with the same WU that had 5.86% blanking with 3 singles and 1 repeating pulse. So it looks like there isn't really a difference between the two, but I'm still going with x64 SSE3.

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

Well.. I've just started my offline testing of the two CPU apps for APv7.. x86_AVX and x64_SSE3. Seeing as the same WU was just finished by r557 AVX and reported, I now have a time to compare it to. 5.87% blanking on that WU. I guess one with zero blanking should have been used, but I'm still interested to see which version finishes faster on my CPU. I'll find out in 11-12 hours (or more, maybe).

Annnnd.. done.

Results:

r557 AVX SSE2: 39,734 seconds
r2692 x86 AVX: 34,558 seconds
r2692 x64 SSE3: 34,417 seconds

All with the same WU that had 5.86% blanking with 3 singles and 1 repeating pulse. So it looks like there isn't really a difference between the two, but I'm still going with x64 SSE3.

No data for the x64 AVX?

---

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

Annnnd.. done.

Results:

r557 AVX SSE2: 39,734 seconds
r2692 x86 AVX: 34,558 seconds
r2692 x64 SSE3: 34,417 seconds

All with the same WU that had 5.86% blanking with 3 singles and 1 repeating pulse. So it looks like there isn't really a difference between the two, but I'm still going with x64 SSE3.

What about x64 AVX?

Claggy

I...was not aware there was an x64 AVX. I grabbed what I saw on arkayn's page a few days ago.

But I've gotten some new v7's assigned. Woohoo.. initial estimate of 217 hours, when the offline test was about 9.5 hours. That'll be fun watching minutes shave off of that ETA every second.

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

The AP splitters doesn't fire on all cylinders. Too many:

SETI@home 2014-10-13 23:30 Requesting new tasks for GPU
SETI@home 2014-10-13 23:30 Scheduler request completed: got 0 new tasks

Sorry I got to them before you.
10/13/2014 17:20:59 SETI@home Requesting new tasks for CPU and ATI
10/13/2014 17:21:02 SETI@home Scheduler request completed: got 10 new tasks

---

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

The AP splitters doesn't fire on all cylinders. Too many:

SETI@home 2014-10-13 23:30 Requesting new tasks for GPU
SETI@home 2014-10-13 23:30 Scheduler request completed: got 0 new tasks

I also saw "No tasks are available for Astropulse v7" for 10 requests during the 12:26 to 13:31 UTC period. But then at 13:39 I got one and 303 seconds later another. I suspect the splitters may have been wedged and were given a kick.

OTOH, it could have been the suction of many GPUs ;-)

                                                                   Joe

The AP splitters doesn't fire on all cylinders. Too many:

SETI@home 2014-10-13 23:30 Requesting new tasks for GPU
SETI@home 2014-10-13 23:30 Scheduler request completed: got 0 new tasks

I also saw "No tasks are available for Astropulse v7" for 10 requests during the 12:26 to 13:31 UTC period. But then at 13:39 I got one and 303 seconds later another. I suspect the splitters may have been wedged and were given a kick.

OTOH, it could have been the suction of many GPUs ;-)

                                                                   Joe

Of course it could have been the "Astropulse doubters" I have never crunched AP on main, yet with AP v7 I have decided to take the plunge and will be allowing all my machines to crunch AP. Even got 4 overnight!!

---

It's been awhile, but have we got another stuck MB tape? MB splitters have been struggling for about 24 hours now.

---

Grant
Darwin NT

Looking through the last of the AP v6 re-sends (_2 +) that I have, I got quite a few that were aborted by somebody with a 750ti.

host 7361304

At least they had the decency to abort to purge their queue instead of just leaving them in time-out limbo.

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

We are back after a long one

---

About 6 hours I think...

---

rOZZ
Music
Pictures

About 6 hours I think...

websites are up, but servers aren't responding to update calls, so can't report completed tasks, or d/l new tasks..

P.

---