source: sasview/docs/sphinx-docs/source/user/sasgui/perspectives/fitting/fitting_help.rst @ 6e94173

ESS_GUIESS_GUI_DocsESS_GUI_batch_fittingESS_GUI_bumps_abstractionESS_GUI_iss1116ESS_GUI_iss879ESS_GUI_iss959ESS_GUI_openclESS_GUI_orderingESS_GUI_sync_sascalccostrafo411magnetic_scattrelease-4.1.1release-4.1.2release-4.2.2release_4.0.1ticket-1009ticket-1094-headlessticket-1242-2d-resolutionticket-1243ticket-1249ticket885unittest-saveload
Last change on this file since 6e94173 was 6e94173, checked in by smk78, 8 years ago

Re-check fix for link broken by removal of old model docs

  • Property mode set to 100644
File size: 23.1 KB
RevLine 
[49148bb]1.. fitting_help.rst
2
3.. This is a port of the original SasView html help file to ReSTructured text
4.. by S King, ISIS, during SasView CodeCamp-III in Feb 2015.
5
6.. |inlineimage004| image:: sm_image004.gif
7.. |inlineimage005| image:: sm_image005.gif
8.. |inlineimage008| image:: sm_image008.gif
9.. |inlineimage009| image:: sm_image009.gif
10.. |inlineimage010| image:: sm_image010.gif
11.. |inlineimage011| image:: sm_image011.gif
12.. |inlineimage012| image:: sm_image012.gif
13.. |inlineimage018| image:: sm_image018.gif
14.. |inlineimage019| image:: sm_image019.gif
15
16
17Fitting Perspective
18===================
19
20.. ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
21
22Preparing to fit data
23---------------------
24
25To fit some data you must first load some data, activate one or more data sets,
26send those data sets to the fitting perspective, and select a model to fit to
27each data set.
28
29Instructions on how to load and activate data are in the section :ref:`Loading_data`.
30
31SasView can fit data in one of three ways:
32
33*  in *Single* fit mode - individual data sets are fitted independently one-by-one
34
35*  in *Simultaneous* fit mode - multiple data sets are fitted simultaneously to the *same* model with/without constrained parameters (this might be useful, for example, if you have measured the same sample at different contrasts)
36
37*  in *Batch* fit mode - multiple data sets are fitted sequentially to the *same* model (this might be useful, for example, if you have performed a kinetic or time-resolved experiment and have *lots* of data sets!)
38
39.. ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
40
41Selecting a model
42-----------------
43
44By default, the models in SasView are grouped into five categories
45
46*  *Shapes* - models describing 'objects' (spheres, cylinders, etc)
47*  *Shape-Independent* - models describing structure in terms of density correlation functions, fractals, peaks, power laws, etc
48*  *Customized Models* - SasView- or User-created (non-library) Python models
49*  *Uncategorised* - other models (for reflectivity, etc)
50*  *Structure Factor* - S(Q) models
51
52Use the *Category* drop-down menu to chose a category of model, then select
53a model from the drop-down menu beneath. A graph of the chosen model, calculated
54using default parameter values, will appear. The graph will update dynamically
55as the parameter values are changed.
56
57You can decide your own model categorizations using the :ref:`Category_Manager`.
58
59Once you have selected a model you can read its help documentation by clicking
60on the *Description* button to the right.
61
62Show 1D/2D
63^^^^^^^^^^
64
65Models are normally fitted to 1D (ie, I(Q) vs Q) data sets, but some models in
66SasView can also be fitted to 2D (ie, I(Qx,Qy) vs Qx vs Qy) data sets.
67
68*NB: Magnetic scattering can only be fitted in SasView in 2D.*
69
70To activate 2D fitting mode, click the *Show 2D* button on the *Fit Page*. To
71return to 1D fitting model, click the same button (which will now say *Show 1D*).
72
73.. ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
74
75.. _Category_Manager:
76
77Category Manager
78----------------
79
80To change the model categorizations, either choose *Category Manager* from the
81*View* option on the menubar, or click on the *Modify* button on the *Fit Page*.
82
83.. image:: cat_fig0.bmp
84
85The categorization of all models except the customized models can be reassigned,
86added to, and removed using *Category Manager*. Models can also be hidden from view
87in the drop-down menus.
88
89.. image:: cat_fig1.bmp
90
91Changing category
92^^^^^^^^^^^^^^^^^
93
94To change category, highlight a model in the list by left-clicking on its entry and
95then click the *Modify* button. Use the *Change Category* panel that appears to make
96the required changes.
97
98.. image:: cat_fig2.bmp
99
100To create a category for the selected model, click the *Add* button. In order
101to delete a category, select the category name and click the *Remove Selected*
102button. Then click *Done*.
103
104Showing/hiding models
105^^^^^^^^^^^^^^^^^^^^^
106
107Use the *Enable All / Disable All* buttons and the check boxes beside each model to
108select the models to show/hide. To apply the selection, click *Ok*. Otherwise click
109*Cancel*.
110
111*NB: It may be necessary to change to a different category and then back again*
112*before any changes take effect.*
113
114.. ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
115
116Model Functions
117---------------
118
[6e94173]119For a complete list of all the library models available in SasView, see the Model Documentation.
[49148bb]120
121It is also possible to add your own models.
122
123.. ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
124
125.. _Adding_your_own_models:
126
127Adding your own models
128----------------------
129
130There are currently two ways to add your own models to SasView:
131
132* Using the :ref:`Custom_Model_Editor`
133* By :ref:`Writing_a_Plugin`
134
135*NB: Because of the way these options are implemented, it is not possible for them*
136*to use the polydispersity algorithms in SasView. Only models in the model library*
137*can do this. At the time of writing (Release 3.1.0) work is in hand to make it*
138*easier to add new models to the model library.*
139
140.. ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
141
142.. _Custom_Model_Editor:
143
144Custom Model Editor
145-------------------
146
147From the *Fitting* option in the menu bar, select *Edit Custom Model*.
148
149.. image:: edit_model_menu.bmp
150
151and then one of the options
152
153*  *New* - to create a new custom model template
154*  *Sum|Multi(p1,p2)* - to create a new model by summing/multiplying existing models in the model library
155*  *Advanced* - to edit a new custom model
156*  *Delete* - to delete a custom model
157
158New
159^^^^
160
161.. image:: new_model.bmp
162
163A model template generated by this option can be viewed and further modified using
164the :ref:`Advanced` option.
165
166Sum|Multi(p1,p2)
167^^^^^^^^^^^^^^^^
168
169.. image:: sum_model.bmp
170
171This option creates a custom model of the form
172
173Custom Model = scale_factor \* (model1 +/\* model2)
174
175In the *Easy Sum/Multi Editor* give the new custom model a function name and brief
176description (to appear under the *Details* button on the *Fit Page*). Then select
177two existing models, as p1 and p2, and the required operator, '+' or '*' between
178them. Finally, click the *Apply* button to generate the model and then click *Close*.
179
180*NB: Any changes to a custom model generated in this way only become effective after*
181*it is re-selected from the model drop-down menu on the Fit Page.*
182
183.. _Advanced:
184
185Advanced
186^^^^^^^^
187
188Selecting this option shows all the custom models in the plugin model folder
189
190  *C:\\Users\\[username]\\.sasview\\plugin_models* - (on Windows)
191
192You can edit, modify, and save the Python code in any of these models using the
193*Advanced Custom Model Editor*.
194
195*NB: Unless you are confident about what you are doing, it is recommended that you*
196*only modify lines denoted with the ## <----- comments!*
197
198When editing is complete, select *Run -> Compile* from the *Model Editor* menu bar. An
199*Info* box will appear with the results of the compilation and model unit tests. The
200model will only be usable if the tests 'pass'.
201
202To use the model, go to the relevant *Fit Page*, select the *Customized Models*
203category and then select the model from the drop-down menu.
204
205*NB: Any changes to a custom model generated in this way only become effective after*
206*it is re-selected from the model drop-down menu on the Fit Page.*
207
208Delete
209^^^^^^
210
211Simply highlight the custom model to be removed. This operation is final!
212
213*NB: Custom models shipped with SasView cannot be removed in this way.*
214
215.. ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
216
217.. _Writing_a_Plugin:
218
219Writing a Plugin
220----------------
221
222Advanced users can write their own model in Python and save it to the the SasView
223*plugin_models* folder
224
225  *C:\\Users\\[username]\\.sasview\\plugin_models* - (on Windows)
226
227in .py format. The next time SasView is started it will compile the plugin and add
228it to the list of *Customized Models*.
229
230It is recommended that existing plugin models be used as templates.
231
232.. ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
233
234.. _Fitting_Options:
235
236Fitting Options
237---------------
238
239It is possible to specify which optimiser SasView should use to fit the data, and
240to modify some of the configurational parameters for each optimiser.
241
242From *Fitting* in the menu bar select *Fit Options*, then select one of the following
243optimisers:
244
245*  DREAM
246*  Levenberg-Marquardt
247*  Quasi-Newton BFGS
248*  Differential Evolution
249*  Nelder-Mead Simplex
250
251The DREAM optimiser is the most sophisticated, but may not necessarily be the best
252option for fitting simple models. If uncertain, try the Levenberg-Marquardt optimiser
253initially.
254
255These optimisers form the *Bumps* package written by P Kienzle. For more information
256on each optimiser, see the :ref:`Fitting_Documentation`.
257
258.. ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
259
260Fitting Limits
261--------------
262
263By default, *SasView* will attempt to model fit the full range of the data; ie,
264across all *Q* values. If necessary, however, it is possible to specify only a
265sub-region of the data for fitting.
266
267In a *FitPage* or *BatchPage* change the *Q* values in the *Min* and/or *Max*
268text boxes. Vertical coloured bars will appear on the graph with the data and
269'theory' indicating the current *Q* limits (red = *Qmin*, purple = *Qmax*).
270
271To return to including all data in the fit, click the *Reset* button.
272
273.. ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
274
275
276Shortcuts
277---------
278
279Copy/Paste Parameters
280^^^^^^^^^^^^^^^^^^^^^
281
282It is possible to copy the parameters from one *Fit Page* and to paste them into
283another *Fit Page* using the same model.
284
285To *copy* parameters, either:
286
287*  Select *Edit -> Copy Params* from the menu bar, or
288*  Use Ctrl(Cmd on Mac) + Left Mouse Click on the *Fit Page*.
289
290To *paste* parameters, either:
291
292*  Select *Edit -> Paste Params* from the menu bar, or
293*  Use Ctrl(Cmd on Mac) + Shift + Left-click on the *Fit Page*.
294
295If either operation is successful a message will appear in the info line at the
296bottom of the SasView window.
297
298Bookmark
299^^^^^^^^
300
301To *Bookmark* a *Fit Page* either:
302
303*  Select a *Fit Page* and then click on *Bookmark* in the tool bar, or
304*  Right-click and select the *Bookmark* in the popup menu.
305
306.. ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
307
308.. _Status_bar:
309
310Status Bar & Console
311--------------------
312
313The status bar is located at the bottom of the SasView window and displays
314messages, hints, warnings and errors.
315
316At the right-hand side of the status bar is a button marked *Console*. The *Console*
317displays available message history and some run-time traceback information.
318
319During a long task the *Console* can also be used to monitor the progress.
320
321.. ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
322
323.. _Single_Fit_Mode:
324
325Single Fit Mode
326---------------
327
328*NB: Before proceeding, ensure that the Single Mode radio button at the bottom of*
329*the Data Explorer is checked (see the section* :ref:`Loading_data` *).*
330
331This mode fits one data set.
332
333When data is sent to the fitting perspective it is plotted in a graph window as
334markers.
335
336If a graph does not appear, or a graph window appears but is empty, then the data
337has not loaded correctly. Check to see if there is a message in the :ref:`Status_Bar`
338or in the *Console* window.
339
340Assuming the data has loaded correctly, when a model is selected a green model
341calculation (or what SasView calls a 'Theory') line will appear in the earlier graph
342window, and a second graph window will appear displaying the residuals (the
343difference between the experimental data and the theory) at the same X-data values.
344See :ref:`Assessing_Fit_Quality`.
345
346The objective of model-fitting is to find a *physically-plausible* model, and set
347of model parameters, that generate a theory that reproduces the experimental data
348and gives residual values as close to zero as possible.
349
350Change the default values of the model parameters by hand until the theory line
351starts to represent the experimental data. Then uncheck the tick boxes alongside
352all parameters *except* the 'background' and the 'scale'. Click the *Fit* button.
353SasView will optimise the values of the 'background' and 'scale' and also display
354the corresponding uncertainties on the optimised values.
355
356*NB: If no uncertainty is shown it generally means that the model is not very*
357*dependent on the corresponding parameter (or that one or more parameters are*
358*'correlated').*
359
360In the bottom left corner of the *Fit Page* is a box displaying the normalised value
361of the statistical |chi|\  :sup:`2` parameter returned by the optimiser.
362
363Now check the box for another model parameter and click *Fit* again. Repeat this
364process until most or all parameters are checked and have been optimised. As the
365fit of the theory to the experimental data improves the value of 'chi2/Npts' will
366decrease. A good model fit should easily produce values of 'chi2/Npts' that are
367close to zero, and certainly <100. See :ref:`Assessing_Fit_Quality`.
368
369SasView has a number of different optimisers (see the section :ref:`Fitting_Options`).
370The DREAM optimiser is the most sophisticated, but may not necessarily be the best
371option for fitting simple models. If uncertain, try the Levenberg-Marquardt optimiser
372initially.
373
374.. ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
375
376Simultaneous Fit Mode
377---------------------
378
379*NB: Before proceeding, ensure that the Single Mode radio button at the bottom of*
380*the Data Explorer is checked (see the section* :ref:`Loading_data` *).*
381
382This mode is an extension of the :ref:`Single_Fit_Mode` that fits two or more data
383sets *to the same model* simultaneously. If necessary it is possible to constrain
384fit parameters between data sets (eg, to fix a background level, or radius, etc).
385
386If the data to be fit are in multiple files, load each file, then select each file
387in the *Data Explorer*, and *Send To Fitting*. If multiple data sets are in one file,
388load that file, *Unselect All Data*, select just those data sets to be fitted, and
389*Send To Fitting*. Either way, the result should be that for *n* data sets you have
3902\ *n* graphs (*n* of the data and model fit, and *n* of the resulting residuals). But
391it may be helpful to minimise the residuals plots for clarity. Also see
392:ref:`Assessing_Fit_Quality`.
393
394*NB: If you need to use a customized model, you must ensure that model is available*
395*first (see* :ref:`Adding_your_own_models` *).*
396
397Method
398^^^^^^
399
400Now go to each *FitPage* in turn and:
401
402  Select the required category and model;
403
404  Unselect all the model parameters;
405
406  Enter some starting guesses for the parameters;
407
408  Enter any parameter limits (recommended);
409
410  Select which parameters will refine (selecting all is generally a bad idea...);
411
412When done, select *Constrained or Simultaneous Fit* under *Fitting* in the menu bar.
413
414In the *Const & Simul Fit* page that appears, select which data sets are to be
415simultaneously fitted (this will probably be all of them or you would not have loaded
416them in the first place!).
417
418To tie parameters between the data sets with constraints, check the 'yes' radio button
419next to *Add Constraint?* in the *Fit Constraints* box.
420
421*NB: You can only constrain parameters that are set to refine.*
422
423When ready, click the *Fit* button on the *Const & Simul Fit* page, NOT the *Fit*
424button on the individual *FitPage*'s.
425
426Simultaneous Fits without Constraints
427^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
428
429The results of the model-fitting will be returned to each of the individual
430*FitPage*'s.
431
432Note that the chi2/Npts value returned is the SUM of the chi2/Npts of each fit. To
433see the chi2/Npts value for a specific *FitPage*, click the *Compute* button at the
434bottom of that *FitPage* to recalculate. Also see :ref:`Assessing_Fit_Quality`.
435
436Simultaneous Fits with Constraints
437^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
438
439Use the *Easy Setup* drop-down buttons in the *Const & Simul Fit* page to set
440up constraints between *FitPage*'s.
441
442Constraints will generally be of the form
443
444  Mi Parameter1 = Mj.Parameter1
445
446however the text box after the '=' sign can be used to adjust this
447relationship; for example
448
449  Mi Parameter1 = scalar \* Mj.Parameter1
450
451A 'free-form' constraint box is also provided.
452
453Many constraints can be entered for a single fit.
454
455The results of the model-fitting will be returned to each of the individual
456*FitPage*'s.
457
458Note that the chi2/Npts value returned is the SUM of the chi2/Npts of each fit. To
459see the chi2/Npts value for a specific *FitPage*, click the *Compute* button at the
460bottom of that *FitPage* to recalculate. Also see :ref:`Assessing_Fit_Quality`.
461
462.. ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
463
464Batch Fit Mode
465--------------
466
467*NB: Before proceeding, ensure that the Single Mode radio button at the bottom of*
468*the Data Explorer is checked (see the section* :ref:`Loading_data` *). The Batch*
469*Mode button will be used later on!*
470
471This mode *sequentially* fits two or more data sets *to the same model*. Unlike in
472simultaneous fitting, in batch fitting it is not possible to constrain fit parameters
473between data sets.
474
475If the data to be fit are in multiple files, load each file in the *Data Explorer*.
476If multiple data sets are in one file, load just that file. *Unselect All Data*, then
477select a single initial data set to be fitted. Fit that selected data set as described
478above under :ref:`Single_Fit_Mode` .
479
480*NB: If you need to use a customized model, you must ensure that model is available*
481*first (see* :ref:`Adding_your_own_models` *).*
482
483Method
484^^^^^^
485
486Now *Select All Data* in the *Data Explorer*, check the *Batch Mode* radio button
487at the bottom of that panel and *Send To Fitting*. A *BatchPage* will be created.
488
489.. image:: batch_button_area.bmp
490
491*NB: The Batch Page can also be created by checking the Batch Mode radio button*
492*and selecting New Fit Page under Fitting in the menu bar.*
493
494Using the drop-down menus in the *BatchPage*, now set up the *same* data set
495with the *same* model that you just fitted in single fit mode. A quick way to
496set the model parameter values is to just copy them from the earlier Single
497Fit. To do this, go back to the Single Fit *FitPage*, select *Copy Params*
498under *Edit* in the menu bar, then go back to the *BatchPage* and *Paste Params*.
499
500When ready, use the *Fit* button on the *BatchPage* to perform the fitting, NOT
501the *Fit* button on the individual *FitPage*'s.
502
503Unlike in single fit mode, the results of batch fits are not returned to
504the *BatchPage*. Instead, a spreadsheet-like :ref:`Grid_Window` will appear.
505
506If you want to visually check a graph of a particular fit, click on the name of
507a *Data set* in the *Grid Window* and then click the *View Fits* button. The
508data and the model fit will be displayed. If you select mutliple data sets they
509will all appear on one graph.
510
511.. image:: view_button.bmp
512
513*NB: In theory, returning to the BatchPage and changing the name of the I(Q)*
514*data source should also work, but at the moment whilst this does change the*
515*data set displayed it always superimposes the 'theory' corresponding to the*
516*starting parameters.*
517
518If you select a 'Chi2' value and click the *View Fits* button a graph of the
519residuals for that data set is displayed. Again, if you select multiple 'Chi2'
520values then all the residuals data will appear on one graph. Also see
521:ref:`Assessing_Fit_Quality`.
522
523Chain Fitting
524^^^^^^^^^^^^^
525
526By default, the *same* parameter values copied from the initial single fit into
527the *BatchPage* will be used as the starting parameters for all batch fits. It
528is, however, possible to get *SasView* to use the results of a fit to a preceding
529data set as the starting parameters for the next fit in the sequence. This
530variation of batch fitting is called *Chain Fitting*, and will considerably speed
531up model-fitting if you have lots of very similar data sets where a few parameters
532are gradually changing. Do not use chain fitting on disparate data sets.
533
534To use chain fitting, select *Chain Fitting* under *Fitting* in the menu bar. It
535toggles on/off, so selecting it again will switch back to normal batch fitting.
536
537.. _Grid_Window:
538
539Grid Window
540^^^^^^^^^^^
541
542The *Grid Window* provides an easy way to view the results from batch fitting.
543It will be displayed automatically when a batch fit completes, but may be
544opened at any time by selecting *Show Grid Window* under *View* in the menu
545bar.
546
547.. image:: restore_batch_window.bmp
548
549Once a batch fit is completed, all model parameters are displayed but *not*
550their uncertainties. To view the uncertainties, click on a given column then
551go to *Edit* in the menu bar, select *Insert Column Before* and choose the
552required data from the list. An empty column can be inserted in the same way.
553
554To remove a column from the grid, click on the column header and choose
555*Remove Column* under *Edit* in the menu bar. The same functionality also
556allows you to re-order columns.
557
558*NB: You cannot insert/remove/re-order the rows in the Grid Window.*
559
560All of the above functions are also available by right-clicking on a column
561label.
562
563.. image:: edit_menu.bmp
564
565*NB: If there is an existing Grid Window and another batch fit is performed,*
566*an additional 'Table' tab will be added to the Grid Window.*
567
568The parameter values in the *currently selected* table of the *Grid Window*
569can be output to a CSV file by choosing *Save As* under *File* in the (*Grid*
570*Window*) menu bar. The default filename includes the date and time that the
571batch fit was performed.
572
573Saved CSV files can be reloaded by choosing *Open* under *File* in the *Grid*
574*Window* menu bar. The loaded parameters will appear in a new table tab.
575
576.. image:: file_menu.bmp
577
578*NB: Saving the Grid Window does not save any experimental data, residuals*
579*or actual model fits. Consequently if you reload a saved CSV file the*
580*ability to View Fits will be lost.*
581
582Parameter Plots
583^^^^^^^^^^^^^^^
584
585Any column of *numeric* parameter values can be plotted against another using
586the *Grid Window*. Simply select one column at the time and click the *Add*
587button next to the required *X/Y-axis Selection Range* text box. When both
588the X and Y axis boxes have been completed, click the *Plot* button.
589
590When the *Add* button is clicked, *SasView* also automatically completes the
591*X/Y-axis Label* text box with the heading from Row 1 of the selected table,
592but different labels and units can be entered manually.
593
594.. image:: plot_button.bmp
595
596The *X/Y-axis Selection Range* can be edited manually. The text control box
597recognises the operators +, -, \*, /, or 'pow', and allows the following
598types of expression :
599 
600  1) if an axis label range is a function of 1 or more *columns*, write
601     this type of expression
602
603     constant1 * column_name1 [minimum row index :  maximum  row index]
604     operator constant2 * column_name2 [minimum row index :  maximum  row index]
605
606     Example: radius [2 : 5] -3 * scale [2 : 5]
607
608  2) if only some *values* of a given column are needed but the range between
609     the first row and the last row used is not continuous, write this type of
610     expression
611
612     column_name1 [minimum row index1 :  maximum  row index1] , column_name1
613     [minimum row index2 :  maximum  row index2]
614
615     Example: radius [2 : 5] , radius [10 : 25]
616
617.. ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
618
619.. note::  This help document was last changed by Steve King, 04Jun2015
Note: See TracBrowser for help on using the repository browser.