Changeset 711f17e in sasmodels for doc/ref/gpu

Timestamp:

Oct 8, 2016 11:44:56 AM (8 years ago)

Author:

smk78

Branches:

master, core_shell_microgels, costrafo411, magnetic_model, ticket-1257-vesicle-product, ticket_1156, ticket_1265_superball, ticket_822_more_unit_tests

Children:

ec8b9a3

Parents:

066f296

Message:

Tweaks to text. Operation of python shell device test verified. Refs
#734

File:

• doc/ref/gpu/gpu_computations.rst (modified) (4 diffs)

doc/ref/gpu/gpu_computations.rst

@@ -8 +8 @@
 
 To run on the GPU, your computer must have OpenCL drivers installed.
-For information about OpenCL installation see the
-:ref:`opencl-installation` documentation
+For information about OpenCL installation see this
+:ref:`opencl-installation` guidance.
 
 Where the model is evaluated is a little bit complicated.
@@ -16 +16 @@
 on the CPU.  If the OpenCL driver is not available for the CPU then
 it will run as a normal program on the CPU.
+
 For models with a large number of parameters or with a lot of code,
 the GPU may be too small to run the program effectively.
 In this case, you should try simplifying the model, maybe breaking it
-into several different models so that you don't need if statements in your code.
+into several different modules so that you don't need *IF* statements in your code.
 If it is still too big, you can set *opencl=False* in the model file and
 the model will only run as a normal program on the CPU.
 This will not usually be necessary.
 
+Device Selection
+................
 If you have multiple GPU devices you can tell SasView which device to use.
 By default, SasView looks for one GPU and one CPU device
 from available OpenCL platforms.
 
-It prefers AMD or NVIDIA drivers for GPU, and prefers Intel or
-Apple drivers for CPU.
-Both GPU and CPU are included on the assumption that CPU is always available
-and supports double precision.
+SasView prefers AMD or NVIDIA drivers for GPU, and prefers Intel or
+Apple drivers for CPU. Both GPU and CPU are included on the assumption that CPU 
+is always available and supports double precision.
 
 The device order is important: GPU is checked before CPU on the assumption that
 it will be faster. By examining ~/sasview.log you can see which device SasView
 chose to run the model.
+
 If you don't want to use OpenCL, you can set *SAS_OPENCL=None*
 in the environment, and it will only use normal programs.
+
 If you want to use one of the other devices, you can run the following
 from the python console in SasView::
@@ -48 +52 @@
 Use that value as the value of *SAS_OPENCL*.
 
+Compiler Selection
+..................
 For models run as normal programs, you may need to specify a compiler.
 This is done using the SAS_COMPILER environment variable.
@@ -54 +60 @@
 TinyCC is provided with SasView so that is the default.
 If you want one of the other compilers, be sure to have it available
-on the path so SasView can find it.
+in your *PATH* so SasView can find it!
+
+
+.. note::
+    This help document was last changed by Steve King, 08Oct2016