- Timestamp:
- Sep 26, 2016 12:05:13 PM (8 years ago)
- Branches:
- master, ESS_GUI, ESS_GUI_Docs, ESS_GUI_batch_fitting, ESS_GUI_bumps_abstraction, ESS_GUI_iss1116, ESS_GUI_iss879, ESS_GUI_iss959, ESS_GUI_opencl, ESS_GUI_ordering, ESS_GUI_sync_sascalc, costrafo411, magnetic_scatt, release-4.1.1, release-4.1.2, release-4.2.2, release_4.0.1, ticket-1009, ticket-1094-headless, ticket-1242-2d-resolution, ticket-1243, ticket-1249, ticket885, unittest-saveload
- Children:
- a0373d5, e925f61
- Parents:
- 7f23423
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
src/sas/sasgui/perspectives/fitting/media/plugin.rst
r7f23423 r31d7803 288 288 ["radius", "Ang", 50, [0, inf], "volume", "Sphere radius"], 289 289 ] 290 # pylint: enable=bad-whitespace, line-too-long 290 291 291 292 **parameters = [["name", "units", default, [min,max], "type", "tooltip"],...]** … … 577 578 ............ 578 579 579 ::580 581 def ER(radius, thickness):582 """Effective radius of a core-shell sphere."""583 return radius + thickness584 585 580 Away from the dilute limit you can estimate scattering including 586 581 particle-particle interactions using $I(q) = P(q)*S(q)$ where $P(q)$ … … 591 586 form averaged over all the polydispersity values. 592 587 593 Consider the *core_shell_sphere*, which has a simple effective radius 588 :: 589 590 def ER(radius, thickness): 591 """Effective radius of a core-shell sphere.""" 592 return radius + thickness 593 594 Now consider the *core_shell_sphere*, which has a simple effective radius 594 595 equal to the radius of the core plus the thickness of the shell, as 595 596 shown above. Given polydispersity over *(r1, r2, ..., rm)* in radius and … … 616 617 one return value for each point in the mesh grid. 617 618 618 *NOTE: we may be removing or modifying this feature soon. * As of this619 writing, core-shell sphere returns (1., 1.) for *VR*, giving a volume620 ratio of 1.0. 619 *NOTE: we may be removing or modifying this feature soon. As of the 620 time of writing, core-shell sphere returns (1., 1.) for VR, giving a volume 621 ratio of 1.0.* 621 622 622 623 Unit Tests … … 660 661 661 662 If you are editing your model from the SasView GUI, you can test it 662 by selecting *Run -> Compile* from the *Model Editor* menu bar. An663 by selecting *Run > Compile* from the *Model Editor* menu bar. An 663 664 *Info* box will appear with the results of the compilation and a 664 665 check that the model runs. 665 666 666 667 If the model compiles and runs, you can next run the unit tests that 667 you have added using the **test =** values. Switch to the *Shell* tab668 you have added using the **test =** values. Switch to the *Shell* tab 668 669 and type the following:: 669 670 … … 705 706 For the random models, 706 707 707 - sld will be in(-0.5,10.5),708 - angles ( theta, phi, psi) will be in(-180,180),709 - angular dispersion will be in (0,45),710 - polydispersity will be in (0,1)711 - other values will be in (0, 2*v) where vis the value of the parameter in demo.712 713 Dispersion parameters n, sigma and typewill be unchanged from demo so that708 - *sld* will be in the range (-0.5,10.5), 709 - angles (*theta, phi, psi*) will be in the range (-180,180), 710 - angular dispersion will be in the range (0,45), 711 - polydispersity will be in the range (0,1) 712 - other values will be in the range (0, 2\ *v*), where *v* is the value of the parameter in demo. 713 714 Dispersion parameters *n*\, *sigma* and *type* will be unchanged from demo so that 714 715 run times are predictable. 715 716 … … 723 724 ^^^^^^^^^^ 724 725 725 **NB: For now we are not providing pylint with SasView; unless you have a726 SasView development environment available, you can ignore this section .**726 **NB: For now we are not providing pylint with SasView; so unless you have a 727 SasView development environment available, you can ignore this section!** 727 728 728 729 Run the lint check with:: … … 736 737 for standard model functions *Iq*, *Iqxy*, etc. 737 738 738 We will have delinting sessions at the SasView code camps, where we can739 We will have delinting sessions at the SasView Code Camps, where we can 739 740 decide on standards for model files, parameter names, etc. 740 741 741 For now, you can tell pylint to ignore things. For example, to align you 742 For now, you can tell pylint to ignore things. For example, to align your 742 743 parameters in blocks:: 743 744 … … 775 776 - `amsmath <http://www.ams.org/publications/authors/tex/amslatex>`_ 776 777 778 There is also a neat online WYSIWYG ReStructuredText editor at http://rst.ninjs.org\ . 779 777 780 Finally 778 781 ^^^^^^^ … … 780 783 Once compare and the unit test(s) pass properly and everything is done, 781 784 consider adding your model to the 782 ` model marketplace <http://marketplace.sasview.org/>`_.785 `Model Marketplace <http://marketplace.sasview.org/>`_.
Note: See TracChangeset
for help on using the changeset viewer.