Changeset 343

Timestamp:

Dec 4, 2009 5:04:28 PM (14 years ago)

Author:

toby

Message:

# on 2000/10/18 00:11:17, toby did:
move utilites
organize

File:

• trunk/doc/expguierr.html (modified) (5 diffs, 3 props)

trunk/doc/expguierr.html

@@ -19 +19 @@
 alt="Link to Tcl/Tk information">
 </CENTER></A>
+<br clear=all>
 <hr>
 
@@ -26 +27 @@
 
 <center><h1>
-EXPGUI Dialogs, Warnings and Error Messages
+EXPGUI Informational, Warning and Error Messages
 </h1></center>
 This page contains additional information about various warning 
@@ -32 +33 @@
 for a number of utility functions.
 
+<H2>Informational Messages</H2>
 <a name="Overwrite"></a>
 <h3>File has been modified...</h3> 
@@ -87 +89 @@
 </DL></DL>
 
-<br clear=all>
-<a name="ConvertUnix"></a>
-<h3>Unix File Conversions</h3> 
-<DL><DL>
-In UNIX, GSAS data, experiment and instrument parameter files are expected to 
-have a format with exactly 80 characters per line and no line
-separators (no carriage returns or linefeeds). Files in this format
-are called "Direct Access". Normal UNIX files may have any number 
-of characters per line and every line is terminated by a line feed character. 
-These files are called "sequential". 
-EXPGUI uses the convention that all uppercase is used for Direct Access files
-while all lowercase is used for sequential files.
-<P>
-The Unix File Conversion menu is used to convert sequential files to 
-direct access for use in GSAS or to convert direct access files to 
-sequential, for use in standard UNIX programs, such as editors or e-mail.
-</DL></DL>
-
-<br clear=all>
-<a name="ConvertWin"></a>
-<h3>Windows File Conversions</h3> 
-<DL><DL>
-In Windows, GSAS data, experiment and instrument parameter files are
-expected to have a format with exactly 80 characters per line followed 
-by a carriage returns and a linefeed (82 characters total per line). 
-Files in this format can be read in "Direct Access" mode. The Convert menu
-in windows can be used to convert files into this format (it can also 
-convert UNIX direct access files correctly). The original version of the 
-file is retained and renamed.
-<P>
-</DL></DL>
-
-<br clear=all>
-<a name="Composition"></a>
-<h3>Compute Composition</h3> 
-<DL><DL>
-The composition box shows the unit cell and asymmetric unit composition
-for all phases in a material. Site multiplicities and occupancies are 
-taken into account.
-</DL></DL>
-
-<br clear=all>
-<a name="ExportMSI"></a>
-<h3>Export coordinates in MSI .xtl format</h3> 
-<DL><DL>
-The Export/exp2xtl routine writes a .xtl file, as is used in Insight-II and
-Cerius2 (Molecular Simulations, Inc.). Note that spacegroups are not named 
-exactly the same in the two programs and the origin may need to be specified
-as "origin 2", for spacegroups where the center of symmetry is not at the 
-origin. It is up to the user to get things right.
-</DL></DL>
-
-<br clear=all>
-<a name="DeleteHistoryRecords"></a>
-<h3>Delete History Records</h3> 
-<DL><DL>
-Every time a GSAS program (including EXPGUI) is run, an entry is added to 
-the "history records" in the .EXP file. After 999 entries have been written,
-no more can be added to the file. Further, reading large numbers of history
-records can slow the GSAS programs 
-(this is less of a problem on faster computers). For these reasons, it may be 
-a good idea to prune the older history records from the file. If more than 100
-history records are found in an experiment file, EXPGUI suggests that the
-older history entries be deleted. Alternately the File/EraseHistory command
-can be used to invoke the this option.
-<P>
-On the dialog the number of history records to be retained is specified. 
-Also, after records have been deleted, the remaining records can be renumbered
-starting with 1, so that the 999 record limit is not reached.
-</DL></DL>
-
-<br clear=all>
-<a name="AbandonAtomConstraints"></a>
-<h3>Abandoning Constraint Editing</h3> 
-<DL><DL>
-If the "Cancel Changes" button is pressed when
-a profile or atom contraint is being edited or created, a message saying 
-"Do you want to lose any changes made to this constraint?" is displayed, even
-if no changes have been made to the constraint. Changes are recorded only when the
-"Save" button is pressed.
-</DL></DL>
+
 
 <br clear=all>
