Ignore:
Timestamp:
Mar 31, 2019 5:43:12 AM (5 years ago)
Author:
GitHub <noreply@…>
Parents:
6d7b252b (diff), d4cde37 (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.
git-author:
Paul Kienzle <pkienzle@…> (03/31/19 05:43:12)
git-committer:
GitHub <noreply@…> (03/31/19 05:43:12)
Message:

Merge d4cde3775cc19e3e8ac413babb90e5015eb330e7 into 6d7b252bf3722c053065645b1afe65424979127f

File:
1 edited

Legend:

Unmodified
Added
Removed
  • src/sas/sasgui/perspectives/fitting/media/fitting_help.rst

    r9258c43c r6d7b252b  
    4242*  *Ellipsoid* - ellipsoidal shapes (oblate,prolate, core shell, etc) 
    4343*  *Parellelepiped* - as the name implies 
    44 *  *Sphere* - sheroidal shapes (sphere, core multishell, vesicle, etc) 
     44*  *Sphere* - spheroidal 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 
     63Product Models 
     64^^^^^^^^^^^^^^ 
     65 
     66.. figure:: p_and_s_buttons.png 
     67 
     68S(Q) models can be combined with models in the other categories to generate 
     69what SasView calls "product models". See :ref:`Product_Models` for more 
     70information. 
     71 
    6372Show 1D/2D 
    6473^^^^^^^^^^ 
     
    119128 
    120129For a complete list of all the library models available in SasView, see 
    121 the `Model Documentation <../../../index.html>`_ . 
     130the `Model Documentation <../../../sasgui/perspectives/fitting/models/index.html>`_ . 
    122131 
    123132It is also possible to add your own models. 
     
    338347These optimisers form the *Bumps* package written by P Kienzle. For more information 
    339348on each optimiser, see the :ref:`Fitting_Documentation`. 
     349 
     350.. ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ 
     351 
     352Fitting Integer Parameters 
     353-------------------------- 
     354 
     355Most of the parameters in SasView models will naturally take floating point (decimal)  
     356values, but there are some parameters which can only have integer values. Examples  
     357include, but are not limited to, the number of shells in a multilayer vesicle, the  
     358number of beads in a pearl necklace, the number of arms of a star polymer, and so on. 
     359Wherever possible/recognised, the integer nature of a parameter is specified in the  
     360respective model documentation and/or parameter table, so read the documentation  
     361carefully! 
     362 
     363Integer parameters must be fitted with care. 
     364 
     365Start 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  
     368The SasView optimizers treat integer parameters internally as floating point  
     369numbers, but the values presented to the user are truncated or rounded, as  
     370appropriate. 
     371 
     372In most instances integer parameters will probably be greater than zero. A good  
     373policy in such cases is to use a constraint to enforce this. 
     374 
     375Because an integer parameter should, by definition, only move in integer steps,  
     376problems may be encountered if the optimizer step size is too small. Similarly,  
     377be **very careful** about applying polydispersity to integer parameters. 
     378 
     379The Levenberg-Marquardt and Quasi-Newton BFGS (and other derivative-based)  
     380optimizers are probably best avoided for fitting models with integer parameters. 
    340381 
    341382.. ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ 
Note: See TracChangeset for help on using the changeset viewer.