Differences between revisions 12 and 13
Deletions are marked like this. Additions are marked like this.
Line 10: Line 10:

== Development Notes ==

 * [[mrisurf_CUDA|mrisurf and CUDA]]

CUDA Developers Guide

This is the root of the CUDA developing documentation. Everything should go underneath here. For instance if one wants to add a CUDATesting page, it should go in http://surfer.nmr.mgh.harvard.edu/fswiki/CUDADevelopersGuide/CUDATesting and a link to that page should be pointed from here.

Enabling CUDA in the Build Environment

CUDAEnabling page gives one an idea of what tweaks have been done in the build environment and what tweaks one should make to add their CUDA enabled binary to the build environment

Development Notes

Running within recon-all

The convention for running CUDA-enabled executables within recon-all is the following. Firstly, it was decided that rather than create a single executable with a --use-cuda switch, instead, a separate executable with the post-fix _cuda is to be created, ie. mri_em_register_cuda (paired with mri_em_register). The recon-all script will itself accept a -use-cuda switch, which will then run the cuda-enabled executable over the default (ie mri_em_register_cuda instead of mri_em_register).

Refer to CUDAEnabling, particularly the Makefile.am example. The cuda-enabled executables in-the-works include:

  • mri_em_register_cuda
  • mri_ca_register_cuda
  • mris_sphere_cuda
  • mris_inflate_cuda
  • mris_flatten_cuda

HPC w/ CUDA Tutorials

NVidia's HPC w/ CUDA Tutorials

CUDADevelopersGuide (last edited 2012-04-09 10:34:24 by NickSchmansky)