@@ -182 +104 @@
 </DL></DL>
 
+
+<br clear=all>
+<a name="open"></a>
+<h3>Open Experiment File</h3> 
+<DL><DL>
+The Open Experiment windows is displayed to select a
+experiment file to read or write, as well as a 
+directory to use. When the message at the top reads 
+"Select an experiment file to read" either an
+existing experiment file should be selected, or a new
+name may be typed in at the box at the bottom to enter
+a name manually. If the file is not found, 
+you will be warned and given the option of 
+creating a new experiment with that name.
+
+When the message at the top reads 
+"Select an experiment file to create",
+typically after a "Save as" command, 
+the directory may be changed, but typically 
+a file name will be typed into the bottom box.
+If the file exists, you will be warned before the
+file is overwritten and you will have the option 
+to enter a different file name.
+
+Note that the files in the list can be sorted 
+alphabetically or can be sorted by the date the
+experiment file was last modified, according to 
+the checkbuttons to the upper right.
+</DL></DL>
+
+<H2>Warning Messages</H2>
+
+<br clear=all>
+<a name="AbandonAtomConstraints"></a>
+<h3>Abandoning Constraint Editing</h3> 
+<DL><DL>
+If the "Cancel Changes" button is pressed when
+a profile or atom contraint is being edited or created, a message saying 
+"Do you want to lose any changes made to this constraint?" is displayed, even
+if no changes have been made to the constraint. Changes are recorded only when the
+"Save" button is pressed.
+</DL></DL>
+
+
+<br clear=all>
+<a name="OpenErr"></a>
+<h3>File ... does not exist in ...</h3> 
+<DL><DL>
+When an attempt is made to open a file that does not
+already exists, for example when the EXPNAM command
+is used, this warning is displayed. The answer can be 
+"Select other" or "Create", where "Select other" will
+return you to a file selection dialog and "Create" 
+will create a new dialog with this name.
+</DL></DL>
+
+<br clear=all>
+<a name="OverwriteErr"></a>
+<a name="OverwriteCnv"></a>
+<h3>File ... already exists in ... OK to overwrite?</h3> 
+<DL><DL>
+When an attempt is made to using the File/"Save As" 
+command to write the current experiment file 
+with a new name, but 
+a file with the newly specified name already exists,
+this message is displayed. Choose "Select other"
+to specify a different file name or "Overwrite"
+to use this name in which case the older file 
+is replaced.
+<P>
+A similar warning will occur in UNIX when converting files.
+If the intended output filealready exists,
+this message is displayed. Choose "Cancel"
+to specify a different file name or "Overwrite"
+to use this name in which case the older file 
+is replaced. 
+This message can be seen in Windows when converting files, 
+for slightly different reasons. When files are converted, the 
+converted file keeps the same name as the original version. However,
+th original file is renamed to XXXX.ord, where XXXX.YYY is the 
+original file name. If a file named XXXX.ord already exists, this message
+is displayed.
+</DL></DL>
+
+<H2>Error Messages</H2>
+
+<br clear=all>
+<a name="NoPGPLOT"></a>
+<h3>Unable to find file GRFONT.DAT...</h3> 
+<DL><DL>
+The file <tt>grfont.dat</tt> is expected to be in the ...\gsas\fonts directory
+in DOS/Windows platforms and files <tt>grfont.dat</tt> and 
+<tt>pgxwin_server</tt> are expected to be found in the .../gsas/pgl directory
+in UNIX. If these files cannot be found, GSAS will not be able to produce 
+graphics in programs such as POWPLOT, RAWPLOT,...
+If GSAS and EXPGUI are correctly installed this error will not occur
+(see the installation notes for 
+<A HREF="expgui_Win_readme.html">Windows</A>
+and 
+<A HREF="expgui_Unix_readme.html">UNIX</A>.
+
+</DL></DL>
+
+<br clear=all>
+<a name="ConvNotFound"></a>
+<h3>Sorry, file ... not found in ...</h3> 
+<DL><DL>
+The specifed input file was not found for conversion
+</DL></DL>
+
+<br clear=all>
+<a name="ConvSameName"></a>
+<h3>Sorry, filenames must differ</h3> 
+<DL><DL>
+For UNIX file conversions, the input and output file names
+must be different. You have specifed the same name twice.
+</DL></DL>
+
 <br clear=all>
 <a name=""></a>