- Timestamp:
- May 16, 2017 9:59:55 AM (8 years ago)
- Branches:
- master, core_shell_microgels, costrafo411, magnetic_model, ticket-1257-vesicle-product, ticket_1156, ticket_1265_superball, ticket_822_more_unit_tests
- Children:
- b52e00f
- Parents:
- 2e66ef5 (diff), ba62072 (diff)
Note: this is a merge changeset, the changes displayed below correspond to the merge itself.
Use the (diff) links above to see all the changes relative to each parent. - Location:
- doc/guide
- Files:
-
- 12 added
- 1 edited
- 10 moved
Legend:
- Unmodified
- Added
- Removed
-
doc/guide/gpu/gpu_computations.rst
r3f5a566 r8ae8532 4 4 GPU Computations 5 5 **************** 6 SasView modelevaluations can run on your graphics card (GPU) or they can run6 sasmodels evaluations can run on your graphics card (GPU) or they can run 7 7 on the processor (CPU). In general, calculations performed on the GPU will run faster. 8 8 … … 32 32 33 33 SasView prefers AMD or NVIDIA drivers for GPU, and prefers Intel or 34 Apple drivers for CPU. Both GPU and CPU are included on the assumption that CPU 34 Apple drivers for CPU. Both GPU and CPU are included on the assumption that CPU 35 35 is always available and supports double precision. 36 36 … … 63 63 64 64 65 .. note:: 66 This help document was last changed by Steve King, 08Oct2016 65 *Document History* 66 67 | 2016-10-08 Steve King 68 | 2017-05-07 Paul Kienzle -
doc/guide/gpu/opencl_installation.rst
rec8b9a3 r990d8df 4 4 OpenCL Installation 5 5 ******************* 6 *Warning! GPU devices do not in general offer the same level of memory protection as CPU devices. If your code attempts to write outside allocated memory buffers unpredicatable behaviour may result (eg, your video display may freeze, or your system may crash, etc). Do not install OpenCL drivers without first checking for known issues (eg, some computer manufacturers install modified graphics drivers so replacing these may not be a good idea!). If in doubt, seek advice from an IT professional before proceeding further.* 6 *Warning! GPU devices do not in general offer the same level of memory 7 protection as CPU devices. If your code attempts to write outside allocated 8 memory buffers unpredicatable behaviour may result (eg, your video display 9 may freeze, or your system may crash, etc). Do not install OpenCL drivers 10 ithout first checking for known issues (eg, some computer manufacturers 11 install modified graphics drivers so replacing these may not be a good 12 idea!). If in doubt, seek advice from an IT professional before proceeding 13 further.* 7 14 8 15 1. Check if you have OpenCL already installed … … 25 32 Mac OSX 26 33 ....... 27 For OS X operating systems higher than 10.6 OpenCL is shipped along with the system. 34 For OS X operating systems higher than 10.6 OpenCL is shipped along with 35 the system. 28 36 29 However, OpenCL has had a rocky history on Macs. Apple provide a useful compatibility table at https://support.apple.com/en-us/HT202823 37 However, OpenCL has had a rocky history on Macs. Apple provide a useful 38 compatibility table at https://support.apple.com/en-us/HT202823 30 39 31 40 … … 44 53 ....... 45 54 N/A 46 47 You cannot download OpenCL driver updates for your Mac. They are packaged with the normal quarterly OS X updates from Apple. 55 56 You cannot download OpenCL driver updates for your Mac. They are packaged 57 with the normal quarterly OS X updates from Apple. 48 58 49 59 50 60 .. note:: 51 Intel provides OpenCL drivers for Intel processors at https://software.intel.com/en-us/articles/opencl-drivers 61 Intel provides OpenCL drivers for Intel processors at 62 https://software.intel.com/en-us/articles/opencl-drivers 52 63 These can sometimes make use of special vector instructions across multiple 53 64 processors, so it is worth installing if the GPU does not support double … … 55 66 or AMD. 56 67 57 68 58 69 .. note:: 59 70 This help document was last changed by Steve King, 08Oct2016 -
doc/guide/index.rst
rbb6f0f3 r2e66ef5 1 ********** 2 SAS Models 3 ********** 1 **************** 2 SAS Models Guide 3 **************** 4 4 5 Small angle X-ray and Neutron (SAXS and SANS) scattering examines the 6 scattering patterns produced by a beam travelling through the sample 7 and scattering at low angles. The scattering is computed as a function 8 of $q_x$ and $q_y$, which for a given beam wavelength corresponds to 9 particular scattering angles. Each pixel on the detector corresponds to 10 a different scattering angle. If the sample is unoriented, the scattering 11 pattern will appear as rings on the detector. In this case, a circular 12 average can be taken with 1-dimension data at $q = \surd (q_x^2 + q_y^2)$ 13 compared to the orientationally averaged SAS scattering pattern. 5 .. toctree:: 6 :numbered: 4 7 :maxdepth: 4 14 8 15 Models have certain features in common. 16 17 Every model has a *scale* and a *background*. 18 19 Talk about orientation, with diagrams for orientation so that we don't need 20 a link on every model page? 21 22 .. _orientation: 23 24 .. figure: img/orientation1.jpg 25 26 Orientation in 3D 27 28 .. figure: img/orientation2.jpg 29 30 Orientation cross sections 31 32 Talk about polydispersity. 33 34 Talk about magnetism, converting the magnetism help file to inline text here, 35 with links so that models can point back to it. 36 37 Need to talk about structure factors even though we don't have any 38 implemented yet. 9 intro.rst 10 install.rst 11 pd/polydispersity.rst 12 resolution.rst 13 magnetism/magnetism.rst 14 sesans/sans_to_sesans.rst 15 sesans/sesans_fitting.rst 16 plugin.rst 17 scripting.rst 18 refs.rst -
doc/guide/magnetism/magnetism.rst
rdeb854f r990d8df 2 2 3 3 Polarisation/Magnetic Scattering 4 ================================ =======================4 ================================ 5 5 6 In earlier versions of SasView magnetic scattering was implemented in just five 7 (2D) models 8 9 * :ref:`sphere` 10 * :ref:`core-shell-sphere` 11 * :ref:`core-multi-shell` 12 * :ref:`cylinder` 13 * :ref:`parallelepiped` 14 15 From SasView 4.x it is implemented on most models in the 'shape' category. 16 17 In general, the scattering length density (SLD = $\beta$) in each region where the 18 SLD is uniform, is a combination of the nuclear and magnetic SLDs and, for polarised 19 neutrons, also depends on the spin states of the neutrons. 6 Models which define a scattering length density parameter can be evaluated 7 as magnetic models. In general, the scattering length density (SLD = 8 $\beta$) in each region where the SLD is uniform, is a combination of the 9 nuclear and magnetic SLDs and, for polarised neutrons, also depends on the 10 spin states of the neutrons. 20 11 21 12 For magnetic scattering, only the magnetization component $\mathbf{M_\perp}$ … … 98 89 .. note:: 99 90 This help document was last changed by Steve King, 02May2015 91 92 * Document History * 93 94 | 2017-05-08 Paul Kienzle -
doc/guide/sesans/sesans_fitting.rst
r3330bb4 r8ae8532 7 7 =================== 8 8 9 .. note:: A proper installation of the developers setup of SasView (http://trac.sasview.org/wiki/AnacondaSetup) is a prerequisite for using these instructions. 9 .. note:: 10 11 A proper installation of the developers setup of SasView 12 (http://trac.sasview.org/wiki/AnacondaSetup) is a prerequisite for 13 using these instructions. 10 14 11 15 It is possible to fit SESANS measurements from the command line in Python. … … 13 17 Simple Fits 14 18 ........... 15 In the folder sasmodels/example the file sesans_sphere_2micron.py gives an example of how to fit a shape to a measurement. 19 In the folder sasmodels/example the file sesans_sphere_2micron.py gives 20 an example of how to fit a shape to a measurement. 16 21 17 22 The command:: … … 23 28 .. image:: sesans_img/SphereLineFitSasView.png 24 29 25 All the parameters and names in sesans_sphere_2micron.py (shown below) can be adjusted to fit your own problem:: 30 All the parameters and names in sesans_sphere_2micron.py (shown below) can 31 be adjusted to fit your own problem:: 26 32 27 33 """ … … 64 70 # Constraints 65 71 # model.param_name = f(other params) 66 # EXAMPLE: model.scale = model.radius*model.radius*(1 - phi) - where radius and scale are model functions and phi is67 # a custom parameter72 # EXAMPLE: model.scale = model.radius*model.radius*(1 - phi) - where radius 73 # and scale are model functions and phi is a custom parameter 68 74 model.scale = phi*(1-phi) 69 75 … … 74 80 Incorporating a Structure Factor 75 81 ................................ 76 An example of how to also include a structure factor can be seen in the following example taken from Washington et al., 77 *Soft Matter*\, (2014), 10, 3016 (dx.doi.org/10.1039/C3SM53027B). These are time-of-flight measurements, which is the 78 reason that not the polarisation is plotted, but the :math:`\frac{log(P/P_0)}{\lambda^2}` . The sample is a dispersion 79 of core-shell colloids at a high volume fraction with hard sphere interactions. 82 An example of how to also include a structure factor can be seen in the 83 following example taken from Washington et al., *Soft Matter*\, (2014), 10, 3016 84 (dx.doi.org/10.1039/C3SM53027B). These are time-of-flight measurements, which 85 is the reason that not the polarisation is plotted, but the 86 :math:`\frac{log(P/P_0)}{\lambda^2}` . The sample is a dispersion of 87 core-shell colloids at a high volume fraction with hard sphere interactions. 80 88 81 89 The fit can be started by:: … … 87 95 .. image:: sesans_img/HardSphereLineFitSasView.png 88 96 89 The code sesans_parameters_css-hs.py can then be used as a template for a fitting problem with a structure factor:: 97 The code sesans_parameters_css-hs.py can then be used as a template for a 98 fitting problem with a structure factor:: 90 99 91 100 """ … … 131 140 # Constraints 132 141 # model.param_name = f(other params) 133 # EXAMPLE: model.scale = model.radius*model.radius*(1 - phi) - where radius and scale are model functions and phi is134 # a custom parameter142 # EXAMPLE: model.scale = model.radius*model.radius*(1 - phi) - where radius 143 # and scale are model functions and phi is a custom parameter 135 144 model.scale = phi*(1-phi) 136 145 model.volfraction = phi
Note: See TracChangeset
for help on using the changeset viewer.