source: trunk/doc/expguierr.html @ 502

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

# on 2001/12/16 18:15:31, toby did:
liveplot: explain the "FORTRAN" error

  • Property rcs:author set to toby
  • Property rcs:date set to 2001/12/16 18:15:31
  • Property rcs:lines set to +23 -1
  • Property rcs:rev set to 1.7
  • Property rcs:state set to Exp
  • Property svn:keywords set to Author Date Revision Id
File size: 14.2 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.
[463]155The "Include Archived Files" checkbox allows archive files
156named <xxxxxx>.Onn to be read
[412]157(see the
[463]158<A href="expguic.html#archive">archive option</A>).
159See the <A href="#LoadArchived">Load Archived File</A>, below, for
160further discussion.
[412]163<br clear=all>
164<a name="LoadArchived"></a>
165<h3>Load Archived File</h3> 
167When a archived experiment file is read, the "Load Archived File"
168window is displayed to select the name to be used for the experiment.
169There are two choices. One is to reuse existing name.
[463]170This will cause the current version of the experiment file to be
171archived so that it is not lost. The selected [older] archived
172version will then be read and will be saved as the latest version of the
173experiment file.
174The other option is to save the experiment
[412]175under a new name.
[440]178<br clear=all>
179<a name="ExcludeRegion"></a>
180<h3>Exclude Data...<BR>Delete Region...</h3> 
182This message is shown before adding or deleting an excluded region using
183<a href="excledt.html">EXCLEDT</a> to confirm an action.
184See the <a href="excledt.html#AddRegion">discussion on Adding Regions</a>
185in EXCLEDT.
186Note that this
187confirmation message can be eliminated if desired, (see the
188EXCLEDT Options menu item <a href="excledt.html#prompt">Prompt on add/del</a>.)
189<br clear=all>
192<br clear=all>
193<a name="ProcessRegions"></a>
194<h3>The upper (lower) limit has changed...<BR>The excluded regions have changed...</h3>
196This message is shown
197if the upper data limit is raised (or d-min ls lowered) so that
198<a href="excledt.html">EXCLEDT</a> can display the data that have been added.
199It is also shown when
200<a href="excledt.html">EXCLEDT</a> exits so that the new data limits
201can be processed. GENLES will not run properly until POWPREF is run.
204<br clear=all>
205<a name="RegionTooBig"></a>
206<h3>The upper (lower) data point...</h3>
208This message is shown when the upper data limit (lower d-min limit)
209well outside the range of data.
210It is probably best to accept this suggestion. See the
211<a href="excledt.html#LimitTooHigh">discussion on data limits</a>
212in the EXCLEDT web page for more information.
215<br clear=all>
216<a name="ProcessUse"></a>
217<h3>You have changed histogram flags...</h3>
219This message is shown
220after changing histogram flags so that a different set of histograms
221will be included or excluded in a refinement.
222GENLES will not run properly until POWPREF is run.
[412]225<a name="Warn"></a>
[343]226<H2>Warning Messages</H2>
[316]228<br clear=all>
[343]229<a name="AbandonAtomConstraints"></a>
230<h3>Abandoning Constraint Editing</h3> 
[343]232If the "Cancel Changes" button is pressed when
[369]233a profile or atom constraint is being edited or created, a message saying
[343]234"Do you want to lose any changes made to this constraint?" is displayed, even
235if no changes have been made to the constraint. Changes are recorded only when the
236"Save" button is pressed.
[316]240<br clear=all>
[343]241<a name="OpenErr"></a>
242<h3>File ... does not exist in ...</h3> 
[343]244When an attempt is made to open a file that does not
245already exists, for example when the EXPNAM command
246is used, this warning is displayed. The answer can be
247"Select other" or "Create", where "Select other" will
248return you to a file selection dialog and "Create"
249will create a new dialog with this name.
252<br clear=all>
[343]253<a name="OverwriteErr"></a>
254<a name="OverwriteCnv"></a>
255<h3>File ... already exists in ... OK to overwrite?</h3> 
[343]257When an attempt is made to using the File/"Save As"
258command to write the current experiment file
259with a new name, but
260a file with the newly specified name already exists,
261this message is displayed. Choose "Select other"
262to specify a different file name or "Overwrite"
263to use this name in which case the older file
264is replaced.
[343]266A similar warning will occur in UNIX when converting files.
[369]267If the intended output file already exists,
[343]268this message is displayed. Choose "Cancel"
269to specify a different file name or "Overwrite"
270to use this name in which case the older file
271is replaced.
272This message can be seen in Windows when converting files,
273for slightly different reasons. When files are converted, the
274converted file keeps the same name as the original version. However,
275th original file is renamed to XXXX.ord, where XXXX.YYY is the
276original file name. If a file named XXXX.ord already exists, this message
277is displayed.
[412]280<br clear=all>
281<a name="NoValidHist"></a>
282<h3>No histograms are ready to plot. Run GENLES and try again.</h3> 
284This happens when LIVEPLOT is run but no valid histograms are available
285to plot. LIVEPLOT can plot histograms only when they have been processed by
286both POWPREF and GENLES.
289<a name="Error"></a>
[343]290<H2>Error Messages</H2>
[316]292<br clear=all>
[343]293<a name="NoPGPLOT"></a>
294<h3>Unable to find file GRFONT.DAT...</h3> 
[343]296The file <tt>grfont.dat</tt> is expected to be in the ...\gsas\fonts directory
297in DOS/Windows platforms and files <tt>grfont.dat</tt> and
298<tt>pgxwin_server</tt> are expected to be found in the .../gsas/pgl directory
299in UNIX. If these files cannot be found, GSAS will not be able to produce
300graphics in programs such as POWPLOT, RAWPLOT,...
301If GSAS and EXPGUI are correctly installed this error will not occur
302(see the installation notes for
303<A HREF="expgui_Win_readme.html">Windows</A>
305<A HREF="expgui_Unix_readme.html">UNIX</A>.
309<br clear=all>
[343]310<a name="ConvNotFound"></a>
311<h3>Sorry, file ... not found in ...</h3> 
[369]313The specified input file was not found for conversion
316<br clear=all>
[343]317<a name="ConvSameName"></a>
318<h3>Sorry, filenames must differ</h3> 
320For UNIX file conversions, the input and output file names
[369]321must be different. You have specified the same name twice.
324<br clear=all>
[369]325<a name="NoRename"></a>
326<h3>Unable to rename <I>XXXXX</I>.LST</h3> 
328This message is displayed if the GSAS .LST file could not
329be renamed prior to running DISAGL in a separate window.
330On Windows it appears that LSTVIEW can prevent EXPGUI
331from renaming the .LST file. Either exit LSTVIEW
332while running DISAGL or reset the DISAGL option
333DISAGL so that output goes to the .LST file.
336<br clear=all>
[440]337<a name="OldEXPTOOL"></a>
338<h3>You must upgrade the EXPTOOL program...</h3> 
340The original version of the EXPTOOL program used within
341EXPGUI to add histograms does not work with dummy histograms.
342Versions of GSAS distributed prior to October 2001 do not contain this updated
343routine. A more recent version of the EXPTOOL program can
344be downloaded from
345<A Href="">
347<A Href="">
348</A> or
349<A Href="">
351Alternately, EXPEDT can be used to add dummy histograms.
354<br clear=all>
[495]355<a name="TCLDUMPError"></a>
356<h3>Error running TCLDUMP (LIVEPLOT or BKGEDIT)</h3> 
358The program TCLDUMP (or program HSTDMP if TCLDUMP is not found) is used to read
359the binary <I>expnam</I>.Pxx and <I>expnam</I>.Rxx files produced by
360POWPREF and GENLES so that refinement results can be plotted.
361If there is an error reading these files, an error message is produced
362reading "There was an error running the TCLDUMP program..."
363and the text of the error message reads something like
364"Invalid command name 'FORTRAN'".
365The most common reason for this error is that the
366<I>expnam</I>.Pxx and <I>expnam</I>.Rxx files do not exist (because you have
367not run POWPREF or have moved/renamed the .EXP file. It is possible,
368but less common for this error to occur if TCLDUMP tries to read files
369produced by an older version of GSAS (since the internal format of the
370binary files sometimes changes). If you see this message, run POWPREF & GENLES
371to force these files to be written. If the GSAS results can be plotted in
372POWPLOT, but not in LIVEPLOT or BKGEDIT, please contact Brian Toby at
373<a href="">Brian.Toby@NIST.GOV</a>.
376<br clear=all>
[316]377<a name=""></a>
384<TR><TH><A  Href="expgui.html">EXPGUI top</A> 
387<a href="">Brian Toby</a> (<a href="">Brian.Toby@NIST.GOV</a>)
389$Revision: 495 $ $Date: 2009-12-04 23:07:07 +0000 (Fri, 04 Dec 2009) $
Note: See TracBrowser for help on using the repository browser.