| 1 | <html> |
|---|
| 2 | <head> |
|---|
| 3 | <title>EXPGUI Messages</title> |
|---|
| 4 | <meta name="keywords" content="crystallography, Rietveld, diffraction, |
|---|
| 5 | GSAS, EXPGUI"> |
|---|
| 6 | </HEAD> |
|---|
| 7 | <style> |
|---|
| 8 | A:link {text-decoration:none} |
|---|
| 9 | A:vlink {text-decoration:none} |
|---|
| 10 | </style> |
|---|
| 11 | |
|---|
| 12 | <BODY BGCOLOR="#FFFFFF" |
|---|
| 13 | topmargin="0" leftmargin="0" marginwidth="0" marginheight="0" |
|---|
| 14 | text="#000000" link="#0033ff" vlink="#0033ff" alink="#0033ff"> |
|---|
| 15 | |
|---|
| 16 | <? |
|---|
| 17 | include("/var/www/include/navigation.inc"); |
|---|
| 18 | include("/var/www/include/utility.inc"); |
|---|
| 19 | ?> |
|---|
| 20 | <blockquote><font face="arial, helvetica, sans-serif"> |
|---|
| 21 | |
|---|
| 22 | <TABLE BORDER BGCOLOR="#FFFF40" ALIGN=RIGHT> |
|---|
| 23 | <TR><TH><A Href="expgui.html">EXPGUI top</A> |
|---|
| 24 | </TH></TR></TABLE><BR CLEAR=ALL> |
|---|
| 25 | |
|---|
| 26 | <center><h1> |
|---|
| 27 | <HR noshade width="75%" size="2" align="center"> |
|---|
| 28 | EXPGUI Informational, Warning and Error Messages |
|---|
| 29 | <HR noshade width="75%" size="2" align="center"> |
|---|
| 30 | </h1></center> |
|---|
| 31 | This page contains additional information about various warning |
|---|
| 32 | and error screens that may occur in EXPGUI as well as descriptions |
|---|
| 33 | for a number of utility functions. |
|---|
| 34 | |
|---|
| 35 | <a name="Info"></a> |
|---|
| 36 | <H2>Informational Messages</H2> |
|---|
| 37 | <a name="Overwrite"></a> |
|---|
| 38 | <h3>File has been modified...</h3> |
|---|
| 39 | <DL><DL> |
|---|
| 40 | This message occurs when EXPGUI detects that the experiment file has |
|---|
| 41 | been changed by another program. (EXPGUI only tracks the file |
|---|
| 42 | modification date, so that the file could have been opened for writing, |
|---|
| 43 | but no actual changes were made.) This can be normal behavior -- for example |
|---|
| 44 | after a refinement cycle has been run, |
|---|
| 45 | or this can signal a problem, such as two people |
|---|
| 46 | or sessions trying to edit the same .EXP file. |
|---|
| 47 | This warning is made because a choice must be made: to keep the version |
|---|
| 48 | currently displayed in EXPGUI, or to use the new version |
|---|
| 49 | written by the other program. |
|---|
| 50 | On UNIX, this message can be avoided by setting the |
|---|
| 51 | <a href="expguic.html#Autoupdate">Autoupdate EXP</a> flag |
|---|
| 52 | to "on" causes .EXP files to be loaded automatically after GSAS |
|---|
| 53 | programs are run, eliminating most occurrences where this message is |
|---|
| 54 | displayed, but with the disadvantage that a bad refinement run can not |
|---|
| 55 | be reversed easily. |
|---|
| 56 | <UL> |
|---|
| 57 | <LI> |
|---|
| 58 | If you choose to keep the |
|---|
| 59 | currently displayed version and make changes and then save the file, either |
|---|
| 60 | by using the File/Save menu option or by running a GSAS program, |
|---|
| 61 | the new version just written will be lost, |
|---|
| 62 | if any changes are made in EXPGUI and are then saved. |
|---|
| 63 | This can be useful -- to discard the |
|---|
| 64 | results of a refinement that has gone awry -- |
|---|
| 65 | but in other cases may not be desirable. |
|---|
| 66 | <LI> |
|---|
| 67 | If you opt to load the new .EXP file, by pressing "Load new", |
|---|
| 68 | the version currently displayed in |
|---|
| 69 | the EXPGUI window will be lost. This is normally what you will want to do, |
|---|
| 70 | but if you unsure, you can select "Continue with old", use File/Save As to |
|---|
| 71 | save the version in EXPGUI and then use "EXPNAM" to load the new version, |
|---|
| 72 | so they can be compared. |
|---|
| 73 | </UL> |
|---|
| 74 | If changes have been made to the experiment file in EXPGUI |
|---|
| 75 | since it was last saved, and |
|---|
| 76 | the file is changed by an external program, the message "you have made |
|---|
| 77 | changes to this version" is added and a third button, |
|---|
| 78 | "Save edited version", is shown. Under this circumstance, the usual action, |
|---|
| 79 | pressing "Load new" could result in valuable changes being lost. Pressing |
|---|
| 80 | "Save edited version" results brings you to the File/"Save as" menu, |
|---|
| 81 | where the modified version of the experiment file in EXPGUI can be |
|---|
| 82 | saved under a new name. |
|---|
| 83 | <br clear=all> |
|---|
| 84 | </DL></DL> |
|---|
| 85 | |
|---|
| 86 | <a name="lock"></a> |
|---|
| 87 | <h3>Please wait while GSAS program finishes...</h3> |
|---|
| 88 | <DL><DL> |
|---|
| 89 | A window labeled "<font face="courier">Please wait while GSAS program finishes." |
|---|
| 90 | If a problem occurs, close the DOS box and press the "Continue" button</font> |
|---|
| 91 | is created in Windows-9x while GSAS programs are run. As this window |
|---|
| 92 | is created, a "lock" file (<font face="courier">expgui.lck</font>) is also created. When the |
|---|
| 93 | DOS batch file running the GSAS program completes, this file is deleted. |
|---|
| 94 | The EXPGUI process waits until the <font face="courier">expgui.lck</font> lock file |
|---|
| 95 | is deleted. Should the DOS process crash before the file is deleted, |
|---|
| 96 | the "Continue" button can be pressed. This causes |
|---|
| 97 | EXPGUI to continue and deletes the lock file. |
|---|
| 98 | <br clear=all> |
|---|
| 99 | </DL></DL> |
|---|
| 100 | |
|---|
| 101 | <br clear=all> |
|---|
| 102 | <a name="Inputtitle"></a> |
|---|
| 103 | <h3>Input a value for the title</h3> |
|---|
| 104 | <DL><DL> |
|---|
| 105 | A dialog with "Enter a value for the title for experiment..." appears |
|---|
| 106 | when a new experiment is created. Note that this title can be edited |
|---|
| 107 | later on the |
|---|
| 108 | <a href="expgui1.html">Least Squares Control Page</a>. |
|---|
| 109 | </DL></DL> |
|---|
| 110 | |
|---|
| 111 | |
|---|
| 112 | |
|---|
| 113 | <br clear=all> |
|---|
| 114 | <a name="ChooseCIF"></a> |
|---|
| 115 | <h3>Choose CIF Block</h3> |
|---|
| 116 | <DL><DL> |
|---|
| 117 | When coordinates/cell parameters are read from a CIF, all blocks in the file |
|---|
| 118 | are read. If more than block containing coordinates is found, a message |
|---|
| 119 | saying "More than one block in CIF contains coordinates. Select the block to use." |
|---|
| 120 | One must then select one of these blocks from the list of blocks. |
|---|
| 121 | The blocks with coordinates are listed, both numbered and with the |
|---|
| 122 | block (data_) name. The "CIF Browser" |
|---|
| 123 | button can be pressed to view the data names and their values for each block. |
|---|
| 124 | </DL></DL> |
|---|
| 125 | |
|---|
| 126 | |
|---|
| 127 | <br clear=all> |
|---|
| 128 | <a name="open"></a> |
|---|
| 129 | <h3>Open Experiment File</h3> |
|---|
| 130 | <DL><DL> |
|---|
| 131 | The Open Experiment windows is displayed to select a |
|---|
| 132 | experiment file to read or write, as well as a |
|---|
| 133 | directory to use. When the message at the top reads |
|---|
| 134 | "Select an experiment file to read" either an |
|---|
| 135 | existing experiment file should be selected, or a new |
|---|
| 136 | name may be typed in at the box at the bottom to enter |
|---|
| 137 | a name manually. If the file is not found, |
|---|
| 138 | you will be warned and given the option of |
|---|
| 139 | creating a new experiment with that name. |
|---|
| 140 | |
|---|
| 141 | When the message at the top reads |
|---|
| 142 | "Select an experiment file to create", |
|---|
| 143 | typically after a "Save as" command, |
|---|
| 144 | the directory may be changed, but typically |
|---|
| 145 | a file name will be typed into the bottom box. |
|---|
| 146 | If the file exists, you will be warned before the |
|---|
| 147 | file is overwritten and you will have the option |
|---|
| 148 | to enter a different file name. |
|---|
| 149 | <P> |
|---|
| 150 | Note that the files in the list can be sorted |
|---|
| 151 | alphabetically or can be sorted by the date the |
|---|
| 152 | experiment file was last modified, according to |
|---|
| 153 | the checkbuttons to the upper right. |
|---|
| 154 | <P> |
|---|
| 155 | The "Include Archived Files" checkbox allows archive files |
|---|
| 156 | named <xxxxxx>.Onn to be read |
|---|
| 157 | (see the |
|---|
| 158 | <A href="expguic.html#archive">archive option</A>). |
|---|
| 159 | See the <A href="#LoadArchived">Load Archived File</A>, below, for |
|---|
| 160 | further discussion. |
|---|
| 161 | </DL></DL> |
|---|
| 162 | |
|---|
| 163 | <br clear=all> |
|---|
| 164 | <a name="LoadArchived"></a> |
|---|
| 165 | <h3>Load Archived File</h3> |
|---|
| 166 | <DL><DL> |
|---|
| 167 | When a archived experiment file is read, the "Load Archived File" |
|---|
| 168 | window is displayed to select the name to be used for the experiment. |
|---|
| 169 | There are two choices. One is to reuse existing name. |
|---|
| 170 | This will cause the current version of the experiment file to be |
|---|
| 171 | archived so that it is not lost. The selected [older] archived |
|---|
| 172 | version will then be read and will be saved as the latest version of the |
|---|
| 173 | experiment file. |
|---|
| 174 | The other option is to save the experiment |
|---|
| 175 | under a new name. |
|---|
| 176 | </DL></DL> |
|---|
| 177 | |
|---|
| 178 | <br clear=all> |
|---|
| 179 | <a name="ExcludeRegion"></a> |
|---|
| 180 | <h3>Exclude Data...<BR>Delete Region...</h3> |
|---|
| 181 | <DL><DL> |
|---|
| 182 | This message is shown before adding or deleting an excluded region using |
|---|
| 183 | <a href="excledt.html">EXCLEDT</a> to confirm an action. |
|---|
| 184 | See the <a href="excledt.html#AddRegion">discussion on Adding Regions</a> |
|---|
| 185 | in EXCLEDT. |
|---|
| 186 | Note that this |
|---|
| 187 | confirmation message can be eliminated if desired, (see the |
|---|
| 188 | EXCLEDT Options menu item <a href="excledt.html#prompt">Prompt on add/del</a>.) |
|---|
| 189 | <br clear=all> |
|---|
| 190 | </DL></DL> |
|---|
| 191 | |
|---|
| 192 | <br clear=all> |
|---|
| 193 | <a name="ProcessRegions"></a> |
|---|
| 194 | <h3>The upper (lower) limit has changed...<BR>The excluded regions have changed...</h3> |
|---|
| 195 | <DL><DL> |
|---|
| 196 | This message is shown |
|---|
| 197 | if 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. |
|---|
| 199 | It is also shown when |
|---|
| 200 | <a href="excledt.html">EXCLEDT</a> exits so that the new data limits |
|---|
| 201 | can be processed. GENLES will not run properly until POWPREF is run. |
|---|
| 202 | </DL></DL> |
|---|
| 203 | |
|---|
| 204 | <br clear=all> |
|---|
| 205 | <a name="RegionTooBig"></a> |
|---|
| 206 | <h3>The upper (lower) data point...</h3> |
|---|
| 207 | <DL><DL> |
|---|
| 208 | This message is shown when the upper data limit (lower d-min limit) |
|---|
| 209 | well outside the range of data. |
|---|
| 210 | It is probably best to accept this suggestion. See the |
|---|
| 211 | <a href="excledt.html#LimitTooHigh">discussion on data limits</a> |
|---|
| 212 | in the EXCLEDT web page for more information. |
|---|
| 213 | </DL></DL> |
|---|
| 214 | |
|---|
| 215 | <br clear=all> |
|---|
| 216 | <a name="ProcessUse"></a> |
|---|
| 217 | <h3>You have changed histogram flags...</h3> |
|---|
| 218 | <DL><DL> |
|---|
| 219 | This message is shown |
|---|
| 220 | after changing histogram flags so that a different set of histograms |
|---|
| 221 | will be included or excluded in a refinement. |
|---|
| 222 | GENLES will not run properly until POWPREF is run. |
|---|
| 223 | </DL></DL> |
|---|
| 224 | |
|---|
| 225 | <a name="Warn"></a> |
|---|
| 226 | <H2>Warning Messages</H2> |
|---|
| 227 | |
|---|
| 228 | <br clear=all> |
|---|
| 229 | <a name="AbandonEditConstraints"></a> |
|---|
| 230 | <a name="AbandonAtomConstraints"></a> |
|---|
| 231 | <h3>Abandoning Constraint Editing</h3> |
|---|
| 232 | <DL><DL> |
|---|
| 233 | If the "Cancel Changes" button is pressed when |
|---|
| 234 | a profile or atom constraint is being edited or created, a message saying |
|---|
| 235 | "Do you want to lose any changes made to this constraint?" is displayed, even |
|---|
| 236 | if no changes have been made to the constraint. Changes are recorded only when the |
|---|
| 237 | "Save" button is pressed. |
|---|
| 238 | </DL></DL> |
|---|
| 239 | |
|---|
| 240 | |
|---|
| 241 | <br clear=all> |
|---|
| 242 | <a name="OpenErr"></a> |
|---|
| 243 | <h3>File ... does not exist in ...</h3> |
|---|
| 244 | <DL><DL> |
|---|
| 245 | When an attempt is made to open a file that does not |
|---|
| 246 | already exists, for example when the EXPNAM command |
|---|
| 247 | is used, this warning is displayed. The answer can be |
|---|
| 248 | "Select other" or "Create", where "Select other" will |
|---|
| 249 | return you to a file selection dialog and "Create" |
|---|
| 250 | will create a new dialog with this name. |
|---|
| 251 | </DL></DL> |
|---|
| 252 | |
|---|
| 253 | <br clear=all> |
|---|
| 254 | <a name="OverwriteErr"></a> |
|---|
| 255 | <a name="OverwriteCnv"></a> |
|---|
| 256 | <h3>File ... already exists in ... OK to overwrite?</h3> |
|---|
| 257 | <DL><DL> |
|---|
| 258 | When an attempt is made to using the File/"Save As" |
|---|
| 259 | command to write the current experiment file |
|---|
| 260 | with a new name, but |
|---|
| 261 | a file with the newly specified name already exists, |
|---|
| 262 | this message is displayed. Choose "Select other" |
|---|
| 263 | to specify a different file name or "Overwrite" |
|---|
| 264 | to use this name in which case the older file |
|---|
| 265 | is replaced. |
|---|
| 266 | <P> |
|---|
| 267 | A similar warning will occur in UNIX when converting files. |
|---|
| 268 | If the intended output file already exists, |
|---|
| 269 | this message is displayed. Choose "Cancel" |
|---|
| 270 | to specify a different file name or "Overwrite" |
|---|
| 271 | to use this name in which case the older file |
|---|
| 272 | is replaced. |
|---|
| 273 | This message can be seen in Windows when converting files, |
|---|
| 274 | for slightly different reasons. When files are converted, the |
|---|
| 275 | converted file keeps the same name as the original version. However, |
|---|
| 276 | th original file is renamed to XXXX.ord, where XXXX.YYY is the |
|---|
| 277 | original file name. If a file named XXXX.ord already exists, this message |
|---|
| 278 | is displayed. |
|---|
| 279 | </DL></DL> |
|---|
| 280 | |
|---|
| 281 | <br clear=all> |
|---|
| 282 | <a name="NoValidHist"></a> |
|---|
| 283 | <h3>No histograms are ready to plot. Run GENLES and try again.</h3> |
|---|
| 284 | <DL><DL> |
|---|
| 285 | This happens when LIVEPLOT is run but no valid histograms are available |
|---|
| 286 | to plot. LIVEPLOT can plot histograms only when they have been processed by |
|---|
| 287 | both POWPREF and GENLES. |
|---|
| 288 | </DL></DL> |
|---|
| 289 | |
|---|
| 290 | <br clear=all> |
|---|
| 291 | <a name="Customizewarning"></a> |
|---|
| 292 | <h3>Error reading localconfig or .gsas_config:</h3> |
|---|
| 293 | <DL><DL> |
|---|
| 294 | This happens when an invalid command is encountered in file localconfig |
|---|
| 295 | or .gsas_config. Some or all of the commands in these files |
|---|
| 296 | will be skipped over, |
|---|
| 297 | but nothing serious wrong will likely result. Note that the |
|---|
| 298 | localconfig file is located in the expgui directory |
|---|
| 299 | (typically /home/gsas/expgui/localconfig or |
|---|
| 300 | C:\gsas\expgui\localconfig) and the .gsas_config is located in your |
|---|
| 301 | home directory (~/.gsas_config or C:\.gsas_config in windows). |
|---|
| 302 | If you rename each file to something else, the error should go away. |
|---|
| 303 | At that point you can decide if you want to track the error down to retain |
|---|
| 304 | your <a href="expgui_cfg.html">customizations</a>. |
|---|
| 305 | </DL></DL> |
|---|
| 306 | |
|---|
| 307 | <a name="Error"></a> |
|---|
| 308 | <H2>Error Messages</H2> |
|---|
| 309 | |
|---|
| 310 | <br clear=all> |
|---|
| 311 | <a name="NoPGPLOT"></a> |
|---|
| 312 | <h3>Unable to find file GRFONT.DAT...</h3> |
|---|
| 313 | <DL><DL> |
|---|
| 314 | The file <font face="courier">grfont.dat</font> is expected to be in the ...\gsas\fonts directory |
|---|
| 315 | in DOS/Windows platforms and files <font face="courier">grfont.dat</font> and |
|---|
| 316 | <font face="courier">pgxwin_server</font> are expected to be found in the .../gsas/pgl directory |
|---|
| 317 | in UNIX. If these files cannot be found, GSAS will not be able to produce |
|---|
| 318 | graphics in programs such as POWPLOT, RAWPLOT,... |
|---|
| 319 | If GSAS and EXPGUI are correctly installed this error will not occur |
|---|
| 320 | (see the installation notes for |
|---|
| 321 | <A HREF="expgui_Win_readme.html">Windows</A> |
|---|
| 322 | and |
|---|
| 323 | <A HREF="expgui_Unix_readme.html">UNIX</A>. |
|---|
| 324 | |
|---|
| 325 | </DL></DL> |
|---|
| 326 | |
|---|
| 327 | <br clear=all> |
|---|
| 328 | <a name="ConvNotFound"></a> |
|---|
| 329 | <h3>Sorry, file ... not found in ...</h3> |
|---|
| 330 | <DL><DL> |
|---|
| 331 | The specified input file was not found for conversion |
|---|
| 332 | </DL></DL> |
|---|
| 333 | |
|---|
| 334 | <br clear=all> |
|---|
| 335 | <a name="ConvSameName"></a> |
|---|
| 336 | <h3>Sorry, filenames must differ</h3> |
|---|
| 337 | <DL><DL> |
|---|
| 338 | For UNIX file conversions, the input and output file names |
|---|
| 339 | must be different. You have specified the same name twice. |
|---|
| 340 | </DL></DL> |
|---|
| 341 | |
|---|
| 342 | <br clear=all> |
|---|
| 343 | <a name="NoRename"></a> |
|---|
| 344 | <h3>Unable to rename <I>XXXXX</I>.LST</h3> |
|---|
| 345 | <DL><DL> |
|---|
| 346 | This message is displayed if the GSAS .LST file could not |
|---|
| 347 | be renamed prior to running DISAGL in a separate window. |
|---|
| 348 | On Windows it appears that LSTVIEW can prevent EXPGUI |
|---|
| 349 | from renaming the .LST file. Either exit LSTVIEW |
|---|
| 350 | while running DISAGL or reset the DISAGL option |
|---|
| 351 | DISAGL so that output goes to the .LST file. |
|---|
| 352 | </DL></DL> |
|---|
| 353 | |
|---|
| 354 | <br clear=all> |
|---|
| 355 | <a name="OldEXPTOOL"></a> |
|---|
| 356 | <h3>You must upgrade the EXPTOOL program...</h3> |
|---|
| 357 | <DL><DL> |
|---|
| 358 | The original version of the EXPTOOL program used within |
|---|
| 359 | EXPGUI to add histograms does not work with dummy histograms. |
|---|
| 360 | Versions of GSAS distributed prior to October 2001 do not contain this updated |
|---|
| 361 | routine. A more recent version of the EXPTOOL program can |
|---|
| 362 | be downloaded from |
|---|
| 363 | <A Href="ftp://ftp.ncnr.nist.gov/pub/cryst/gsas/exe_win/"> |
|---|
| 364 | ftp://ftp.ncnr.nist.gov/pub/cryst/gsas/exe_win/</A>, |
|---|
| 365 | <A Href="ftp://ftp.ncnr.nist.gov/pub/cryst/gsas/exe_linux/"> |
|---|
| 366 | ftp://ftp.ncnr.nist.gov/pub/cryst/gsas/exe_linux/</A> or |
|---|
| 367 | <A Href="ftp://ftp.ncnr.nist.gov/pub/cryst/gsas/exe_sgi/"> |
|---|
| 368 | ftp://ftp.ncnr.nist.gov/pub/cryst/gsas/exe_sgi/</A>. |
|---|
| 369 | Alternately, EXPEDT can be used to add dummy histograms. |
|---|
| 370 | </DL></DL> |
|---|
| 371 | |
|---|
| 372 | <br clear=all> |
|---|
| 373 | <a name="TCLDUMPError"></a> |
|---|
| 374 | <h3>Error running TCLDUMP (LIVEPLOT or BKGEDIT)</h3> |
|---|
| 375 | <DL><DL> |
|---|
| 376 | The program TCLDUMP (or program HSTDMP if TCLDUMP is not found) is used to read |
|---|
| 377 | the binary <I>expnam</I>.Pxx and <I>expnam</I>.Rxx files produced by |
|---|
| 378 | POWPREF and GENLES so that refinement results can be plotted. |
|---|
| 379 | If there is an error reading these files, an error message is produced |
|---|
| 380 | reading "There was an error running the TCLDUMP program..." |
|---|
| 381 | and the text of the error message reads something like |
|---|
| 382 | "Invalid command name 'FORTRAN'". |
|---|
| 383 | The most common reason for this error is that the |
|---|
| 384 | <I>expnam</I>.Pxx and <I>expnam</I>.Rxx files do not exist (because you have |
|---|
| 385 | not run POWPREF or have moved/renamed the .EXP file. It is possible, |
|---|
| 386 | but less common for this error to occur if TCLDUMP tries to read files |
|---|
| 387 | produced by an older version of GSAS (since the internal format of the |
|---|
| 388 | binary files sometimes changes). If you see this message, run POWPREF & GENLES |
|---|
| 389 | to force these files to be written. If the GSAS results can be plotted in |
|---|
| 390 | POWPLOT, but not in LIVEPLOT or BKGEDIT, please contact Brian Toby at |
|---|
| 391 | <a href="mailto:brian.toby@nist.gov">Brian.Toby@NIST.GOV</a>. |
|---|
| 392 | </DL></DL> |
|---|
| 393 | |
|---|
| 394 | <br clear=all> |
|---|
| 395 | <a name=""></a> |
|---|
| 396 | <h3></h3> |
|---|
| 397 | <DL><DL> |
|---|
| 398 | </DL></DL> |
|---|
| 399 | |
|---|
| 400 | <hr> |
|---|
| 401 | <TABLE BORDER BGCOLOR="#FFFF40" ALIGN=RIGHT> |
|---|
| 402 | <TR><TH><A Href="expgui.html">EXPGUI top</A> |
|---|
| 403 | </TH></TR></TABLE> |
|---|
| 404 | |
|---|
| 405 | <P><font size=-1><A HREF="MAILTO:crystal@NIST.gov?subject=WWW page <?=$PHP_SELF?>">Comments, corrections or questions: crystal@NIST.gov</A></font><BR> |
|---|
| 406 | <font size=-1><? lastmod(); ?> </font> |
|---|
| 407 | <br> |
|---|
| 408 | $Revision: 657 $ $Date: 2009-12-04 23:09:50 +0000 (Fri, 04 Dec 2009) $ |
|---|
| 409 | </blockquote> |
|---|
| 410 | </body> |
|---|
| 411 | </html> |
|---|
