source: trunk/doc/expguierr.html @ 577

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

# on 2002/01/23 20:00:50, toby did:
clean up font references

  • Property rcs:author set to toby
  • Property rcs:date set to 2002/01/23 20:00:50
  • Property rcs:lines set to +8 -8
  • Property rcs:rev set to 1.9
  • Property rcs:state set to Exp
  • Property svn:keywords set to Author Date Revision Id
File size: 14.4 KB
3   <META NAME="Author" CONTENT="Brian H. Toby">
4   <title>EXPGUI Messages</title>
[517]5   <meta name="keywords" content="crystallography, Rietveld, diffraction,
9A:link {text-decoration:none}
10A:vlink {text-decoration:none}
14      topmargin="0" leftmargin="0" marginwidth="0" marginheight="0" 
15      text="#000000" link="#0033ff" vlink="#0033ff" alink="#0033ff">
18   include("/var/www/include/");
19   include("/var/www/include/");
21<blockquote><font face="arial, helvetica, sans-serif">
24<TR><TH><A  Href="expgui.html">EXPGUI top</A> 
[517]28<HR noshade width="75%" size="2" align="center">
[343]29EXPGUI Informational, Warning and Error Messages
[517]30<HR noshade width="75%" size="2" align="center">
32This page contains additional information about various warning
33and error screens that may occur in EXPGUI as well as descriptions
34for a number of utility functions.
[412]36<a name="Info"></a>
[343]37<H2>Informational Messages</H2>
[316]38<a name="Overwrite"></a>
39<h3>File has been modified...</h3> 
41This message occurs when EXPGUI detects that the experiment file has
42been changed by another program. (EXPGUI only tracks the file
43modification date, so that the file could have been opened for writing,
44but no actual changes were made.) This can be normal behavior -- for example
45after a refinement cycle has been run,
46or this can signal a problem, such as two people
47or sessions trying to edit the same .EXP file.
48This warning is made because a choice must be made: to keep the version
49currently displayed in EXPGUI, or to use the new version
50written by the other program.
51On UNIX, this message can be avoided by setting the
52<a href="expguic.html#Autoupdate">Autoupdate EXP</a> flag
53to "on" causes .EXP files to be loaded automatically after GSAS
[369]54programs are run, eliminating most occurrences where this message is
[316]55displayed, but with the disadvantage that a bad refinement run can not
56be reversed easily.
59If you choose to keep the
60currently displayed version and make changes and then save the file, either
61by using the File/Save menu option or by running a GSAS program,
[369]62the new version just written will be lost,
63if any changes are made in EXPGUI and are then saved.
64This can be useful -- to discard the
65results of a refinement that has gone awry --
66but in other cases may not be desirable.
68If you opt to load the new .EXP file, by pressing "Load new",
69the version currently displayed in
70the EXPGUI window will be lost. This is normally what you will want to do,
71but if you unsure, you can select "Continue with old", use File/Save As to
72save the version in EXPGUI and then use "EXPNAM" to load the new version,
73so they can be compared.
[369]75If changes have been made to the experiment file in EXPGUI
76since it was last saved, and
77the file is changed by an external program, the message "you have made
[316]78changes to this version" is added and a third button,
79"Save edited version", is shown. Under this circumstance, the usual action,
[369]80pressing "Load new" could result in valuable changes being lost. Pressing
[316]81"Save edited version" results brings you to the File/"Save as" menu,
82where the modified version of the experiment file in EXPGUI can be
83saved under a new name.
84<br clear=all>
[369]87<a name="lock"></a>
88<h3>Please wait while GSAS program finishes...</h3> 
[551]90A window labeled "<font face="courier">Please wait while GSAS program finishes."
91If a problem occurs, close the DOS box and press the "Continue" button</font> 
[369]92is created in Windows-9x while GSAS programs are run. As this window
[551]93is created, a "lock" file (<font face="courier">expgui.lck</font>) is also created. When the
[369]94DOS batch file running the GSAS program completes, this file is deleted.
[551]95The EXPGUI process waits until the <font face="courier">expgui.lck</font> lock file
[369]96is deleted. Should the DOS process crash before the file is deleted,
97the "Continue" button can be pressed. This causes
98EXPGUI to continue and deletes the lock file.
[316]99<br clear=all>
102<br clear=all>
[316]103<a name="Inputtitle"></a>
104<h3>Input a value for the title</h3> 
106A dialog with "Enter a value for the title for experiment..."  appears
107when a new experiment is created. Note that this title can be edited
108later on the
109<a href="expgui1.html">Least Squares Control Page</a>.
[316]114<br clear=all>
[343]115<a name="ChooseCIF"></a>
116<h3>Choose CIF Block</h3> 
[343]118When coordinates/cell parameters are read from a CIF, all blocks in the file
119are read. If more than block containing coordinates is found, a message
120saying "More than one block in CIF contains coordinates. Select the block to use."
121One must then select one of these blocks from the list of blocks.
122The blocks with coordinates are listed, both numbered and with the
123block (data_) name. The "CIF Browser"
124button can be pressed to view the data names and their values for each block.
[316]128<br clear=all>
[343]129<a name="open"></a>
130<h3>Open Experiment File</h3> 
[343]132The Open Experiment windows is displayed to select a
133experiment file to read or write, as well as a
134directory to use. When the message at the top reads
135"Select an experiment file to read" either an
136existing experiment file should be selected, or a new
137name may be typed in at the box at the bottom to enter
138a name manually. If the file is not found,
139you will be warned and given the option of
140creating a new experiment with that name.
142When the message at the top reads
143"Select an experiment file to create",
144typically after a "Save as" command,
145the directory may be changed, but typically
146a file name will be typed into the bottom box.
147If the file exists, you will be warned before the
148file is overwritten and you will have the option
149to enter a different file name.
[343]151Note that the files in the list can be sorted
152alphabetically or can be sorted by the date the
153experiment file was last modified, according to
154the checkbuttons to the upper right.
[463]156The "Include Archived Files" checkbox allows archive files
157named <xxxxxx>.Onn to be read
[412]158(see the
[463]159<A href="expguic.html#archive">archive option</A>).
160See the <A href="#LoadArchived">Load Archived File</A>, below, for
161further discussion.
[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.
[463]171This will cause the current version of the experiment file to be
172archived so that it is not lost. The selected [older] archived
173version will then be read and will be saved as the latest version of the
174experiment file.
175The other option is to save the experiment
[412]176under a new name.
[440]179<br clear=all>
180<a name="ExcludeRegion"></a>
181<h3>Exclude Data...<BR>Delete Region...</h3> 
183This message is shown before adding or deleting an excluded region using
184<a href="excledt.html">EXCLEDT</a> to confirm an action.
185See the <a href="excledt.html#AddRegion">discussion on Adding Regions</a>
186in EXCLEDT.
187Note that this
188confirmation message can be eliminated if desired, (see the
189EXCLEDT Options menu item <a href="excledt.html#prompt">Prompt on add/del</a>.)
190<br clear=all>
193<br clear=all>
194<a name="ProcessRegions"></a>
195<h3>The upper (lower) limit has changed...<BR>The excluded regions have changed...</h3>
197This message is shown
198if the upper data limit is raised (or d-min ls lowered) so that
199<a href="excledt.html">EXCLEDT</a> can display the data that have been added.
200It is also shown when
201<a href="excledt.html">EXCLEDT</a> exits so that the new data limits
202can be processed. GENLES will not run properly until POWPREF is run.
205<br clear=all>
206<a name="RegionTooBig"></a>
207<h3>The upper (lower) data point...</h3>
209This message is shown when the upper data limit (lower d-min limit)
210well outside the range of data.
211It is probably best to accept this suggestion. See the
212<a href="excledt.html#LimitTooHigh">discussion on data limits</a>
213in the EXCLEDT web page for more information.
216<br clear=all>
217<a name="ProcessUse"></a>
218<h3>You have changed histogram flags...</h3>
220This message is shown
221after changing histogram flags so that a different set of histograms
222will be included or excluded in a refinement.
223GENLES will not run properly until POWPREF is run.
[412]226<a name="Warn"></a>
[343]227<H2>Warning Messages</H2>
[316]229<br clear=all>
[343]230<a name="AbandonAtomConstraints"></a>
231<h3>Abandoning Constraint Editing</h3> 
[343]233If the "Cancel Changes" button is pressed when
[369]234a profile or atom constraint is being edited or created, a message saying
[343]235"Do you want to lose any changes made to this constraint?" is displayed, even
236if no changes have been made to the constraint. Changes are recorded only when the
237"Save" button is pressed.
[316]241<br clear=all>
[343]242<a name="OpenErr"></a>
243<h3>File ... does not exist in ...</h3> 
[343]245When an attempt is made to open a file that does not
246already exists, for example when the EXPNAM command
247is used, this warning is displayed. The answer can be
248"Select other" or "Create", where "Select other" will
249return you to a file selection dialog and "Create"
250will create a new dialog with this name.
253<br clear=all>
[343]254<a name="OverwriteErr"></a>
255<a name="OverwriteCnv"></a>
256<h3>File ... already exists in ... OK to overwrite?</h3> 
[343]258When an attempt is made to using the File/"Save As"
259command to write the current experiment file
260with a new name, but
261a file with the newly specified name already exists,
262this message is displayed. Choose "Select other"
263to specify a different file name or "Overwrite"
264to use this name in which case the older file
265is replaced.
[343]267A similar warning will occur in UNIX when converting files.
[369]268If the intended output file already exists,
[343]269this message is displayed. Choose "Cancel"
270to specify a different file name or "Overwrite"
271to use this name in which case the older file
272is replaced.
273This message can be seen in Windows when converting files,
274for slightly different reasons. When files are converted, the
275converted file keeps the same name as the original version. However,
276th original file is renamed to XXXX.ord, where XXXX.YYY is the
277original file name. If a file named XXXX.ord already exists, this message
278is displayed.
[412]281<br clear=all>
282<a name="NoValidHist"></a>
283<h3>No histograms are ready to plot. Run GENLES and try again.</h3> 
285This happens when LIVEPLOT is run but no valid histograms are available
286to plot. LIVEPLOT can plot histograms only when they have been processed by
287both POWPREF and GENLES.
290<a name="Error"></a>
[343]291<H2>Error Messages</H2>
[316]293<br clear=all>
[343]294<a name="NoPGPLOT"></a>
295<h3>Unable to find file GRFONT.DAT...</h3> 
[551]297The file <font face="courier">grfont.dat</font> is expected to be in the ...\gsas\fonts directory
298in DOS/Windows platforms and files <font face="courier">grfont.dat</font> and
299<font face="courier">pgxwin_server</font> are expected to be found in the .../gsas/pgl directory
[343]300in UNIX. If these files cannot be found, GSAS will not be able to produce
301graphics in programs such as POWPLOT, RAWPLOT,...
302If GSAS and EXPGUI are correctly installed this error will not occur
303(see the installation notes for
304<A HREF="expgui_Win_readme.html">Windows</A>
306<A HREF="expgui_Unix_readme.html">UNIX</A>.
310<br clear=all>
[343]311<a name="ConvNotFound"></a>
312<h3>Sorry, file ... not found in ...</h3> 
[369]314The specified input file was not found for conversion
317<br clear=all>
[343]318<a name="ConvSameName"></a>
319<h3>Sorry, filenames must differ</h3> 
321For UNIX file conversions, the input and output file names
[369]322must be different. You have specified the same name twice.
325<br clear=all>
[369]326<a name="NoRename"></a>
327<h3>Unable to rename <I>XXXXX</I>.LST</h3> 
329This message is displayed if the GSAS .LST file could not
330be renamed prior to running DISAGL in a separate window.
331On Windows it appears that LSTVIEW can prevent EXPGUI
332from renaming the .LST file. Either exit LSTVIEW
333while running DISAGL or reset the DISAGL option
334DISAGL so that output goes to the .LST file.
337<br clear=all>
[440]338<a name="OldEXPTOOL"></a>
339<h3>You must upgrade the EXPTOOL program...</h3> 
341The original version of the EXPTOOL program used within
342EXPGUI to add histograms does not work with dummy histograms.
343Versions of GSAS distributed prior to October 2001 do not contain this updated
344routine. A more recent version of the EXPTOOL program can
345be downloaded from
346<A Href="">
348<A Href="">
349</A> or
350<A Href="">
352Alternately, EXPEDT can be used to add dummy histograms.
355<br clear=all>
[495]356<a name="TCLDUMPError"></a>
357<h3>Error running TCLDUMP (LIVEPLOT or BKGEDIT)</h3> 
359The program TCLDUMP (or program HSTDMP if TCLDUMP is not found) is used to read
360the binary <I>expnam</I>.Pxx and <I>expnam</I>.Rxx files produced by
361POWPREF and GENLES so that refinement results can be plotted.
362If there is an error reading these files, an error message is produced
363reading "There was an error running the TCLDUMP program..."
364and the text of the error message reads something like
365"Invalid command name 'FORTRAN'".
366The most common reason for this error is that the
367<I>expnam</I>.Pxx and <I>expnam</I>.Rxx files do not exist (because you have
368not run POWPREF or have moved/renamed the .EXP file. It is possible,
369but less common for this error to occur if TCLDUMP tries to read files
370produced by an older version of GSAS (since the internal format of the
371binary files sometimes changes). If you see this message, run POWPREF & GENLES
372to force these files to be written. If the GSAS results can be plotted in
373POWPLOT, but not in LIVEPLOT or BKGEDIT, please contact Brian Toby at
374<a href="">Brian.Toby@NIST.GOV</a>.
377<br clear=all>
[316]378<a name=""></a>
385<TR><TH><A  Href="expgui.html">EXPGUI top</A> 
388<a href="">Brian Toby</a> (<a href="">Brian.Toby@NIST.GOV</a>)
390$Revision: 551 $ $Date: 2009-12-04 23:08:04 +0000 (Fri, 04 Dec 2009) $
Note: See TracBrowser for help on using the repository browser.