There are two ways of customizing the behavior of ATOMS. One is to use the output template files described in Chapter and Appendix to control the output data from an ATOMS run. The other is to use the runtime configuration file to control how ATOMS behaves while running. The configuration options in the runtime configuration file are the topic of this chapter.
The default runtime configuration file is found in the 'lib/' subdirectory where ATOMS is installed. It is called 'atomsrc'. When ATOMS starts running, one of the first things it does is to read this file and use its contents to set certain defaults. On a multiuser system such as Unix, VMS, or Windows NT, the individual user can keep a runtime configuration file which is different from the system-wide file. ATOMS first reads the system-wide file, then searches for the user's personal file. If found, the personal file is used to override the settings from the system-wide file. On any kind of Unix machine, the personal runtime configuration file is kept as '$HOME/.atoms/atomsrc'. $HOME represents the user's home directory. The user's runtime configuration file is kept is the same '.atoms/' directory where custom atp files (see Chapter ) are kept. On a VMS machine, the user's runtime configuration file is kept in >undecided?. On a networked Windows NT machine it is kept in >undecided?. On Macintoshes and Windows 9x machines, there is no concept of a user directory thus ATOMS does not search for a user's runtime configuration file
The runtime configuration file uses Perl's syntax and is interpreted by ATOMS as perl code. If you are unfamiliar with Perl's syntax, just follow the examples given in the supplied 'atomsrc' file when you modify it. The best way to make a personal runtime configuration file is to copy the system-wide file to your '.atoms/' directory and edit it as desired.
This list describes the things that can be customized using the runtime configuration file. See Section for an explanation of the configuration utility in TkATOMS, which can be used to modify the variables on the fly.
Of all these variables only $prefer_feff_eight has any effect on WebATOMS, although in the future cookies might be used to replicate the behavior of $atoms_language.
======================================================================= Atoms 3.0beta1 (linux) 2001/01/07 ======================================================================= titre > YBCO: Y Ba2 Cu3 O7 feff: Ecrit le fichier dans feff.inp =======================================================================Figure : Screen output of ATOMS in French.
======================================================================= Atoms 3.0alpha21 (linux) 2001/01/07 ======================================================================= titulo > YBCO: Y Ba2 Cu3 O7 feff: Escribiendo archivo en feff.inp =======================================================================Figure : Screen output of ATOMS in Spanish. The most powerful feature of the configuration file is the ability to set the language used by ATOMS during operation. This is demonstrated in Figures and . By setting the $atoms_language variable to french, spanish, or german, virtually every text string written by ATOMS or TkATOMS will be written in that language. It is my intention that ATOMS be a true polyglot. Currently I only have translations into French, Spanish, and German, however I will happily add any new language to ATOMS if I am given a translation. From the experiences of the people who made the translations, it takes a native speaker with a good command of English about 4 hours to translate all the text data. With the release of perl 5.6, Unicode is fully supported by perl and perl/Tk. This gives ATOMS the ability to speak virtually any language, including many Asian languages. Anyone interested in translating the text data into their native tongue should contact me.