ViewVC Help
View File | Revision Log | Show Annotations | View Changeset | Root Listing
root/OpenMD/branches/development/README
Revision: 511
Committed: Fri Apr 15 22:43:26 2005 UTC (20 years ago) by gezelter
Original Path: trunk/README
File size: 2739 byte(s)
Log Message:
gmake in case people forget

File Contents

# User Rev Content
1 gezelter 2 OOPSE
2    
3     OOPSE is an open-source Object-Oriented Parallel Simulation Engine.
4     It is primarily used to perform molecular dynamics simulations on
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).
9    
10     Simulations are started in OOPSE using two files:
11    
12     1) a C-based meta-data (.md) file, and
13    
14     2) a modified XYZ format for initial coordinate and velocity information.
15    
16     Detailed descriptions of the structures of these two files are
17     available in the "doc" directory. Sample simulations are
18     available in the "samples" directory.
19    
20     What you need to compile and use OOPSE:
21    
22     1) Good C, C++ and Fortran95 compilers. We've built and tested OOPSE
23     on the following architecture & compiler combinations:
24    
25     Architecture CC CXX F90 Notes
26     ------------------------- ---- ----- ----- ----------------------
27     ix86-pc-linux-gnu icc icpc ifort (Intel versions 7 & 8)
28 gezelter 508 powerpc-apple-darwin7.8.0 xlc xlc++ xlf (IBM XL v. 6.0/8.1)
29 gezelter 2 mips-sgi-irix6.5 cc CC f90 (MIPSpro 7.4)
30     sparc-sun-solaris2.8 cc CC f95 (Forte Developer 7)
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
34     use a Fortran *95* compler for the fortran side of OOPSE, and
35     pgf90 does not implement the required portions of the f95
36     language. Fortran77 and Fortran90 (i.e. g77 and pgf90) are *not*
37 gezelter 508 sufficient to compile the fortran portions of OOPSE. Tests
38     with the PATHSCALE compiler on 64-bit AMD Opteron machines
39     are ongoing.
40 gezelter 2
41 gezelter 511 2) GNU make (also known as gmake). Regular make won't work.
42     Really. We've tried. Don't bother with regular make.
43     Seriously. You need GNU make. Did we mention that you
44     need GNU make?
45 gezelter 2
46 gezelter 508 3) Perl. Compilation dependencies in Fortran95 are somewhat
47     complicated, so the build process uses a perl script called
48 gezelter 511 filepp to do this job. You need perl for filepp, so you
49     need perl to build OOPSE.
50 gezelter 508
51     4) MPI is optional for the single processor version of OOPSE,
52     but is required if you want OOPSE to run in parallel.
53    
54     We like MPICH-1.2.*. Other implementations might work, but we
55 gezelter 2 haven't tried. You can get MPICH here:
56     http://www-unix.mcs.anl.gov/mpi/mpich/
57    
58 gezelter 508 5) Assorted unix utilities (lexx, yacc) or their GNU equivalents.
59 gezelter 2
60     INSTRUCTIONS
61    
62     1) Get, build, and test the required pieces above.
63 gezelter 508 2) ./configure (or ./configure --with-mpi=/usr/local/mpich)
64 gezelter 2 3) make
65     4) make install
66    
67 gezelter 508 That's it.