- Timestamp:
- Mar 30, 2019 2:31:38 AM (6 years ago)
- Branches:
- master
- Children:
- 4ecf91a
- Parents:
- 104613f (diff), 332c10d (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. - Location:
- src/sas
- Files:
-
- 1 added
- 4 edited
Legend:
- Unmodified
- Added
- Removed
-
src/sas/sasgui/perspectives/fitting/media/fitting.rst
rc926a97 r332c10d 17 17 Smearing Functions <resolution> 18 18 19 Fitting Models with Structure Factors <fitting_sq> 20 21 Writing a Plugin Model <plugin> 22 19 23 Polarisation/Magnetic Scattering <magnetism/magnetism> 20 24 21 25 Oriented Particles <orientation/orientation> 22 26 … … 27 31 Fitting SESANS Data <sesans/sesans_fitting> 28 32 29 Writing a Plugin Model <plugin>30 31 33 Computations with a GPU <gpu_setup> 32 34 -
src/sas/sasgui/perspectives/fitting/media/fitting_help.rst
r9258c43c rb7ce5ad 338 338 These optimisers form the *Bumps* package written by P Kienzle. For more information 339 339 on 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. 340 372 341 373 .. ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ -
src/sas/sasgui/perspectives/fitting/gpu_options.py
r895703d r104613f 257 257 #The same block of code as for OK but it is needed if we want to have 258 258 #active response to Test button 259 import numpy as np 259 260 no_opencl_msg = False 260 261 if self.sas_opencl: … … 269 270 try: 270 271 env = sasmodels.kernelcl.environment() 271 clinfo = [(ctx.devices[0].platform.vendor, 272 ctx.devices[0].platform.version, 273 ctx.devices[0].vendor, 274 ctx.devices[0].name, 275 ctx.devices[0].version) 276 for ctx in env.context] 272 dtype64 = np.dtype('float64') 273 dtype32 = np.dtype('float32') 274 if dtype64 in env.context: 275 ctx = env.context[dtype64].devices[0] 276 else: 277 ctx = env.context[dtype32].devices[0] 278 clinfo = (ctx.platform.vendor, 279 ctx.platform.version, 280 ctx.vendor, 281 ctx.name, 282 ctx.version) 277 283 except Exception: 278 284 clinfo = None
Note: See TracChangeset
for help on using the changeset viewer.