Changes in / [f5f8553:d4cde37] in sasview
- Files:
-
- 3 deleted
- 6 edited
Legend:
- Unmodified
- Added
- Removed
-
INSTALL.txt
re40390ee r26c9b85 47 47 More information can be found here: 48 48 49 http://www.sasview.org/help /50 http://www.sasview.org/faq /49 http://www.sasview.org/help.html 50 http://www.sasview.org/faq.html 51 51 http://www.sasview.org/trac/wiki/DevNotes -
docs/sphinx-docs/source/user/RELEASE.rst
r2c355a2 r8514f89 156 156 * Fixes # 784: Add 3D integral to Correlation Function analysis 157 157 * 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??? 159 159 * Fixes # 830: Check compliance of loader against NXcanSAS-1.0 release 160 160 * Fixes # 838: Fix model download from marketplace … … 770 770 that any previous versions of SasView are uninstalled prior to 771 771 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. 775 773 776 774 .. note:: The easiest approach to setting up the proper environment to … … 967 965 Frequently Asked Questions 968 966 ========================== 969 http://www.sasview.org/faq /967 http://www.sasview.org/faq.html 970 968 971 969 -
src/sas/sasgui/perspectives/fitting/media/fitting.rst
r332c10d rc926a97 17 17 Smearing Functions <resolution> 18 18 19 Fitting Models with Structure Factors <fitting_sq>20 21 Writing a Plugin Model <plugin>22 23 19 Polarisation/Magnetic Scattering <magnetism/magnetism> 24 20 25 21 Oriented Particles <orientation/orientation> 26 22 … … 31 27 Fitting SESANS Data <sesans/sesans_fitting> 32 28 29 Writing a Plugin Model <plugin> 30 33 31 Computations with a GPU <gpu_setup> 34 32 -
src/sas/sasgui/perspectives/fitting/media/fitting_help.rst
r6d7b252b r8b89396 42 42 * *Ellipsoid* - ellipsoidal shapes (oblate,prolate, core shell, etc) 43 43 * *Parellelepiped* - as the name implies 44 * *Sphere* - s pheroidal shapes (sphere, core multishell, vesicle, etc)44 * *Sphere* - sheroidal shapes (sphere, core multishell, vesicle, etc) 45 45 * *Lamellae* - lamellar shapes (lamellar, core shell lamellar, stacked 46 46 lamellar, etc) … … 61 61 on the *Description* button to the right. 62 62 63 Product Models64 ^^^^^^^^^^^^^^65 66 .. figure:: p_and_s_buttons.png67 68 S(Q) models can be combined with models in the other categories to generate69 what SasView calls "product models". See :ref:`Product_Models` for more70 information.71 72 63 Show 1D/2D 73 64 ^^^^^^^^^^ … … 128 119 129 120 For a complete list of all the library models available in SasView, see 130 the `Model Documentation <../../../ sasgui/perspectives/fitting/models/index.html>`_ .121 the `Model Documentation <../../../index.html>`_ . 131 122 132 123 It is also possible to add your own models. … … 347 338 These optimisers form the *Bumps* package written by P Kienzle. For more information 348 339 on each optimiser, see the :ref:`Fitting_Documentation`. 349 350 .. ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ351 352 Fitting Integer Parameters353 --------------------------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. Examples357 include, but are not limited to, the number of shells in a multilayer vesicle, the358 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 the360 respective model documentation and/or parameter table, so read the documentation361 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 using366 *a priori* knowledge, fix as many of the other parameters as possible.367 368 The SasView optimizers treat integer parameters internally as floating point369 numbers, but the values presented to the user are truncated or rounded, as370 appropriate.371 372 In most instances integer parameters will probably be greater than zero. A good373 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.381 340 382 341 .. 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. 1 Test 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. 6 2 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. 3 1D 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. 11 4 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. 5 2D 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. 15 6 16 Coordinate data sets are designed to be read by the Generic Scattering 17 Calculator tool. 7 Coordinate data sets are designed to be read by the Generic Scattering Calculator tool. 18 8 19 9 Image data sets are designed to be read by the Image Viewer tool. 20 10 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. 11 Save 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. 25 12 26 SESANS data sets primarily contain the neutron polarisation as a function of 27 the spin-echo length. 13 SESANS 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.