Changes in / [14ecc24e:658dd57] in sasview
- Files:
-
- 3 deleted
- 3 edited
Legend:
- Unmodified
- Added
- Removed
-
.pydevproject
r9d93c37 r26c8be3 4 4 <pydev_property name="org.python.pydev.PYTHON_PROJECT_VERSION">python 2.7</pydev_property> 5 5 <pydev_pathproperty name="org.python.pydev.PROJECT_SOURCE_PATH"> 6 <path>/sasview /src</path>6 <path>/sasview4/src</path> 7 7 </pydev_pathproperty> 8 8 </pydev_project> -
src/sas/sasgui/perspectives/fitting/media/fitting_help.rst
r9d93c37 r5295cf5 636 636 637 637 Example: radius [2 : 5] , radius [10 : 25] 638 639 .. ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ 640 641 Combined Batch Fit Mode 642 ----------------------- 643 644 Batch mode does not allow for multiple models. In other words in batch mode 645 all the data sets must be fit with single model and set of parameter. At times 646 there may be a shape change occuring in the series that requires changing the 647 model part way through the series. In this case set up two batch fit pages 648 following the instructions in :ref:`Batch Fit Mode`. However *be careful!* each 649 time a batch fit panel runs fit it will overwrite the table of values. 650 651 However there may be occassion when one wants to run these two (or more) batch 652 fits and then plot one of the common parameters (e.g. radius of shere and 653 eventually cylinder). In this case the Combined Batch Fit can be used. 654 Similarly to the Simultaneous Fit page a new page will appear. In this case, 655 instead of a check box for each fitpage model there will be a check box for each 656 batchpage. Clicking the Fit button will run each batch fit *in sequence*. 657 658 .. image:: combine_batch_page.png 659 660 The batch table will then pop up at the end as before with the following 661 caveats: 662 663 .. note:: 664 The order matters. The parameters in the table will be taken from the model 665 used in the first batch page of the list. Any parameters from the 666 second and on batch pages that have the same name as a parameter in the first 667 will show up allowing for plotting of that parameter across the models. 668 .. note:: 669 a corralary of the above is that currently models created as a sum|multiply 670 model will not work as desired because the generated model parameters have a 671 p#_ appended to the beginning and thus radius and p1_radius will not be 672 recognized as the same parameter. 673 674 .. image:: combine_batch_grid.png 675 676 In this case the series is a time series. Unfortunately the time is not listed 677 in the file but the file name contains the information. A column can be added 678 manually, in this case called time. Clicking on the top of a column will select 679 it. Clicking next on the Add button next to the x or y row will add the cell 680 information to use in a plot. The axis labels will be automatically populated 681 from the top row information. Units can be specified as well using text and a 682 subset of in line Latex. Once this is set up, in this case using the peak 683 position from the two different models for the y axis and time on the x axis, 684 one clicks the Plot button. 685 686 .. image:: combine_batch_plot.png 687 688 Note the discontinuity in the peak position. This 689 is due to the fact that the Guassian fit is actually pretty bad and is not 690 actually finding the peak. 691 692 .. ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ 693 694 .. note:: This help document was last changed by Paul Butler, 06April2017 638 639 .. ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ 640 641 .. note:: This help document was last changed by Steve King, 10Oct2016 -
src/sas/sasgui/perspectives/fitting/simfitpage.py
ra9f9ca4 r959eb01 1 1 """ 2 Simultaneous or Batchfit page2 Simultaneous fit page 3 3 """ 4 # Note that this is used for both Simultaneous/Constrained fit AND for5 # combined batch fit. This is done through setting of the batch_on parameter.6 # There are the a half dozen or so places where an if statement is used as in7 # if not batch_on:8 # xxxx9 # else:10 # xxxx11 # This is just wrong but dont have time to fix this go. Proper approach would be12 # to strip all parts of the code that depend on batch_on and create the top13 # level class from which a contrained/simultaneous fit page and a combined14 # batch page inherit.15 #16 # 04/09/2017 --PDB17 18 4 import sys 19 5 from collections import namedtuple … … 414 400 # General Help button 415 401 self.btHelp = wx.Button(self, wx.ID_HELP, 'HELP') 416 if self.batch_on: 417 self.btHelp.SetToolTipString("Combined Batch Fitting help.") 418 else: 419 self.btHelp.SetToolTipString("Simultaneous/Constrained Fitting help.") 402 self.btHelp.SetToolTipString("Simultaneous/Constrained Fitting help.") 420 403 self.btHelp.Bind(wx.EVT_BUTTON, self._on_help) 421 404 … … 544 527 """ 545 528 _TreeLocation = "user/sasgui/perspectives/fitting/fitting_help.html" 546 if not self.batch_on: 547 _PageAnchor = "#simultaneous-fit-mode" 548 _doc_viewer = DocumentationWindow(self, self.ID_DOC, _TreeLocation, 529 _PageAnchor = "#simultaneous-fit-mode" 530 _doc_viewer = DocumentationWindow(self, self.ID_DOC, _TreeLocation, 549 531 _PageAnchor, 550 532 "Simultaneous/Constrained Fitting Help") 551 else:552 _PageAnchor = "#combined-batch-fit-mode"553 _doc_viewer = DocumentationWindow(self, self.ID_DOC, _TreeLocation,554 _PageAnchor,555 "Combined Batch Fit Help")556 533 557 534 def set_manager(self, manager):
Note: See TracChangeset
for help on using the changeset viewer.