FAC is a software packge for the calculation of various atomic processes.

Contact: Bugs, and suggestions, please report to:

mfgu@stanford.edu Ming Feng Gu. Physics Department Stanford University

Hi Fernando-

tng: I am not sure, but it could be SAOtng, and this is the predecessor of ds9, so we wouldn't 
need it.

FAC: is the Flexible Atomic Code by Ming-Feng Gu. I doubt that anybody would need it here 
anymore (except perhaps Daniel Savin and his group). In case you need it: 




There are two interfaces available to the FAC numerical lib. One makes use
of the Python scripting language, implemented as a package "pfac".
The other interface uses a simple command parser, compiled into executables. 
The two interfaces are independent. Either one or both can be installed.

1) ./configure
Note 1: Specify the option --with-cfortran=xxFortran, if you F77 compiler 
        is not g77 or sun's f77. see faclib/cfortran.doc for supported F77 
Note 2: If your C compiler is not gcc, then you need to supply the PIC
	(position independent code) option with --enable-cpic=***
	If your F77 compiler is not g77, then you need to supply the PIC
	option with --enable-fpic=***
	Supply the optimization option for C and F77 compilers with
	--enable-copt=*** and --enable-fopt=*** respectively if desired.
Note 3: specify --prefix=my/dir, if the default /usr/local is not what you 
	want. This dir only affects the installation of SFAC executables.
Note 4: some of the functions have a parallel version using MPI. You can build 
        with MPI enabled using the option --with-mpi=***, where *** is the MPI
	implementation installed on your machine. It has been tested with lammpi.
	If a different version of MPI is used, you have to supply the compile and
	link flags to the C compiler with --with-mpicompile and --with-mpilink.
	A modified python interpretor will be built in the python/ dir, which is 
	called mpy. This interpretor should be used instead of the standard Python
	when using the parallel version.

2) make; make install
This installs the SFAC interface.

3) If you have Python 2.0 or later installed, then:
   make pfac
   make install-pfac
This installs the PFAC interface into Python's default site-package dir. If
this is not what you want, or you don't have the permision. then, instead of
running "make install-pfac", try:

   python setup.py install --prefix=/my/own/dir

In order for python to find the installed "pfac" modules, one would have to 
define an environment variable PYTHONPATH to point to the directory 
"/my/own/dir/lib/python#.#/site-packages", where "#.#" is the Python version.
In csh, this requires 

    setenv PYTHONPATH /my/own/dir/lib/python#.#/site-packages 

or in bash, 

    PYTHONPATH=/my/own/dir/lib/python#.#/site-packages;export PYTHONPATH

Alternatively, one may do:

   python setup.py install --home=/my/own/dir

in this case, PYTHONPATH should be set to "/my/own/dir/lib/python. There
are some other ways to specify where you want the python modules go. Check
the python distutil documentation for details.

The modules can be called just like any python modules, either from the
interpreter interactively, or pass the script to python. 
e.g., python fe24_level.py.

The non-python interface produces 3 executables, "sfac", "scrm" and 
"spol", accepting input files as arguments. The syntax of the input file 
for both programs is identical, and is very similar to the Python syntax,
except for the missing of flow constrols.

For more details, please read the manual, and be sure to read the FAQ 
section of the manual. 

Bugs, and suggestions, please report to:
	Ming Feng Gu.
	Physics Department
	Stanford University