ViewVC Help
View File | Revision Log | Show Annotations | View Changeset | Root Listing
root/group/trunk/OOPSE-4/README
(Generate patch)

Comparing trunk/OOPSE-4/README (file contents):
Revision 2208 by gezelter, Fri Apr 15 22:43:26 2005 UTC vs.
Revision 2568 by gezelter, Mon Jan 16 23:10:15 2006 UTC

# Line 5 | Line 5 | Embedded Atom Method (EAM).
5   "strange" atom types that are not normally handled by other simulation
6   packages.  This includes atoms with orientational degrees of freedom
7   (point dipoles, sticky atoms), as well as transition metals under the
8 < Embedded Atom Method (EAM).
8 > Embedded Atom Method (EAM) or Sutton-Chen (SC) potentials.
9  
10   Simulations are started in OOPSE using two files:
11  
# Line 24 | Line 24 | What you need to compile and use OOPSE:
24  
25      Architecture                CC     CXX     F90    Notes
26      -------------------------   ----   -----   -----  ----------------------
27 <    ix86-pc-linux-gnu           icc    icpc    ifort  (Intel versions 7 & 8)
28 <    powerpc-apple-darwin7.8.0   xlc    xlc++   xlf    (IBM XL v. 6.0/8.1)
29 <    mips-sgi-irix6.5            cc     CC      f90    (MIPSpro 7.4)
30 <    sparc-sun-solaris2.8        cc     CC      f95    (Forte Developer 7)
27 >    ix86-pc-linux-gnu           icc    icpc    ifort  (Intel versions 7-9)
28 >    powerpc-apple-darwin8.4.0   gcc    g++     xlf    (GNU v.4 / IBM XL v. 8.1)
29 >    x86_64-unknown-linux-gnu    pgcc   pgCC    pgf95  (Portland Group v. 6.0)
30 >    sparc-sun-solaris2.8        cc     CC      f95    (Sun ONE Studio 10)
31      
32 <    We've successfully compiled OOPSE with gcc and g++, as well as
33 <    pgcc and pgCC in linux environments.  However, you will need to
32 >    We've successfully compiled OOPSE with the Pathscale c, c++, and
33 >    Fortran95 compilers on the  x86_64-unknown-linux-gnu architecture,
34 >    but a bug in the exception handling on these compilers causes
35 >    OOPSE to abort (rather than providing a useful error message) when
36 >    an error is found in the meta-data file.
37 >  
38 >    The GNU compilers, gcc and g++, work very well, but you will need to
39      use a Fortran *95* compler for the fortran side of OOPSE, and
40      pgf90 does not implement the required portions of the f95
41      language.  Fortran77 and Fortran90 (i.e. g77 and pgf90) are *not*
42 <    sufficient to compile the fortran portions of OOPSE.  Tests
43 <    with the PATHSCALE compiler on 64-bit AMD Opteron machines
44 <    are ongoing.
42 >    sufficient to compile the fortran portions of OOPSE.   Gfortran
43 >    does not yet build our fortran code, but g95 might.  If you use
44 >    one of these compilers, please let us know of any build or runtime
45 >    errors.
46  
47   2) GNU make (also known as gmake).  Regular make won't work.  
48      Really.  We've tried.  Don't bother with regular make.  
# Line 55 | Line 61 | What you need to compile and use OOPSE:
61      haven't tried.  You can get MPICH here:
62      http://www-unix.mcs.anl.gov/mpi/mpich/
63  
58 5) Assorted unix utilities (lexx, yacc) or their GNU equivalents.
59
64   INSTRUCTIONS
65  
66   1) Get, build, and test the required pieces above.

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines