- Timestamp:
- Apr 12, 2018 4:43:24 PM (6 years ago)
- Location:
- Tutorials
- Files:
-
- 53 added
- 2 edited
- 1 moved
Legend:
- Unmodified
- Added
- Removed
-
Tutorials/PythonScript/Scripting.htm
r3218 r3342 128 128 access a GSAS-II project, which is done with a call to 129 129 <TT>GSASIIscriptable.G2Project()</tt>. This can be done in one of two 130 ways: a call with <tt>G2sc.G2Project( filename=</tt><I>file</I><tt>)</tt> creates a new130 ways: a call with <tt>G2sc.G2Project(newgpx=</tt><I>file</I><tt>)</tt> creates a new 131 131 (empty) project, while a call with 132 132 <tt>G2sc.G2Project(gpxfile=</tt><I>file</I><tt>)</tt> opens and … … 138 138 <P> 139 139 In this example, we create a new project by using the 140 <tt> filename=</tt><I>file</I> argument with this code:140 <tt>newgpx=</tt><I>file</I> argument with this code: 141 141 142 142 <blockquote><textarea rows="3" cols="70" readonly> 143 143 # create a project with a default project name 144 gpx = G2sc.G2Project( filename='PbSO4.gpx')</textarea></blockquote>144 gpx = G2sc.G2Project(newgpx='PbSO4.gpx')</textarea></blockquote> 145 145 146 146 Note that the file will not actually be created until an operation … … 583 583 584 584 <blockquote><textarea rows="4" cols="70" readonly> 585 gpx = G2sc.G2Project( filename='PbSO4sim.gpx') # create a project585 gpx = G2sc.G2Project(newgpx='PbSO4sim.gpx') # create a project 586 586 # step 1, setup: add a phase to the project 587 587 phase0 = gpx.add_phase(os.path.join(datadir,"PbSO4-Wyckoff.cif"), … … 655 655 <hr> 656 656 <address></address> 657 <!-- hhmts start -->Last modified: Thu Jan 11 09:41:57CST 2018 <!-- hhmts end -->657 <!-- hhmts start -->Last modified: Mon Feb 19 14:53:43 CST 2018 <!-- hhmts end --> 658 658 </body> </html> -
Tutorials/Simulation/SimTutorial.htm
r3237 r3342 666 666 <p class=MsoNormal><span style='font-size:12.0pt;mso-fareast-font-family:"Times New Roman"; 667 667 mso-bidi-font-family:"Times New Roman"'>Note that a new histogram is now added 668 to the data tree, as below. <o:p></o:p></span></p> 668 to the data tree, as below. (Note the "Edit range" button which can be 669 used to change the values entered on the previous dialog). 670 <o:p></o:p></span></p> 669 671 670 672 <p class=MsoNormal><span style='font-size:12.0pt;mso-fareast-font-family:"Times New Roman"; … … 838 840 mso-bidi-font-family:"Times New Roman"'>A refinement computation is needed to 839 841 cause the pattern to be simulated. When a pattern is first simulated, the 840 observed pattern is set to the computed pattern. This means that it is actually 841 possible to optimize any parameters that are selected to be refined. There is 842 no reason to actually do this, so we will turn off optimization by setting the 843 number of cycles to zero. Click on the Controls data tree entry and set the Max 842 observed pattern is set to the computed pattern (this can be reset by 843 using the "Edit range" button when the histogram data tree item is 844 selected. This means that it is actually 845 possible to optimize any parameters that are selected to be refined, 846 which can be used to test the sensitivity of different models refined 847 against a 848 simulated dataset. In this case we only need to compute the simulated 849 pattern, so we will turn off optimization by setting the 850 number of cycles to zero. Do this by clicking on the Controls data tree entry and set the Max 844 851 cycles value to 0 using the pull-down menu:<o:p></o:p></span></p> 845 852
Note: See TracChangeset
for help on using the changeset viewer.