Changeset 13f5656 in sasview for src/sas/sasgui/perspectives
- Timestamp:
- Oct 10, 2016 12:59:02 PM (8 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.1.1, release-4.1.2, release-4.2.2, ticket-1009, ticket-1094-headless, ticket-1242-2d-resolution, ticket-1243, ticket-1249, ticket885, unittest-saveload
- Children:
- ec72ceb
- Parents:
- 131d94b (diff), afb93df (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. - git-author:
- wpotrzebowski <Wojciech.Potrzebowski@…> (10/10/16 12:58:46)
- git-committer:
- wpotrzebowski <Wojciech.Potrzebowski@…> (10/10/16 12:59:02)
- Location:
- src/sas/sasgui/perspectives
- Files:
-
- 3 added
- 1 deleted
- 3 edited
- 1 moved
Legend:
- Unmodified
- Added
- Removed
-
src/sas/sasgui/perspectives/calculator/media/python_shell_help.rst
rd85c194 rafb93df 3 3 .. This is a port of the original SasView html help file to ReSTructured text 4 4 .. by S King, ISIS, during SasView CodeCamp-III in Feb 2015. 5 .. Text revised during Code Camp V in Oct 2016. 5 6 6 Python Shell Tool 7 ================= 7 .. _Python_shell: 8 9 Python Shell-Editor Tool 10 ======================== 8 11 9 12 Description 10 13 ----------- 11 14 12 This is a Python shell/editor (PyCrust) provided with WxPython. An editing 13 notebook will show up when a Python file is created/loaded with the *New* or 14 *Open* options on the menu. 15 This is a Python shell/editor provided with WxPython. 15 16 16 *Run* enables the editor to compile and run the Python code. 17 For the help about Python, visit the website http://docs.python.org/tutorial/ 17 18 18 For the details about the Python, visit the website http://docs.python.org/tutorial/ 19 .. note:: This shell/editor has its own help, but the Help() and Credits() calls do not work on Macs. 19 20 20 The NumPy, SciPy, and Matplotlib, etc, libraries are shipped with SasView. 21 However, some functionality may not work. 21 The NumPy, SciPy, and Matplotlib, etc, libraries are shipped with SasView and so functions from these can be imported into the shell/editor, however, some functionality may not work. 22 22 23 PyCrust has its own Help. 23 .. image:: new_pycrust_example.png 24 :align: center 24 25 25 *NOTE! The Help() and Credits() calls do not work on Macs.* 26 When a Python file, for example a fitting model, is created or loaded with the *New* or *Open* options from the menu, a new tab opens with an editing notebook. 26 27 27 .. ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ 28 .. image:: new_pycrust_example_2.png 29 :align: center 28 30 29 Example 30 ------- 31 If a Python (.py) model has a linked C (.c) subroutine *in the same folder* then the shell/editor will open both! However input focus is usually transferred to the tab with the .c file. 31 32 32 An example calling the Matplotlib plotting gallery: 33 34 .. image:: pycrust_example.png 33 To compile a model, select *Run* > *Check Model* from the shell/editor menu. If the model contains a unit test (which it should!!!) then this will also run and a popup window will report the success/failure of the test. 35 34 36 35 .. ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ 37 36 38 .. note:: This help document was last changed by Steve King, 1 9Feb201537 .. note:: This help document was last changed by Steve King, 10Oct2015 -
src/sas/sasgui/perspectives/fitting/media/fitting.rst
r2a6d757 re8447d8 3 3 Fitting Documentation 4 4 ===================== 5 6 .. note:: In Windows use [Alt]-[Cursor left] to return to the previous page 5 7 6 8 .. toctree:: -
src/sas/sasgui/perspectives/fitting/media/fitting_help.rst
r05829fb rafb93df 141 141 From the *Fitting* option in the menu bar, select *Edit Custom Model*. 142 142 143 .. image:: edit_model_menu. bmp143 .. image:: edit_model_menu.png 144 144 145 145 and then one of the options 146 146 147 * *New* - to create a new custom model template148 * *Sum|Multi(p1,p2)* - to create a new model by summing/multiplying existing modelsin the model library149 * *Advanced* - to edit a new custom model147 * *New* - to create a custom model template with a help dialog 148 * *Sum|Multi(p1,p2)* - to create a custom model by summing/multiplying *existing models* in the model library 149 * *Advanced* - to create/edit a custom model in a Python shell 150 150 * *Delete* - to delete a custom model 151 * *Load* - to (re-)load custom models 151 152 152 153 New … … 184 185 ^^^^^^^^ 185 186 186 Selecting this option shows all the custom models in the plugin model folder 187 188 *C:\\Users\\ [username]\\.sasview\\plugin_models* - (on Windows)187 Selecting this option shows all the custom models in the plugin model folder, on Windows this is 188 189 *C:\\Users\\{username}\\.sasview\\plugin_models* 189 190 190 191 You can edit, modify, and save the Python code in any of these models using the 191 *Advanced Custom Model Editor*. 192 193 See :ref:`Writing_a_Plugin` for details on the plugin format. 194 195 *NB: Sum/Product models are still using the SasView 3.x model format. Unless 196 you are confident about what you are doing, it is recommended that you 197 only modify lines denoted with the ## <----- comments!* 198 199 When editing is complete, select *Run -> Compile* from the *Model Editor* menu bar. An 200 *Info* box will appear with the results of the compilation and model unit tests. The 201 model will only be usable if the tests 'pass'. 192 *Advanced Custom Model Editor*. Note that this is actually the same tool as the :ref:`Python_shell` . 193 194 For details of the SasView plugin model format see :ref:`Writing_a_Plugin` . 195 196 .. note:: Model files generated with the Sum/Multi option are still using the SasView 3.x model format. Unless you are confident about what you are doing, it is recommended that you only modify lines denoted with the ## <----- comments! 197 198 When editing is complete, select *Run* > *Check Model* from the *Advanced Custom Model Editor* menu bar. An *Info* box will appear with the results of the compilation and model unit tests. The model will only be usable if the tests 'pass'. 202 199 203 200 To use the model, go to the relevant *Fit Page*, select the *Customized Models* 204 201 category and then select the model from the drop-down menu. 205 202 206 *NB: Any changes to a custom model generated in this way only become effective after* 207 *it is re-selected from the model drop-down menu on the Fit Page.* 203 Any changes to a custom model generated in this way only become effective *after* it is re-selected from the model drop-down menu on the FitPage. 208 204 209 205 Delete … … 213 209 214 210 *NB: Custom models shipped with SasView cannot be removed in this way.* 211 212 Load 213 ^^^^ 214 215 This option loads (or re-loads) all models present in the plugin model folder. 215 216 216 217 .. ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
Note: See TracChangeset
for help on using the changeset viewer.