. . It is a shame I am running Windows, I would love to see how well the Special Cuda 60 app performs on my GT730 (CC=3.5), even though I am planning on retiring it...

You could always build a Linux machine for it, the parts are cheap on eBay.

. . But then I would have to learn Linux.

Stephen

.

As soon as I (or anyone) has managed to isolate and fix the unroll bug, the special alpha will become available in Windows form. It's not now, only because the mass devastation of the project results that would occur if released. Fortunately have more time for digging from a couple of days ago, though not promising quick fixes. The pulsefinding is unfortunately the most complex part of these applications.

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

The world just got stranger....
Reverted to the state before doing "a", rebooted (twice - I made trypo the first time round and got some "really interesting" error messages), and I'm now seeing all three GPUs chugging away on Beta (I haven't had the courage yet to try your special app - I wanted to get the beast behaving itself on a "stock" application first.

---

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

Downloaded, and ready to install, but let's allow the beast settle down before I give it a serious "prod in the ribs" - probably tomorrow night (UK time)....

For those that get impatient for me reporting back on this machine it is this one: https://setiathome.berkeley.edu/show_host_detail.php?hostid=8161267

---

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

The world just got stranger....
Reverted to the state before doing "a", rebooted (twice - I made trypo the first time round and got some "really interesting" error messages), and I'm now seeing all three GPUs chugging away on Beta (I haven't had the courage yet to try your special app - I wanted to get the beast behaving itself on a "stock" application first.

Hmmm, OK.
I was just about to explain again why I Don't use the repository version of BOINC. I use the Berkeley version with the single BOINC folder in my Home folder. Everything just works using the Berkeley version in the Home folder and there are a few Hosts around using even the ancient 6.10 version of BOINC with the 10 series GPUs without any problems. As long as you're using a Ubuntu 14.04 based version of Linux the older Berkeley version of BOINC still works. Just don't try the Berkeley BOINC with 16.04. Yet another reason to say with 14.04 ;-)

Glad to hear it's working.

As soon as I (or anyone) has managed to isolate and fix the unroll bug, the special alpha will become available in Windows form. It's not now, only because the mass devastation of the project results that would occur if released. Fortunately have more time for digging from a couple of days ago, though not promising quick fixes. The pulsefinding is unfortunately the most complex part of these applications.

[Update:] Have located a race condition across unroll for best pulse. @TBar: have you any examples of non-best reportables out of whack (with unroll active) ?

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

Well, I'd say about half the time a Bad Pulse is reported the Best Pulse is also incorrect. You can see a couple examples above http://setiathome.berkeley.edu/forum_thread.php?id=80636&postid=1834778. It seems to be worse in OSX....if that's what you're asking ;-)

Well, I'd say about half the time a Bad Pulse is reported the Best Pulse is also incorrect. You can see a couple examples above http://setiathome.berkeley.edu/forum_thread.php?id=80636&postid=1834778. It seems to be worse in OSX....if that's what you're asking ;-)

Rephrasing... It's always either only the 'best pulse' that's bad, or that same bad best and an equivalently bad reportable right ? (actually scratch that, frequency will depend on unroll, will have to do some figuring)

[Edit:] Looking through those again, yeah the overflow one has no bests (fair enough) . Gives me a bit more ammo, thanks. Looks like a missing reduction step for unroll bests

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

If I recall correctly one time we saw just reverse:
BAD reported but correct best (for non-bugged case there were reported and best just the same).
(So, the main issue is reportable signal incorrect reporting, incorrect bests are of less importance).

---

SETI apps news
We're not gonna fight them. We're gonna transcend them.

Learning Linux isn't too bad, especially if you use one of the modern distros - I've just reconfigured one of my PCs into a Linux box using "Mint" and am now getting the beast to run as I want it. The actual install took less than half an hour, sits alongside the Windows installation which is still there as a fall-back if I need it (or any of the data therein).
The one thing I am having to think about is that only one of the GPUs is recognised by BOINC/S@H, and I do recall having a similar problem under Windows...

. . Hi Bob,

. . It is the prospect of needing to learn a while new system from the ground up that I find daunting.

. . I am still trying to understand the ins and outs of Windows without jumping in at the deep end :) with Linux.

Stephen

.

