File: README.md

package info (click to toggle)
feff85exafs 0.2%2Bdfsg-3
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 39,276 kB
  • sloc: fortran: 271,644; f90: 121,166; ansic: 2,589; perl: 1,854; python: 1,743; ada: 1,412; makefile: 1,150; sh: 245; csh: 167
file content (42 lines) | stat: -rw-r--r-- 1,478 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
# Executable scripts for feff8l

## f85e

This is a bash script which emulates the behavior of a monolithic Feff
by running the "modules" one after another given a `feff.inp` file.

This script is used by the unit testing framework.

In its current form, it deduces the locations of the various
stand-alone executables for the modules based on the structure of the
repository.  That is, this script assumes that is lives in the `bin/`
folder of the repository and that the executables will be found in
subfolders of the `src` folder, where `bin/` and `src/` are at the
same level of the repository folder structure.

	~/feff8l/> ls -R
	./bin:
	f85e*

	./src:
	ATOM/    EXCH/  FOVRG/    JSON/  PAR/   RDINP/  FortranCompilation.py
	COMMON/  FF2X/  GENFMT/   LIB/   PATH/  XSPH/   SConstruct
	DEBYE/   FMS/   HEADERS/  MATH/  POT/   attic/  README.md

	and so on...

Eventually, an installation scripts might be written, in which case a
successor to this script will need to know (or determine) the
installation locations of the various executables.

For now, I am assuming that primary purpose of the `f85e` script is to
aid unit testing during the development of Feff8L.

# feff85_light

This is a script written by Josh.  It makes calls to executables
called `opconsat`, `atomic`, and `aps2exc`, none of which I know how
to build from the source code provided.  The text of the script
suggests that Josh intended this to be an example of using
Feff8L, but its use is unclear.