Changeset 59485a4 in sasmodels for doc/guide/gpu_setup.rst


Ignore:
Timestamp:
Sep 28, 2017 2:38:48 PM (7 years ago)
Author:
Paul Kienzle <pkienzle@…>
Branches:
master, core_shell_microgels, costrafo411, magnetic_model, ticket-1257-vesicle-product, ticket_1156, ticket_1265_superball, ticket_822_more_unit_tests
Children:
505d0ad
Parents:
3048ec6
Message:

doc tweaks

File:
1 edited

Legend:

Unmodified
Added
Removed
  • doc/guide/gpu_setup.rst

    rc0d7ab3 r59485a4  
    44GPU Setup 
    55******************** 
     6 
     7SAS model evaluations can run on your graphics card (GPU) or they can run 
     8on the processor (CPU). In general, calculations performed on the GPU 
     9will run faster. 
     10 
    611 
    712OpenCL Installation 
     
    7479************* 
    7580 
    76 SAS model evaluations can run on your graphics card (GPU) or they can run 
    77 on the processor (CPU). In general, calculations performed on the GPU will run faster. 
    78  
    79 To run on the GPU, your computer must have OpenCL drivers installed. 
    80 For information about OpenCL installation see this 
    81 :ref:`opencl-installation` guidance. 
    82  
    83 Where the model is evaluated is a little bit complicated. 
     81The logic for choosing the compute platform is a little bit complicated. 
    8482If the model has the line *single=False* then it requires double precision. 
    8583If the GPU is single precision only, then it will try running via OpenCL 
     
    8886 
    8987For models with a large number of parameters or with a lot of code, 
    90 the GPU may be too small to run the program effectively. 
    91 In this case, you should try simplifying the model, maybe breaking it 
    92 into several different modules so that you don't need *IF* statements in your code. 
    93 If it is still too big, you can set *opencl=False* in the model file and 
    94 the model will only run as a normal program on the CPU. 
    95 This will not usually be necessary. 
     88the GPU may be too small to run the program effectively. In this case, you 
     89should try simplifying the model, maybe breaking it into several different 
     90models so that you don't need *IF* statements in your code. If it is still 
     91too big, you can set *opencl=False* in the model file and the model will 
     92only run as a normal program on the CPU. This will not usually be necessary. 
    9693 
    9794Device Selection 
Note: See TracChangeset for help on using the changeset viewer.