source: trunk/doc/expguierr.html @ 440

Last change on this file since 440 was 440, checked in by toby, 12 years ago

# on 2001/09/25 23:16:40, toby did:
document EXCLEDT and Dummy histogram warnings/error

  • Property rcs:author set to toby
  • Property rcs:date set to 2001/09/25 23:16:40
  • Property rcs:lines set to +66 -1
  • Property rcs:rev set to 1.5
  • Property rcs:state set to Exp
  • Property svn:keywords set to Author Date Revision Id
File size: 13.1 KB
3   <META NAME="Author" CONTENT="Brian H. Toby">
4   <title>EXPGUI Messages</title>
8<A HREF=>
9<IMG SRC="" 
10alt="Link to NIST Center for Neutron Research home page"
12<A HREF=>
13<IMG SRC="" 
14alt="Link to National Institute of Standards & Technology home page"
17<A Href="">
18<IMG SRC="tcltklogo100.gif" 
19alt="Link to Tcl/Tk information">
[343]21<br clear=all>
25<TR><TH><A  Href="expgui.html">EXPGUI top</A> 
[343]29EXPGUI Informational, Warning and Error Messages
31This page contains additional information about various warning
32and error screens that may occur in EXPGUI as well as descriptions
33for a number of utility functions.
[412]35<a name="Info"></a>
[343]36<H2>Informational Messages</H2>
[316]37<a name="Overwrite"></a>
38<h3>File has been modified...</h3> 
40This message occurs when EXPGUI detects that the experiment file has
41been changed by another program. (EXPGUI only tracks the file
42modification date, so that the file could have been opened for writing,
43but no actual changes were made.) This can be normal behavior -- for example
44after a refinement cycle has been run,
45or this can signal a problem, such as two people
46or sessions trying to edit the same .EXP file.
47This warning is made because a choice must be made: to keep the version
48currently displayed in EXPGUI, or to use the new version
49written by the other program.
50On UNIX, this message can be avoided by setting the
51<a href="expguic.html#Autoupdate">Autoupdate EXP</a> flag
52to "on" causes .EXP files to be loaded automatically after GSAS
[369]53programs are run, eliminating most occurrences where this message is
[316]54displayed, but with the disadvantage that a bad refinement run can not
55be reversed easily.
58If you choose to keep the
59currently displayed version and make changes and then save the file, either
60by using the File/Save menu option or by running a GSAS program,
[369]61the new version just written will be lost,
62if any changes are made in EXPGUI and are then saved.
63This can be useful -- to discard the
64results of a refinement that has gone awry --
65but in other cases may not be desirable.
67If you opt to load the new .EXP file, by pressing "Load new",
68the version currently displayed in
69the EXPGUI window will be lost. This is normally what you will want to do,
70but if you unsure, you can select "Continue with old", use File/Save As to
71save the version in EXPGUI and then use "EXPNAM" to load the new version,
72so they can be compared.
[369]74If changes have been made to the experiment file in EXPGUI
75since it was last saved, and
76the file is changed by an external program, the message "you have made
[316]77changes to this version" is added and a third button,
78"Save edited version", is shown. Under this circumstance, the usual action,
[369]79pressing "Load new" could result in valuable changes being lost. Pressing
[316]80"Save edited version" results brings you to the File/"Save as" menu,
81where the modified version of the experiment file in EXPGUI can be
82saved under a new name.
83<br clear=all>
[369]86<a name="lock"></a>
87<h3>Please wait while GSAS program finishes...</h3> 
[412]89A window labeled "<tt>Please wait while GSAS program finishes."
90If a problem occurs, close the DOS box and press the "Continue" button</tt> 
[369]91is created in Windows-9x while GSAS programs are run. As this window
92is created, a "lock" file (<tt>expgui.lck</tt>) is also created. When the
93DOS batch file running the GSAS program completes, this file is deleted.
94The EXPGUI process waits until the <tt>expgui.lck</tt> lock file
95is deleted. Should the DOS process crash before the file is deleted,
96the "Continue" button can be pressed. This causes
97EXPGUI to continue and deletes the lock file.
[316]98<br clear=all>
101<br clear=all>
[316]102<a name="Inputtitle"></a>
103<h3>Input a value for the title</h3> 
105A dialog with "Enter a value for the title for experiment..."  appears
106when a new experiment is created. Note that this title can be edited
107later on the
108<a href="expgui1.html">Least Squares Control Page</a>.
[316]113<br clear=all>
[343]114<a name="ChooseCIF"></a>
115<h3>Choose CIF Block</h3> 
[343]117When coordinates/cell parameters are read from a CIF, all blocks in the file
118are read. If more than block containing coordinates is found, a message
119saying "More than one block in CIF contains coordinates. Select the block to use."
120One must then select one of these blocks from the list of blocks.
121The blocks with coordinates are listed, both numbered and with the
122block (data_) name. The "CIF Browser"
123button can be pressed to view the data names and their values for each block.
[316]127<br clear=all>
[343]128<a name="open"></a>
129<h3>Open Experiment File</h3> 
[343]131The Open Experiment windows is displayed to select a
132experiment file to read or write, as well as a
133directory to use. When the message at the top reads
134"Select an experiment file to read" either an
135existing experiment file should be selected, or a new
136name may be typed in at the box at the bottom to enter
137a name manually. If the file is not found,
138you will be warned and given the option of
139creating a new experiment with that name.
141When the message at the top reads
142"Select an experiment file to create",
143typically after a "Save as" command,
144the directory may be changed, but typically
145a file name will be typed into the bottom box.
146If the file exists, you will be warned before the
147file is overwritten and you will have the option
148to enter a different file name.
[343]150Note that the files in the list can be sorted
151alphabetically or can be sorted by the date the
152experiment file was last modified, according to
153the checkbuttons to the upper right.
155In Unix another checkbox appears, offering the choice
156to "Include Archived Files." When this is checked, files
157named <xxxxxx>.EXP.nnn and <xxxxxx>.EXP.nnn.gz
158(see the
159<A href="expguic.html#archive">archive option</A>)
160are included in the file box. These files can be directly loaded.
161(Note the <A href="#LoadArchived">Load Archived File</A> discussion, below.
[412]164<br clear=all>
165<a name="LoadArchived"></a>
166<h3>Load Archived File</h3> 
168When a archived experiment file is read, the "Load Archived File"
169window is displayed to select the name to be used for the experiment.
170There are two choices. One is to reuse existing name.
171This will cause the archived experiment to overwrite the current version of
172the experiment file. The other option is to save the experiment
173under a new name.
[440]176<br clear=all>
177<a name="ExcludeRegion"></a>
178<h3>Exclude Data...<BR>Delete Region...</h3> 
180This message is shown before adding or deleting an excluded region using
181<a href="excledt.html">EXCLEDT</a> to confirm an action.
182See the <a href="excledt.html#AddRegion">discussion on Adding Regions</a>
183in EXCLEDT.
184Note that this
185confirmation message can be eliminated if desired, (see the
186EXCLEDT Options menu item <a href="excledt.html#prompt">Prompt on add/del</a>.)
187<br clear=all>
190<br clear=all>
191<a name="ProcessRegions"></a>
192<h3>The upper (lower) limit has changed...<BR>The excluded regions have changed...</h3>
194This message is shown
195if the upper data limit is raised (or d-min ls lowered) so that
196<a href="excledt.html">EXCLEDT</a> can display the data that have been added.
197It is also shown when
198<a href="excledt.html">EXCLEDT</a> exits so that the new data limits
199can be processed. GENLES will not run properly until POWPREF is run.
202<br clear=all>
203<a name="RegionTooBig"></a>
204<h3>The upper (lower) data point...</h3>
206This message is shown when the upper data limit (lower d-min limit)
207well outside the range of data.
208It is probably best to accept this suggestion. See the
209<a href="excledt.html#LimitTooHigh">discussion on data limits</a>
210in the EXCLEDT web page for more information.
213<br clear=all>
214<a name="ProcessUse"></a>
215<h3>You have changed histogram flags...</h3>
217This message is shown
218after changing histogram flags so that a different set of histograms
219will be included or excluded in a refinement.
220GENLES will not run properly until POWPREF is run.
[412]223<a name="Warn"></a>
[343]224<H2>Warning Messages</H2>
[316]226<br clear=all>
[343]227<a name="AbandonAtomConstraints"></a>
228<h3>Abandoning Constraint Editing</h3> 
[343]230If the "Cancel Changes" button is pressed when
[369]231a profile or atom constraint is being edited or created, a message saying
[343]232"Do you want to lose any changes made to this constraint?" is displayed, even
233if no changes have been made to the constraint. Changes are recorded only when the
234"Save" button is pressed.
[316]238<br clear=all>
[343]239<a name="OpenErr"></a>
240<h3>File ... does not exist in ...</h3> 
[343]242When an attempt is made to open a file that does not
243already exists, for example when the EXPNAM command
244is used, this warning is displayed. The answer can be
245"Select other" or "Create", where "Select other" will
246return you to a file selection dialog and "Create"
247will create a new dialog with this name.
250<br clear=all>
[343]251<a name="OverwriteErr"></a>
252<a name="OverwriteCnv"></a>
253<h3>File ... already exists in ... OK to overwrite?</h3> 
[343]255When an attempt is made to using the File/"Save As"
256command to write the current experiment file
257with a new name, but
258a file with the newly specified name already exists,
259this message is displayed. Choose "Select other"
260to specify a different file name or "Overwrite"
261to use this name in which case the older file
262is replaced.
[343]264A similar warning will occur in UNIX when converting files.
[369]265If the intended output file already exists,
[343]266this message is displayed. Choose "Cancel"
267to specify a different file name or "Overwrite"
268to use this name in which case the older file
269is replaced.
270This message can be seen in Windows when converting files,
271for slightly different reasons. When files are converted, the
272converted file keeps the same name as the original version. However,
273th original file is renamed to XXXX.ord, where XXXX.YYY is the
274original file name. If a file named XXXX.ord already exists, this message
275is displayed.
[412]278<br clear=all>
279<a name="NoValidHist"></a>
280<h3>No histograms are ready to plot. Run GENLES and try again.</h3> 
282This happens when LIVEPLOT is run but no valid histograms are available
283to plot. LIVEPLOT can plot histograms only when they have been processed by
284both POWPREF and GENLES.
287<a name="Error"></a>
[343]288<H2>Error Messages</H2>
[316]290<br clear=all>
[343]291<a name="NoPGPLOT"></a>
292<h3>Unable to find file GRFONT.DAT...</h3> 
[343]294The file <tt>grfont.dat</tt> is expected to be in the ...\gsas\fonts directory
295in DOS/Windows platforms and files <tt>grfont.dat</tt> and
296<tt>pgxwin_server</tt> are expected to be found in the .../gsas/pgl directory
297in UNIX. If these files cannot be found, GSAS will not be able to produce
298graphics in programs such as POWPLOT, RAWPLOT,...
299If GSAS and EXPGUI are correctly installed this error will not occur
300(see the installation notes for
301<A HREF="expgui_Win_readme.html">Windows</A>
303<A HREF="expgui_Unix_readme.html">UNIX</A>.
307<br clear=all>
[343]308<a name="ConvNotFound"></a>
309<h3>Sorry, file ... not found in ...</h3> 
[369]311The specified input file was not found for conversion
314<br clear=all>
[343]315<a name="ConvSameName"></a>
316<h3>Sorry, filenames must differ</h3> 
318For UNIX file conversions, the input and output file names
[369]319must be different. You have specified the same name twice.
322<br clear=all>
[369]323<a name="NoRename"></a>
324<h3>Unable to rename <I>XXXXX</I>.LST</h3> 
326This message is displayed if the GSAS .LST file could not
327be renamed prior to running DISAGL in a separate window.
328On Windows it appears that LSTVIEW can prevent EXPGUI
329from renaming the .LST file. Either exit LSTVIEW
330while running DISAGL or reset the DISAGL option
331DISAGL so that output goes to the .LST file.
334<br clear=all>
[440]335<a name="OldEXPTOOL"></a>
336<h3>You must upgrade the EXPTOOL program...</h3> 
338The original version of the EXPTOOL program used within
339EXPGUI to add histograms does not work with dummy histograms.
340Versions of GSAS distributed prior to October 2001 do not contain this updated
341routine. A more recent version of the EXPTOOL program can
342be downloaded from
343<A Href="">
345<A Href="">
346</A> or
347<A Href="">
349Alternately, EXPEDT can be used to add dummy histograms.
352<br clear=all>
[316]353<a name=""></a>
360<TR><TH><A  Href="expgui.html">EXPGUI top</A> 
363<a href="">Brian Toby</a> (<a href="">Brian.Toby@NIST.GOV</a>)
365$Revision: 440 $ $Date: 2009-12-04 23:06:12 +0000 (Fri, 04 Dec 2009) $
Note: See TracBrowser for help on using the repository browser.