- Timestamp:
- Sep 15, 2017 11:40:46 AM (7 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.2.2, ticket-1009, ticket-1094-headless, ticket-1242-2d-resolution, ticket-1243, ticket-1249, ticket885, unittest-saveload
- Children:
- ca383a0
- Parents:
- c56d9d74
- Location:
- src/sas/sasgui/perspectives/fitting/media
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
src/sas/sasgui/perspectives/fitting/media/fitting_help.rst
r203669a re081946 214 214 ['radius_effective', '', 1, [-numpy.inf, numpy.inf], 'volume', ''], 215 215 ['volfraction', '', 1, [-numpy.inf, numpy.inf], '', ''], 216 [...], 216 217 217 218 and to the declarations of the functions Iq and Iqxy::: … … 242 243 them. Finally, click the *Apply* button to generate and test the model and then click *Close*. 243 244 244 Any changes to a plugin model generated in this way only become effective *after* it is re-selected from the plugin models drop-down menu on the FitPage. If the model is not listed you can force a 245 Any changes to a plugin model generated in this way only become effective *after* it is re-selected 246 from the plugin models drop-down menu on the FitPage. If the model is not listed you can force a 245 247 recompilation of the plugins by selecting *Fitting* > *Plugin Model Operations* > *Load Plugin Models*. 246 248 … … 253 255 254 256 model_info = load_model_info('sphere+power_law') 255 model_info.name = 'My PluginModel'257 model_info.name = 'MyPluginModel' 256 258 model_info.description = 'sphere + power_law' 257 259 Model = make_model_from_info(model_info) … … 261 263 and description too!!! 262 264 263 The model specification string can handle multiple models and combinations of operators (+ - * /) which265 The model specification string can handle multiple models and combinations of operators (+ - * \\) which 264 266 are processed according to normal conventions. Thus 'model1+model2*model3' would be valid and would 265 267 multiply model2 by model3 before adding model1. In this example, parameters in the *FitPage* would be 266 prefixed A_\ (for model2), B_\ (for model3) and C_\ (for model1). Whilst this might appear a little 267 confusing, unless you were creating a plugin model from multiple instances of the same model the parameter assignments ought to be obvious when you load the plugin. 268 268 prefixed A (for model2), B (for model3) and C (for model1). Whilst this might appear a little 269 confusing, unless you were creating a plugin model from multiple instances of the same model the parameter 270 assignments ought to be obvious when you load the plugin. 271 272 If you need to include another plugin model in the model specification string, just prefix the name of 273 that model with *custom*. For instance:: 274 275 sphere+custom.MyPluginModel 276 277 To create a P(Q)*\S(Q) model use the @ symbol instead of * like this:: 278 279 sphere@hardsphere 280 269 281 This streamlined approach to building complex plugin models from existing library models, or models 270 282 available on the *Model Marketplace*, also permits the creation of P(Q)*\S(Q) plugin models, something -
src/sas/sasgui/perspectives/fitting/media/plugin.rst
rc56d9d74 re081946 20 20 21 21 **What follows below is quite technical. If you just want a helping hand to get 22 started creating your own models see :ref:`Adding_your_own_models`.**22 started creating your own models see** :ref:`Adding_your_own_models`. 23 23 24 24 Overview
Note: See TracChangeset
for help on using the changeset viewer.