Changes in / [b9c432ac:104613f] in sasview


Ignore:
Files:
1 deleted
5 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

    rb7ce5ad r8b89396  
    338338These optimisers form the *Bumps* package written by P Kienzle. For more information 
    339339on each optimiser, see the :ref:`Fitting_Documentation`. 
    340  
    341 .. ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ 
    342  
    343 Fitting Integer Parameters 
    344 -------------------------- 
    345  
    346 Most of the parameters in SasView models will naturally take floating point (decimal)  
    347 values, but there are some parameters which can only have integer values. Examples  
    348 include, but are not limited to, the number of shells in a multilayer vesicle, the  
    349 number of beads in a pearl necklace, the number of arms of a star polymer, and so on. 
    350 Wherever possible/recognised, the integer nature of a parameter is specified in the  
    351 respective model documentation and/or parameter table, so read the documentation  
    352 carefully! 
    353  
    354 Integer parameters must be fitted with care. 
    355  
    356 Start with your best possible guess for the value of the parameter. And using  
    357 *a priori* knowledge, fix as many of the other parameters as possible. 
    358   
    359 The SasView optimizers treat integer parameters internally as floating point  
    360 numbers, but the values presented to the user are truncated or rounded, as  
    361 appropriate. 
    362  
    363 In most instances integer parameters will probably be greater than zero. A good  
    364 policy in such cases is to use a constraint to enforce this. 
    365  
    366 Because an integer parameter should, by definition, only move in integer steps,  
    367 problems may be encountered if the optimizer step size is too small. Similarly,  
    368 be **very careful** about applying polydispersity to integer parameters. 
    369  
    370 The Levenberg-Marquardt and Quasi-Newton BFGS (and other derivative-based)  
    371 optimizers are probably best avoided for fitting models with integer parameters. 
    372340 
    373341.. ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ 
Note: See TracChangeset for help on using the changeset viewer.