Changeset 524

Timestamp:

Dec 4, 2009 5:07:36 PM (14 years ago)

Author:

toby

Message:

# on 2002/01/22 21:08:12, toby did:
add coordinate export section
minor coord. input section changes

File:

• trunk/doc/expgui_cfg.html (modified) (6 diffs, 3 props)

trunk/doc/expgui_cfg.html

@@ -97 +97 @@
 </PRE>
 means that "runGSASwEXP powpref" will be invoked when powpref is invoked.
-. For example, when powpref is selected, the tcl command
+For example, when powpref is selected, the tcl command
 "runGSASwEXP $cmd" is invoked, where variable cmd is set to "powpref".
 <DT><TT>expgui(buttonlist)</TT><DD>
@@ -198 +198 @@
 <IMG SRC="new.gif" HEIGHT=13 WIDTH=36 alt="New!">
 </H3>
-Currently two formats are supported, the Crystallographic Information File (CIF)
-and .CEL files from PowderCell.
+See the <A HREF="expgui.html#import">coordinate import discussion</A> 
+for description of available formats.
 It is possible to define new formats for EXPGUI to use for importing
-phase/coordinate information. This is done by creating a file named 
+phase/coordinate information. This is done by creating a file 
+containing the appropriate Tcl code to read this file type. 
+All that is needed to cause the code to be incorporated into
+EXPGUI is to name it
 <TT>import_</TT><I>xxxx</I><TT>.tcl</TT> (where <I>xxxx</I> is arbitrary)
-in the EXPGUI directory. See the file <TT>import_cell.tcl</TT> as an example.
-
-The file must contain four items:
+and place it in the EXPGUI directory. All files with 
+such names are read when EXPGUI is started. 
+
+The <TT>import_</TT> file must contain four items:
 <UL>
 <LI>
@@ -294 +298 @@
 </DL></DL>
 </OL>
+See the file <TT>import_cell.tcl</TT> as an example for how this code
+is written.
 
 </UL>
+<HR><H3><A NAME="export">Coordinate Export routines for EXPGUI</A>
+<IMG SRC="new.gif" HEIGHT=13 WIDTH=36 alt="New!">
+</H3>
+See the <A HREF="expgui.html#export">coordinate export discussion</A> 
+for description of available formats.
+It is possible to define new formats for EXPGUI to use for exporting
+phase/coordinate information. This is done by creating a file 
+containing the appropriate Tcl code to read this file type. 
+All that is needed to cause the code to be incorporated into
+EXPGUI is to name it
+<TT>export_</TT><I>xxxx</I><TT>.tcl</TT> (where <I>xxxx</I> is arbitrary)
+and place it in the EXPGUI directory. All files with 
+such names are read when EXPGUI the Import/Export=>"Coord Export" submenu 
+is first invoked.
+
+The <TT>export_</TT> file must define two variables:
+<DL><DL>
+<DT>label<DD>
+This defines the text that appears on the submenu. For example:
+<PRE>
+        set label "MSI .xtl format"
+</PRE>
+<DT>action<DD>
+This defines the Tcl routine that will be used to 
+<PRE>
+        set action exp2xtl
+</PRE>
+</DL></DL>
+See the file <TT>export_example.example</TT>, as well as the 
+<TT>export_*.tcl</TT> files
+as examples for how this
+sort of routine is written.
+
 <HR><H3>LSTVIEW</H3>
 The <TT>localconfig</TT> and <TT>.gsas_config</TT> files are read, if present.
@@ -310 +349 @@
 the start of the program. The default is ~1Mb 
 for UNIX systems and ~200K for Windows.
+<DT><TT>txtvw(plotvars)</TT><DD>
+If txtvx(plotvars) is 1, a plot window is created for plotting of 
+R-factors and parameter shifts as a function of cycle number.
+Note that the summary of shifts must be displayed, in order
+to plot parameter shifts. If this variable is set to 0, the
+plot window is not created and LSTVIEW runs a bit faster.
 </DL></DL>
 
@@ -328 +373 @@
 </DL></DL>
 
-One additional variable is present that I don't suggest using at present:
-<UL>
-<LI>plotvars: I am in the process of developing code that tracks 
-and plots shifts and R values as a function cycle number. Setting plotvars to 1
-allows this code to be tested.
-</LI></UL>
-
 <hr><H3>LIVEPLOT</H3><A NAME="liveplot"></A>
 A description of the customization options for LIVEPLOT can be 
@@ -343 +381 @@
 
 <HR>
+<a name="WIDPLT"></a>
 <H3>WIDPLT</H3>
 The widplt script is used to display the FWHM for one or more histograms