source: sasview/src/sas/sasgui/perspectives/fitting/media/fitting_help.copy @ efe730d

ESS_GUIESS_GUI_DocsESS_GUI_batch_fittingESS_GUI_bumps_abstractionESS_GUI_iss1116ESS_GUI_iss879ESS_GUI_iss959ESS_GUI_openclESS_GUI_orderingESS_GUI_sync_sascalcmagnetic_scattrelease-4.2.2ticket-1009ticket-1094-headlessticket-1242-2d-resolutionticket-1243ticket-1249ticket885unittest-saveload
Last change on this file since efe730d was 65dfa99, checked in by smk78, 9 years ago

Restore accidentally deleted files - 2

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