Great, but it didn't work :-(
Mint (Cinamon, 18) is happy in telling me I have three GPUs, two GTX970, and one 1080.
Prodding around I found, in one of the boinc-client directories a file called "coproc_info.xml", this file lists all three GPUs. I've set "use_all_gpus" to 1, that was the first thing I did. After trying (a) from the two options BOINC isn't detecting any of the GPUs - one step back :-(
So, I've tried re-installing the drivers (Nvidia v.367.57) I've now lost BOINC manager from the GUI - oh joy, and I had everything suspended while I tried the above - now to find the command lines I need to get back in control.
Ah, getting lots of "authorization failure -102" responses, hmm, I don't like that as it means the boinc user has lost his marbles somewhere along the road :-(

. . OK, now I definitely don't want to get involved with Linux :)

Stephen

.

As soon as I (or anyone) has managed to isolate and fix the unroll bug, the special alpha will become available in Windows form. It's not now, only because the mass devastation of the project results that would occur if released. Fortunately have more time for digging from a couple of days ago, though not promising quick fixes. The pulsefinding is unfortunately the most complex part of these applications.

. . Not that I have the foggiest about the unroll bug but I like the idea of a test version being available for windows. However long it takes it won't be any worse than waiting for this low profile 1050 ti that MSI touted. Nearly a month and not a peep since they posted it's existence.

Stephen

.

Is it not an old boinc 'feature' that only the first GPU is reported even though all the GPUs can be used?

(Easiest is if all the GPUs are the same...)


Aside: I've had multiple GPUs working on a system. Care was needed with the drivers and ensuring boinc was added to the "video" group.


Happy fast crunchin,
Martin

---

See new freedom: Mageia Linux
Take a look for yourself: Linux Format
The Future is what We all make IT (GPLv3)

If I recall correctly one time we saw just reverse:
BAD reported but correct best (for non-bugged case there were reported and best just the same).
(So, the main issue is reportable signal incorrect reporting, incorrect bests are of less importance).

At present, the race condition showing itself in code would appear to have a number of possible manifestations like that. That doesn't rule out more symptoms from the same, or another bug/race further along. Am probably going to have to reverse engineer what was done first though. I'll need to replicate/confirm without unroll being normal/correct, Vs with it inducing the weirdness.

With unroll, I'm seeing periods distributed across cores via the y grid dimension, which should be fine, so my feeling is there'll be another race deeper in for the result table, as there is with the best table.

[There should be unroll x bests + unroll x result tables to reduce as an extra step, but not seeing it... though eyes do need a rest]

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

After one day sucessful cruching I can't take the eyes of the machinestats.
https://setiathome.berkeley.edu/results.php?hostid=1931980
Very impressive what this small 750Ti is doing with all the units no matter if guppi or something else.
The inconclusiv seems to be coming from the wingmen. If not is the error rate nevertheless very low.

The RAC could be 3-4 times higher with the 750Ti.
Due to the higher power consumtion I reduced the runtime down to 18h per day.

---

Regards from nothern Germany
Roman

SETI@home classic workunits 207,059
SETI@home classic CPU time 1,251,095 hours

It seems that the special app (Cuda 6) performs very well.
This one against the 1060 6G
https://setiathome.berkeley.edu/workunit.php?wuid=2361128750

Against the GTX 780Ti
https://setiathome.berkeley.edu/workunit.php?wuid=2361013895

Do they crunch more parallel or performs the 750Ti that well?

---

Regards from nothern Germany
Roman

SETI@home classic workunits 207,059
SETI@home classic CPU time 1,251,095 hours

The Special App was designed to run the Non-VLAR Arecibo tasks very fast. The current tasks are Non-VLARS, so you're just seeing the App do what it was designed to do. The VLARs were almost ignored in the early builds that didn't use an unroll function. The unroll was added to run the VLARs better. When the VLARs return there won't be that much difference in the Apps. Except the older CUDA 50 App, which doesn't have the unroll function, will be Dog slow on the VLARs. The biggest speed difference is when running the Arecibo Shorties, a lot of time was spent designing the App to run the Shorties. Shame we don't see many Shorties anymore.
Speaking of Shorties, the Quick Overflow Arecibo tasks don't react very well in the Special App, so, if we get a large number of them again you will see a large list of Inconclusives. Fortunately most of them validate eventually, just a heads up.

Are this shorties?
https://setiathome.berkeley.edu/workunit.php?wuid=2361124696
https://setiathome.berkeley.edu/workunit.php?wuid=2361023315
https://setiathome.berkeley.edu/workunit.php?wuid=2360919373

They seems to be valid.
They are quite fast finished too. The cpu version and the openCL app needs much more time to finish.

---

Regards from nothern Germany
Roman

SETI@home classic workunits 207,059
SETI@home classic CPU time 1,251,095 hours

No, those are merely Overflows. Look at the Angle ranges;
WU true angle range is : 0.415008
WU true angle range is : 0.448246
...message -9 result_overflow

Shorties have an Angle range above 2.xxxxx
They usually finish in under 3 minutes on the 750Ti, except when they Overflow.
The Files from Jan 2016 contained a large number of Shorty Overflows, and there are a couple of those files loaded into the Splitters.
They will be back.

I hope that my 1080 and 970s manage to avoid them, but I bet they won't

---

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

After one day sucessful cruching I can't take the eyes of the machinestats.
https://setiathome.berkeley.edu/results.php?hostid=1931980
Very impressive what this small 750Ti is doing with all the units no matter if guppi or something else.
The inconclusiv seems to be coming from the wingmen. If not is the error rate nevertheless very low.

The RAC could be 3-4 times higher with the 750Ti.
Due to the higher power consumtion I reduced the runtime down to 18h per day.

. . They are very impressive times. They are level of performance ahead of my 950s. Almost at the level of a 1060 ...

Stephen

.