Changes in / [f5f8553:d4cde37] in sasview


Ignore:
Files:
3 deleted
6 edited

Legend:

Unmodified
Added
Removed
  • INSTALL.txt

    re40390ee r26c9b85  
    4747More information can be found here: 
    4848 
    49 http://www.sasview.org/help/ 
    50 http://www.sasview.org/faq/ 
     49http://www.sasview.org/help.html 
     50http://www.sasview.org/faq.html 
    5151http://www.sasview.org/trac/wiki/DevNotes 
  • docs/sphinx-docs/source/user/RELEASE.rst

    r2c355a2 r8514f89  
    156156* Fixes # 784: Add 3D integral to Correlation Function analysis 
    157157* Fixes # 786: core_shell_parallelepiped 1-D model is incorrect 
    158 * Fixes # 818: "report button" followed by "save" makes an empty pdf file??? 
     158* Fixes # 818: “report button” followed by “save” makes an empty pdf file??? 
    159159* Fixes # 830: Check compliance of loader against NXcanSAS-1.0 release 
    160160* Fixes # 838: Fix model download from marketplace 
     
    770770          that any previous versions of SasView are uninstalled prior to  
    771771          installing the new version UNLESS you are installing SasView to  
    772           versioned folders. **We recommend you avoid using folder paths  
    773           that contain spaces or characters that cannot be found on a  
    774           standard keyboard (eg, characters with accents, umlauts, etc).** 
     772          versioned folders. 
    775773 
    776774.. note:: The easiest approach to setting up the proper environment to 
     
    967965Frequently Asked Questions 
    968966========================== 
    969 http://www.sasview.org/faq/ 
     967http://www.sasview.org/faq.html 
    970968 
    971969 
  • src/sas/sasgui/perspectives/fitting/media/fitting.rst

    r332c10d rc926a97  
    1717   Smearing Functions <resolution> 
    1818 
    19    Fitting Models with Structure Factors <fitting_sq> 
    20  
    21    Writing a Plugin Model <plugin> 
    22  
    2319   Polarisation/Magnetic Scattering <magnetism/magnetism> 
    24  
     20    
    2521   Oriented Particles <orientation/orientation> 
    2622 
     
    3127   Fitting SESANS Data <sesans/sesans_fitting> 
    3228 
     29   Writing a Plugin Model <plugin> 
     30 
    3331   Computations with a GPU <gpu_setup> 
    3432 
  • src/sas/sasgui/perspectives/fitting/media/fitting_help.rst

    r6d7b252b r8b89396  
    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 .. figure:: p_and_s_buttons.png 
    67  
    68 S(Q) models can be combined with models in the other categories to generate 
    69 what SasView calls "product models". See :ref:`Product_Models` for more 
    70 information. 
    71  
    7263Show 1D/2D 
    7364^^^^^^^^^^ 
     
    128119 
    129120For a complete list of all the library models available in SasView, see 
    130 the `Model Documentation <../../../sasgui/perspectives/fitting/models/index.html>`_ . 
     121the `Model Documentation <../../../index.html>`_ . 
    131122 
    132123It is also possible to add your own models. 
     
    347338These optimisers form the *Bumps* package written by P Kienzle. For more information 
    348339on each optimiser, see the :ref:`Fitting_Documentation`. 
    349  
    350 .. ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ 
    351  
    352 Fitting Integer Parameters 
    353 -------------------------- 
    354  
    355 Most of the parameters in SasView models will naturally take floating point (decimal)  
    356 values, but there are some parameters which can only have integer values. Examples  
    357 include, but are not limited to, the number of shells in a multilayer vesicle, the  
    358 number of beads in a pearl necklace, the number of arms of a star polymer, and so on. 
    359 Wherever possible/recognised, the integer nature of a parameter is specified in the  
    360 respective model documentation and/or parameter table, so read the documentation  
    361 carefully! 
    362  
    363 Integer parameters must be fitted with care. 
    364  
    365 Start with your best possible guess for the value of the parameter. And using  
    366 *a priori* knowledge, fix as many of the other parameters as possible. 
    367   
    368 The SasView optimizers treat integer parameters internally as floating point  
    369 numbers, but the values presented to the user are truncated or rounded, as  
    370 appropriate. 
    371  
    372 In most instances integer parameters will probably be greater than zero. A good  
    373 policy in such cases is to use a constraint to enforce this. 
    374  
    375 Because an integer parameter should, by definition, only move in integer steps,  
    376 problems may be encountered if the optimizer step size is too small. Similarly,  
    377 be **very careful** about applying polydispersity to integer parameters. 
    378  
    379 The Levenberg-Marquardt and Quasi-Newton BFGS (and other derivative-based)  
    380 optimizers are probably best avoided for fitting models with integer parameters. 
    381340 
    382341.. ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ 
  • 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.