How can I get my hands on the CUDA 50 source code? I’m interested in CUDA programming and would like to see how it’s implemented within SETI.

Cheers
Mark

---

It's held in the SVN repository described at Porting and optimizing SETI@home, specifically in the branch

../branches/sah_v7_opt/Xbranch/client

But I'd advise you to consult with Jason_Gee about the current status, build systems, dependencies etc. - it's a permanent 'work in progress' (as evidenced by the way current _v8 code is held in a branch called _v7).

Thanks for the link Richard. I would never have guessed it was still called _v7.

---

Current status of the stock Xbranch Cuda sources (X41) in the svn there is relatively stable, with only minor patches/hotfixes made on an as needed basis. For Windows builds specifically, it's become probably the most difficult of the 3 main platforms to build for. That's due to multiple Cuda version dependant deprecations by combinations of Cuda version and Microsoft visual studio, that tend to complicate wide support base. (More information on which Cuda versions + Visual Studio Versions should be practical available on request. For Cuda 5.0 that'd be said Cuda Toolkit + Visual Studio 2010 recommended, 32 bit builds configured and recommended for that version on Windows for performance reasons)

In that light, and that contributed works to address newer hardware and the new Guppi work are running into structure/design limitations, initial X42 development was started from scratch a week or so ago, on my github. (Still at basic infrastructure stage, implementing a new cross-platform buildsystem and tools to support integration of new technologies that don't quite fit cleanly into the old complex regime). The point with the switch there, is redesign with everything learned going forward, with cross-platform in mind from the start.

Again, with Windows builds specifically, there is a potential further complication, in that the original boincapi application threading model and Cuda driver/runtime threading practices are in conflict, with also some similar though subtler C-Runtime change issues. You would need to either use standard boincapi and address some minor build issues piecemeal, and put up with some reliability issues, or apply some minor customisations to Boincapi/lib. That's not something constrained to Windows alone, as the issues manifest on my Linux and Mac builds, where I use vanilla libraries, from time to time in different ways, though less frequent.

---

"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.

Thanks for all the insight Jason.

It sounds like I’m probably biting off more than I can chew but life is short, if I don’t try I’ll never know. Heck, I might even learn something along the way.

Cheers
Mark

---

Thanks for all the insight Jason.

It sounds like I’m probably biting off more than I can chew but life is short, if I don’t try I’ll never know. Heck, I might even learn something along the way.

Cheers
Mark

Well it's pretty much how I started back in CPU-Only Lunatics code days. Dove in, asked for help, found a few bugs. Constant learning since then for sure, and everyone brings something a bit different to the table. Can't prescribe what you might get out of the endeavour, but certainly fun and addictive ;)

---

"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.

It sounds like some of you here understand what is going on (wrong) with GPU WU's.

Here is a typical one of mine.
http://setiathome.berkeley.edu/result.php?resultid=5091711249

On the one PC that has good GPU power.

Any insight would be helpful.
I am using BOINC 7.6.33, but this was happening on 7.6.22 as well.
I have updated the GPU software 2 times in the last 2 months and it is still having issues.

GPU's are Nvidea ver 368.81.
I had tried downgrading to a point where I didn't have as many failures, but that has no longer helped.

---

Crunch! Crunch! Crunch!

Any insight would be helpful.

I've got the same OS and the same video driver, and am running a GTX 750Ti along with my GTX 1070 and no issues other than the occasional DX12 related crash (dxgmms2.sys)

Other than issues with the power supply, the only other thing that comes to mind is what other programmes are running on the system?
Antivirus, Antimalware, Hardware monitoring? Software for other hardware on that system? 3rd party video card related software?

---

Grant
Darwin NT

AV is Avast. I run Malwarebytes. No hardware monitors. I have Spybot Search & Destroy, but it only runs when I initiate it.

Oh, a NVidia GTX 750TI & 550Ti

---

Crunch! Crunch! Crunch!

AV is Avast. I run Malwarebytes. No hardware monitors. I have Spybot Search & Destroy, but it only runs when I initiate it.

I would suggest setting all of those applications to leave the BOINC file & data directories alone.
I only run Windows Defender.

---

Grant
Darwin NT