source: trunk/doc/expgui_cfg.html @ 143

Last change on this file since 143 was 143, checked in by toby, 11 years ago

# on 2000/05/17 20:27:05, toby did:
major edit

  • Property rcs:author set to toby
  • Property rcs:date set to 2000/05/17 20:27:05
  • Property rcs:lines set to +93 -21
  • Property rcs:rev set to 1.8
  • Property rcs:state set to Exp
  • Property svn:keywords set to Author Date Revision Id
File size: 22.9 KB
Line 
1<HTML>
2   <META NAME="Author" CONTENT="Brian H. Toby">
3   <TITLE>Customizing EXPGUI and Associated Programs</TITLE>
4<HEAD>
5</HEAD>
6<BODY BGCOLOR="#FFFFFF">
7
8<A HREF=http://www.ncnr.nist.gov>
9<IMG SRC="http://www.ncnr.nist.gov/images/ncnrtrans.gif" 
10alt="Link to NIST Center for Neutron Research home page"
11ALIGN=RIGHT></A>
12<A HREF=http://www.nist.gov>
13<IMG SRC="http://www.ncnr.nist.gov/images/webidblue_2lineright.gif" 
14alt="Link to National Institute of Standards & Technology home page"
15ALIGN=LEFT></A>
16<CENTER>
17<H1>
18Customizing EXPGUI and Associated Programs</H1></CENTER>
19
20The EXPGUI GSAS graphical user interface can be modified in many
21ways quite easily.
22This document describes how the GUI works and how to modify the menus without
23significant reprogramming. A little bit of programmaning in Tcl/Tk can go a
24long way in adding new features. See the
25<a HREF="#Customizing">Customizing</A> examples, below.
26
27<H3>EXPGUI</H3>
28The main GUI is created by file expgui, which in turn uses the following files
29sequentially:
30<UL>
31<LI><TT>readexp.tcl</TT>
32<LI><TT>gsascmds.tcl</TT>
33<LI><TT>gsasmenu.tcl</TT>
34</UL>
35Two additional files are read if they are found:
36<UL>
37<LI><TT>localconfig</TT>
38<LI><TT>.gsas_config</TT>
39</UL>
40<P>The first three files,
41(<TT>readexp.tcl</TT>, <TT>gsascmds.tcl</TT>, <TT>gsasmenu.tcl</TT>)
42must be located in the same directory where the <TT>expgui</TT> file is found.
43The <TT>localconfig</TT> file also is read from this directory, if it exists.
44The final file, <TT>.gsas_config</TT>, is read from the user's login directory (UNIX) or <TT>C:\</TT> (Windows).
45The <TT>localconfig</TT> and <TT>.gsas_config</TT> are intended to
46contain system-wide and user-level default values for parameters
47that are described in this document. Most routines have
48a "Save Options" command that writes some of the current parameters to
49file  <TT>.gsas_config</TT>. Note that information in <TT>.gsas_config</TT>
50overrides that in <TT>localconfig</TT>.
51No error occurs if either of these files are not found.
52
53<P>
54The <TT>readexp.tcl</TT> and <TT>gsascmds.tcl</TT> files contain
55tcl procedures that are
56used for more than one application, so it is convenient to place them
57in separate files. They are only of interest to someone trying to debug
58or add new functionality to expgui.
59<P>
60The <TT>gsasmenu.tcl</TT> file defines the contents of the
61menu bar, the contents of the
62button bar and definitions for each command. The contents of this file
63are designed to be modified and extended by users, either by editing the file,
64or by overridding definitions in the <TT>localconfig</TT> or
65<TT>.gsas_config</TT> files.
66
67The important variables defined in the <TT>gsasmenu.tcl</TT> file are:
68<DL><DL>
69<DT>expgui(menunames)<DD>
70This list defines the menu bar headings other than File, Options & Help
71<DT>expgui_menulist<DD>
72Each array element, e.g. expgui_menulist(file) and expgui_menulist(powder),
73defines commands to be added to a menu heading. Each command will appear
74as an array element in expgui_cmdlist.
75<DT>expgui_cmdlist<DD>
76Each array element, e.g. expgui_cmdlist(Save) or expgui_cmdlist(expnam)
77contains two items. The first defines a tcl procedure to be executed
78when the command is invoked, or "-" if no command will be invoked and
79the second contains help information describing what the command does.
80Note that when menu item is selected the variable cmd is set to the
81name of the command, so
82<PRE>
83    expgui_cmdlist(powpref) {{runGSASwEXP $cmd} {Powder data preparation}}
84</PRE>
85means that "runGSASwEXP powpref" will be invoked when powpref is invoked.
86. For example, when powpref is selected, the tcl command
87"runGSASwEXP $cmd" is invoked, where variable cmd is set to "powpref".
88<DT>expgui(buttonlist)<DD>
89This list defines the commands that will appear on the button bar where
90each item that appears on the button bar must have a matching pair of entries
91in expgui_cmdlist.
92Thus if the command
93<PRE>
94   set expgui(buttonlist) {expnam expedt genles ortep fourier forsrh forplot lstview}
95</PRE>
96is placed in the <TT>localconfig</TT> or <TT>.gsas_config</TT> files this will
97redefine the contents of the button bar.
98</DL></DL>
99
100In addition to the variables defined in the previous file, expgui, uses
101a small number of array elements for other configuration options. They are:
102<DL><DL>
103
104<DT>expgui(scriptdir)<DD>
105This determines where files such as <TT>readexp.tcl</TT>, etc.
106are located. This defaults to the location where <TT>expgui</TT> is located so
107it rarely needs to be changed.
108
109<DT>expgui(gsasdir)<DD>
110This contains the location of the GSAS directory, if it is not the
111parent director where expgui is found.
112This determines where a number of GSAS data files will be located. If expedt
113crashes when you try to add new atoms, this is probably wrong.
114
115<DT>expgui(gsasexe)<DD>
116This determines where the GSAS executable files are located.
117You might want to change this is you keep multiple versions of GSAS
118around or if you keep the GSAS files in a different location than
119the default or want to keep the tcl files somewhere other than
120in a subdirectory of the GSAS files.
121
122<DT>expgui(coordfont)<DD>
123Sets the font used for the coordinates scroll box
124
125<DT>expgui(histfont)<DD>
126Sets the font used for the histogram scroll box
127
128<DT>liveplot(hst)<DD>
129Sets the default histogram used for liveplot
130
131<DT>liveplot(legend)<DD>
132Sets the default value for display of the legend in liveplot
133
134<DT>expgui(initstring)<DD>
135Defines commands to be executed by EXPGUI after all other commands
136have been run. This is used to define initialization commands in
137the <TT>localconfig</TT> or <TT>.gsas_config</TT> files that cannot be
138run at the time when the files are sourced. <I>(added in EXPGUI v1.21)</I>
139</DL></DL>
140
141The following variables are written to <tt>.gsas_config</tt> when
142"Save Options" is used. These variables are all set from the GUI and therefore
143do not need to be edited manually.
144
145<DL><DL>
146<DT>expgui(archive)<DD>
147This defines the default state for the archive flag,
148where 0 is off and 1 is on. When archive is on, a copy of the .EXP file
149is saved before a new version of the file is saved and before EXPEDT is run.
150
151<DT>expgui(asorttype)<DD>
152This determines the atom sort mode.
153
154<DT>expgui(hsorttype)<DD>
155This determines the histogram sort mode.
156
157<DT>expgui(filesort)<DD>
158This determines the default file sorting mode for the expnam command.
159
160<DT>env(GSASBACKSPACE)<DD>
161Used only for UNIX: This determines if the default definition
162for the backspace key is overridden; some UNIX systems need this so that
163expedt and other terminal-oriented programs work correctly and
164other systems do not. You can toggle this option using the
165"Override Backspace" option on the file menu to see what works for you.
166
167</DL></DL>
168
169<HR><H3>LSTVIEW</H3>
170The <TT>localconfig</TT> and <TT>.gsas_config</TT> files are read, if present.
171The following options are available for customization in these files:
172<DL><DL>
173<DT>txtvw(menulength)<DD>
174This limits the number of entries that can
175exist in a menu. For example, the default is 25, so when more than 25 cycles
176are found in a .LST file, only the last 25 are listed in the
177"Go To"/cycle submenu.
178<DT>txtvw(maxchars)<DD>
179This limits the maximum number of
180characters that will be read from an existing .LST file to speed
181the start of the program. The default is ~1Mb
182for UNIX systems and ~200K for Windows.
183</DL></DL>
184
185The following variables are written to <tt>.gsas_config</tt> when
186"Save Options" is used. These variables can be set from the GUI and therefore
187do not need to be edited manually.
188
189<DL><DL>
190<DT>txtvw(followcycle)<DD>
191This sets the initial value for the
192"Auto Advance" button in the "Go To" menu. When this is true,
193the program will show the last cycle in the file. As new cycles are
194added, the "view" is advanced.
195
196<DT>txtvw(font)<DD>
197This sets the font used for LSTVIEW. See documentation on the font command in
198Tk for details on font naming.
199</DL></DL>
200
201One additional variable is present that I don't suggest using at present:
202<UL>
203<LI>plotvars: I am in the process of developing code that tracks
204and plots shifts and R values as a function cycle number. Setting plotvars to 1
205allows this code to be tested.
206</LI></UL>
207
208<hr><H3>LIVEPLOT</H3><A NAME="liveplot"></A>
209The <TT>localconfig</TT> and <TT>.gsas_config</TT> files are read, if present.
210Note that some of these options are relevant only if the tcldump program is
211present.
212<P>
213The following options are available for customization in these files:
214<DL><DL>
215<DT>peakinfo(flag<i>n</i>)<DD>
216These variables define if peak positions will be shown
217for reflections in phase "<i>n</i>". Reflections will be shown if
218the value is non-zero.
219
220<DT>peakinfo(color<i>n</i>)<DD>
221These variables define the default colors for
222reflections in phase "<i>n</i>"
223
224<DT>peakinfo(dashes<i>n</i>)<DD>
225These variables define if peaks will be dashed for
226reflections in phase "<i>n</i>" (UNIX only). Lines will be dashed if
227the value is non-zero.
228
229<DT>peakinfo(min<i>n</i>) and peakinfo(max<i>n</i>)<DD>
230These variables dictact the placement vertical position for reflection
231markers, when manually placed (see expgui(autotick), below). To draw
232to the edge of the screen, use -Inf and Inf.
233</DL></DL>
234
235The following variables are written to <tt>.gsas_config</tt> when
236"Save Options" is used. These variables are all set from the GUI and therefore
237do not need to be edited manually.
238
239<DL><DL>
240<DT>graph(printout)<DD>
241This is set to 1 if PostScript files
242will be printed and 0 if they will be written to disk (for Windows all
243files should be written to disk).
244
245<DT>graph(outname)<DD>
246This is the default for the file name used
247when PostScript files will be written to disk.
248
249<DT>graph(outcmd)<DD>
250This is the default for the command used
251to print PostScript files (Unix only).
252
253<DT>graph(legend)<DD>
254Sets the default value for display of the legend in liveplot and widplt.
255
256<DT>peakinfo(obssym)<DD>
257Symbol for observed data points. Valid choices are square, circle, diamond,
258plus, cross, splus and scross.
259
260<DT>peakinfo(obssize)<DD>
261Size for the symbol for observed data points. A value of 1 corresponds to about 1/8 inch
262(about 3 mm).
263
264<DT>expgui(pixelregion)<DD>
265When hkl values are loaded (using tcldump) and reflections are labeled, reflections
266can be labeled using a Shift-Left-Mouse click. All labeled reflections within expgui(pixelregion)
267pixels of the mouse position are assumed to be overlapped and are labeled.
268
269<DT>expgui(fadetime)<DD>
270The time in seconds before reflection labels are removed. A value of zero means that reflections
271must be deleted manually (Shift-Right-Mouse).
272
273<DT>expgui(lblfontsize)<DD>
274A size for reflections labels in pixels.
275
276<DT>expgui(hklbox)<DD>
277If this variable is non-zero, reflection indices are shown in a box.
278
279<DT>expgui(autotick)<DD>
280If this variable is non-zero, reflection markers positions are
281set automatically.
282</DL></DL>
283
284<P>
285<B>Using TCLDUMP with LIVEPLOT.</B>
286LIVEPLOT works with the standard GSAS program HSTDMP, but it works faster and is more
287powerful when used with the TCLDUMP program. Instructions for downloading this file can
288be found in the installation notes for
289<A HREF="expgui_Win_readme.html">
290Windows</A> and
291<A HREF="expgui_Unix_readme.html">
292UNIX</A>. Note that as of the April 2000 releases, GSAS is now distributed
293with TCLDUMP.
294<P>
295<B>Combining CMPR and LIVEPLOT.</B>
296If you have <A HREF="http://www.ncnr.nist.gov/programs/crystallography/software/cmpr.html">CMPR</A>
297installed on your computer, you can use superimpose on the GSAS results
298the peaks for an arbitrary unit cell. If desired, space group extinctions
299can even be shown.
300This is pretty neat! To enable this feature, you must have a version
301of CMPR downloaded after 4 May 1998
302<A HREF="http://www.ncnr.nist.gov/programs/crystallography/software/cmpr.html">
303(see the CMPR installation instructions.)</A>
304For UNIX, create a link from in the expgui
305directory to file cellgen.tcl in the CMPR directory. For example:
306<PRE>
307         ln -s /usr/local/cmpr/cellgen.tcl /usr/local/gsas/expgui/cellgen.tcl
308</PRE>
309For Windows, copy all the CMPR .tcl and .exe files into the expgui directory.
310<P>
311<B>Combining LOGIC and LIVEPLOT</B>
312If you have <A HREF="http://www.ncnr.nist.gov/programs/crystallography/software/logic.html">LOGIC</A>
313installed on your computer, you can superimpose peaks
314for a entry from the ICDD/JCPDS database on a pattern in LIVEPLOT.
315This is also pretty neat!
316To enable this feature, you must have
317a version of LOGIC downloaded after 4 May 1998
318<A HREF="http://www.ncnr.nist.gov/programs/crystallography/software/logic.html">
319(see the LOGIC installation instructions.)</A>
320For UNIX, create a link from in the GSAS GUI
321directory to file icddcmd.tcl in the LOGIC directory. For example:
322<PRE>
323         ln -s /usr/local/powdersuite/icddcmd.tcl /usr/local/gsas/tcl/icddcmd.tcl
324</PRE>
325For Windows, copy all the LOGIC files into the expgui directory.
326<HR>
327<H3>WIDPLT</H3>
328The widplt script is used to display the FWHM for one or more histograms
329from a .EXP file.
330At this point it only works for CW data.
331It is often convenient to add for reference the expected
332instrumental curves as options to the menu. This can be done by creating a
333file called widplot_<i>name</i>. For example, renaming the
334<tt>example_widplt_BT1</tt> file supplied with the distribution to
335<tt>widplt_BT1</tt> will cause the FWHM curves for the NIST BT-1 instrument
336to be added to the menu of defined FWHM values.
337<P>
338Creating such a file is easy. To add a entry define the following
339five array elements using a single, unique element name and then append that
340element name to variable datalist.
341Define
342<PRE>
343    set UVWP(Ge15) {398.5 -343.2  163.0 0}
344    set XY(Ge15) {0 0}
345    set wave(Ge15) 2.0775
346    set lblarr(Ge15) "BT-1 Ge(311) 15'"
347    set ttrange(Ge15) "5 160"
348    lappend datalist Ge15
349</PRE>
350Array element UVWP(item) contains the (Gaussian) GU, GV, GW and GP values,
351while XY(item) contains the (Lorentzian) LX and LY terms. Array element
352wave(item) contains a wavelength, array element lblarr(item) contains
353the text to be shown on the "Plot Contents" menu and ttrange(item)
354defines the range the function is valid.
355<P>
356The following variables are written to <tt>.gsas_config</tt> when
357"Save Options" is used. These variables are all set from the GUI and therefore
358do not need to be edited manually.
359
360<DL><DL>
361<DT>graph(printout)<DD>
362This is set to 1 if PostScript files
363will be printed and 0 if they will be written to disk (for Windows all
364files should be written to disk).
365
366<DT>graph(outname)<DD>
367This is the default for the file name used
368when PostScript files will be written to disk.
369
370<DT>graph(outcmd)<DD>
371This is the default for the command used
372to print PostScript files (Unix only).
373
374<DT>graph(legend)<DD>
375Sets the default value for display of the legend in liveplot and widplt.
376
377<DT>graph(plotunits)<DD>
378Sets the units used for displaying the data. Values are "d", "q", "",
379for d-space, Q and 2-theta, respectively.
380<DT>graph(equivwave)<DD>
381Sets the wavelength used for displaying data, if blank, no conversion is
382done and data are shown in their original wavelength.
383</DL></DL>
384
385<hr>
386<a name="Customizing"><H2>
387Customizing Example 1: Adding a new button to the button bar
388</H2></A>
389When a LeBail extraction is used to refine lattice constants, profile
390terms, ... It is always a good idea to run GENLES a few times after running
391POWPREF. This is because GENLES sets the extracted intensities back to their
392crystallographic values, during the first GENLES cycle after POWPREF has been
393run. Refining anything until the extracted intensities return to reasonable
394values is a really bad idea. Forturnately, running GENLES with the number of
395cycles set to zero gives the Le Bail extraction a head start.
396<P>
397The code below can be used to define a new command, <tt>leBail</tt>. The first
398command adds a command to the button bar and the second one defines what will
399be done when it is invoked (the number of cycles is set to zero and
400GENLES is run three times). It also defines the help entry. Note that commands must start with a lower case letter even though Armel LeBail's last name
401does not.
402
403<PRE>
404    lappend expgui(buttonlist) leBail
405    set expgui_cmdlist(leBail) {
406        {set entryvar(cycles) 0; runGSASwEXP "genles genles genles"}
407        {Converges GENLES with LeBail extractions;
408          Sets the number of cycles to zero and runs GENLES 3 times.}
409    }
410
411</PRE>
412To make this customization, put the above in the <TT>localconfig</TT> 
413file or the
414<TT>~/.gsas_config</TT> or (or <TT>C:\GSAS\EXPGUI\.gsas_config</TT>)
415file.
416<hr>
417<H2>
418Customizing Example 2: Putting DISAGL Results in a Separate Box
419</H2>
420Barbara Reisner has been asking me to put the output from DISAGL in a separate
421window. Sounds like a pretty reasonable request. Here is an example with code
422to do that as a customization option. Please note that this has now been
423incorporated into EXPGUI, so do not use this example.
424<PRE>
425  set expgui(disaglSeparateBox) 1
426  set expgui_cmdlist(disagl) {rundisagl {Hacked Distance/angle calculations}}
427  proc rundisagl {} {
428    global expgui txtvw tcl_version tcl_platform
429    if {$expgui(disaglSeparateBox) && $tcl_platform(platform) != "windows"} {
430        set root [file root $expgui(expfile)]
431        catch {file rename $root.LST $root.OLS}
432        runGSASwEXP disagl
433        catch {file rename $root.LST $root.DIS}
434        catch {file rename $root.OLS $root.LST}
435
436        # open a new window
437        catch {toplevel .disagl}
438        catch {eval grid forget [grid slaves .disagl]}
439        text .disagl.txt -width 100 -wrap none \
440                -yscrollcommand ".disagl.yscroll set" \
441                -xscrollcommand ".disagl.xscroll set"
442        if {$tcl_version >= 8.0} {.disagl.txt config -font $txtvw(font)}
443        scrollbar .disagl.yscroll -command ".disagl.txt yview"
444        scrollbar .disagl.xscroll -command ".disagl.txt xview" -orient horizontal
445        grid .disagl.xscroll -column 0 -row 2 -sticky ew
446        grid .disagl.txt -column 0 -row 1 -sticky nsew
447        grid .disagl.yscroll -column 1 -row 1 -sticky ns
448        grid columnconfigure .disagl 0 -weight 1
449        grid rowconfigure .disagl 1 -weight 1
450        wm title .disagl "DISAGL results $expgui(expfile)"
451        wm iconname .disagl "DISAGL $root"
452        set in [open $root.DIS r]
453        .disagl.txt insert end [read $in]
454        close $in
455        bind all <Control-KeyPress-c> {destroy .disagl}
456        bind .disagl <KeyPress-Prior> ".disagl.txt yview scroll -1 page"
457        bind .disagl <KeyPress-Next> ".disagl.txt yview scroll 1 page"
458        bind .disagl <KeyPress-Right> ".disagl.txt xview scroll 1 unit"
459        bind .disagl <KeyPress-Left> ".disagl.txt xview scroll -1 unit"
460        bind .disagl <KeyPress-Up> ".disagl.txt yview scroll -1 unit"
461        bind .disagl <KeyPress-Down> ".disagl.txt yview scroll 1 unit"
462        bind .disagl <KeyPress-Home> ".disagl.txt yview 0"
463        bind .disagl <KeyPress-End> ".disagl.txt yview end"
464        # don't disable in Win as this prevents the highlighting of selected text
465        if {$tcl_platform(platform) != "windows"} {
466            .disagl.txt config -state disabled
467        }
468    } else {
469        runGSASwEXP disagl
470    }
471  }
472
473if {$tcl_platform(platform) != "windows"} {
474  append expgui(initstring) {
475      $expgui(fm).option.menu add checkbutton  -label "DISAGL window" \
476              -variable expgui(disaglSeparateBox) -underline 0;
477  }
478}
479
480</PRE>
481To make this customization, put the above in the <TT>localconfig</TT> 
482file or the
483<TT>~/.gsas_config</TT> or (or <TT>C:\GSAS\EXPGUI\.gsas_config</TT>)
484file.
485<P>
486Note that the <tt>expgui(initstring)</tt> option became available in EXPGUI
487version 1.21. (Previous versions will ignore this). This code must be executed
488after all the menus and other GUI code has been run. When executed, it
489creates a checkbutton on the Options menu to
490turn the "separate DISAGL window mode" mode on and off.
491
492<hr><H2>
493Customizing Example 3: Adding a new page to EXPGUI
494</H2>
495The steps for creating support for additional functionality, implementation
496of atom constraints, is outlined here. Routines described here can be found in
497file <tt>atomcons.tcl</tt> unless otherwise noted.
498<OL>
499<LI>Create a routine to read and write the appropriate records
500from the .EXP file. In this case, a new routine, constrinfo,
501was added to file <tt>readexp.tcl</tt>.
502This takes considerable care and manual testing.
503<LI>Create a routine that places the appropriate widgets into a frame
504(in this case MakeAtomsConstraintsPane). This routine will be called only once.
505Note that in this example expcons(atommaster) is defined to be the name of the
506frame.
507<LI>Create a routine to display and edit the information shown in the
508frame. In this case, DisplayAtomConstraints. This routine will be called each
509time the page is displayed. Note that this routine and the previous can be
510tested in a separate toplevel until they work well.
511<LI>In this particular example, the previous frame is located on a notebook
512widget that in turn placed on a notebook page, so MakeConstraintsPane is used
513to create this inner notebook when the "Constraints" notebook page is first
514shown. This in turn calls MakeAtomsConstraintsPane and DisplayAtomConstraints.
515No routine is needed to update this page each time the page
516is displayed.
517<LI>Edit file <tt>expgui</tt> to make the following changes:
518<UL>
519<P><LI>load the <tt>atomcons.tcl</tt> file:
520<PRE>
521# commands for costraints
522source [file join $expgui(scriptdir) atomcons.tcl]
523</PRE>
524<P><LI>Define a notebook page for the option. The -createcmd option
525is used only once, but the -raisecmd option is used every time
526the page is exposed.
527<PRE>
528set expgui(consFrame) [\
529            .n insert end consPane -text Constraints \
530            -raisecmd "set expgui(pagenow) consFrame"\
531            -createcmd MakeConstraintsPane]
532</PRE>
533Note that if we were displaying the atoms constraint page directly on
534the main notebook widget, the previous command would have been
535<tt>-raisecmd DisplayAtomConstraints -createcmd MakeAtomsConstraintsPane</tt>
536<P>
537If the frame will need to be updated when histogram information changes,
538add the name of the frame and a command to execute into string
539expgui(frameactionlist), for example:
540<PRE>
541    lappend expgui(frameactionlist) "consFrame DisplayConstraints"
542</PRE>
543</UL>
544</OL>
545<hr>
546GSAS is written by Allen C. Larson and <A HREF="http://www.nist.gov/cgi-bin/exit_nist.cgi?url=http://lansce.lanl.gov/lujan/staff12/vondreele.htm">
547Robert B. Von Dreele</A>, MS-H805,
548Los Alamos National Laboratory, Los Alamos, NM 87545. Problems, questions
549or kudos concerning GSAS should be sent to Robert B. Von Dreele at <A HREF="MAILTO:vondreele@lanl.gov">vondreele@lanl.gov</A>
550
551<P>This GUI is written by Brian H. Toby of the NIST Center for Neutron Research,
552<A HREF="MAILTO:Brian.Toby@NIST.GOV">Brian.Toby@NIST.GOV</A>.
553
554<P>GSAS is Copyright, 1984-1997, The Regents of the University of California.
555The GSAS software was produced under a U.S. Government contract (W-7405-ENG-36)
556by the Los Alamos National Laboratory, which is operated by the University
557of California for the U.S. Department of Energy. The U.S. Government is
558licensed to use, reproduce, and distribute this software. Permission is
559granted to the public to copy and use this software without charge, provided
560that this notice and any statement of authorship are reproduced on all
561copies. Neither the Government nor the University makes any warranty, express
562or implied, or assumes any liability or responsibility for the use of this
563software.
564
565<P>The GUI is not subject to copyright. Have fun.
566
567<P>Brian Toby (<A HREF="MAILTO:Brian.Toby@NIST.GOV">Brian.Toby@NIST.GOV)</A>
568<BR>
569$Revision: 143 $ $Date: 2009-12-04 23:01:07 +0000 (Fri, 04 Dec 2009) $
570</BODY>
571</HTML>
Note: See TracBrowser for help on using the repository browser.