Changes in / [b2964ef:4688acf] in sasview


Ignore:
Location:
src/sas
Files:
1 added
6 deleted
2 edited

Legend:

Unmodified
Added
Removed

  • src/sas/sasgui/perspectives/fitting/media/fitting_help.rst

    rfa307dd rb7ce5ad  
    4242*  *Ellipsoid* - ellipsoidal shapes (oblate,prolate, core shell, etc) 
    4343*  *Parellelepiped* - as the name implies 
    44 *  *Sphere* - spheroidal shapes (sphere, core multishell, vesicle, etc) 
     44*  *Sphere* - sheroidal shapes (sphere, core multishell, vesicle, etc) 
    4545*  *Lamellae* - lamellar shapes (lamellar, core shell lamellar, stacked 
    4646   lamellar, etc) 
    … …  
    6161on the *Description* button to the right. 
    6262 
    63 Product Models 
    64 ^^^^^^^^^^^^^^ 
    65  
    66 S(Q) models can be combined with many models in the other categories to 
    67 generate what SasView calls "product models". The combination can be done by 
    68 one of two methods, but how they behave is slightly different. 
    69  
    70 The first, most straightforward, method is simply to use the S(Q) drop-down in 
    71 the FitPage: 
    72  
    73 .. figure:: p_and_s_buttons.png 
    74  
    75 This example would then generate a product model with the following parameters: 
    76  
    77 .. figure:: p_and_s_buttons_parameters.png 
    78  
    79 The other method is to use the :ref:`Sum|Multi(p1,p2)` tool under Fitting > 
    80 Plugin Model Operations: 
    81  
    82 .. figure:: p_and_s_sum_model.png 
    83  
    84 This creates a product model with the following parameters: 
    85  
    86 .. figure:: p_and_s_sum_model_parameters.png 
    87  
    88 As can be seen, the second method has produced a product model with an extra 
    89 parameter: *radius_effective*. This is the radial distance determining the 
    90 range of the $S(Q)$ interaction and may, or may not, be the same as the 
    91 *radius*, in this example, depending on the concentration of the system. In 
    92 other systems, *radius_effective* may depend on the particle form (shape). 
    93  
    94 See :ref:`Product_Models` for more information. 
    95  
    9663Show 1D/2D 
    9764^^^^^^^^^^ 
    … …  
    152119 
    153120For a complete list of all the library models available in SasView, see 
    154 the `Model Documentation <../../../sasgui/perspectives/fitting/models/index.html>`_ . 
     121the `Model Documentation <../../../index.html>`_ . 
    155122 
    156123It is also possible to add your own models. 
    … …  
    249216Such a plugin should then be available in the S(Q) drop-down box on a FitPage (once 
    250217a P(Q) model has been selected). 
    251  
    252 .. _Sum|Multi(p1,p2): 
    253218 
    254219Sum|Multi(p1,p2) 

  • src/sas/sasview/test/README.txt

    r1cf0fc0 refe730d  
    1 Test data sets are included as a convenience to our users. The data sets are 
    2 organized based on their data structure; 1D data (ie, I(Q)), 2D data 
    3 (ie, I(Qx,Qy)), coordinate data (eg, PDB files), image data 
    4 (eg, TIFF files), SasView saved states, SESANS data, and data in formats that 
    5 are not yet implemented but which are in the works for future releases. 
     1Test data sets are included as a convenience to our users. The data sets are organized based on their data structure; 1D data (ie, I(Q)), 2D data (ie, I(Qx,Qy)), coordinate data (eg, PDB files), image data (eg, TIFF files), SasView saved states, SESANS data, and data in formats that are not yet implemented but which are in the works for future releases. 
    62 
    7 1D data sets EITHER a) have at least two columns of data with I(abs. units) on 
    8 the y-axis and Q on the x-axis, OR b) have I and Q in separate files. Data in 
    9 the latter format (/convertible_files) need to be converted to a single file 
    10 format with the File Converter tool before SasView will analyse them. 
     31D data sets EITHER a) have at least two columns of data with I(abs. units) on the y-axis and Q on the x-axis, OR b) have I and Q in separate files. Data in the latter format (/convertible_files) need to be converted to a single file format with the File Converter tool before SasView will analyse them. 
    114 
    12 2D data sets are data sets that give the deduced intensity for each detector 
    13 pixel. Depending on the file extension, uncertainty and metadata may also be 
    14 available. 
     52D data sets are data sets that give the deduced intensity for each detector pixel. Depending on the file extension, uncertainty and metadata may also be available. 
    156 
    16 Coordinate data sets are designed to be read by the Generic Scattering 
    17 Calculator tool. 
     7Coordinate data sets are designed to be read by the Generic Scattering Calculator tool. 
    188 
    199Image data sets are designed to be read by the Image Viewer tool. 
    2010 
    21 Save states are projects and analyses saved by the SASVIEW program. A single 
    22 analysis file contains the data and parameters for a single fit (.fit), p(r) 
    23 inversion (.pr), or invariant calculation (.inv). A project file (.svs) 
    24 contains the results for every active analysis. 
     11Save states are projects and analyses saved by the SASVIEW program. A single analysis file contains the data and parameters for a single fit (.fit), p(r) inversion (.pr), or invariant calculation (.inv). A project file (.svs) contains the results for every active analysis. 
    2512 
    26 SESANS data sets primarily contain the neutron polarisation as a function of 
    27 the spin-echo length. 
     13SESANS data sets primarily contain the neutron polarisation as a function of the spin-echo length. 
Note: See TracChangeset for help on using the changeset viewer.