| 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 |
|
|
| 24 |
|
|
| 25 |
|
Architecture CC CXX F90 Notes |
| 26 |
|
------------------------- ---- ----- ----- ---------------------- |
| 27 |
< |
ix86-pc-linux-gnu icc icpc ifort (Intel versions 7 & 8) |
| 28 |
< |
powerpc-apple-darwin7.4.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.10 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 |
| 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 |
< |
sufficient to compile the fortran portions of OOPSE. |
| 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 |
> |
OOPSE uses features of the Fortran 95 language. The fortran |
| 39 |
> |
portions of our code will not compile if your compiler does not |
| 40 |
> |
support these particular features. Some (but not all) Fortran 90 |
| 41 |
> |
compilers do support these features. None of the Fortran 77 |
| 42 |
> |
compilers can be used to compile OOPSE. |
| 43 |
|
|
| 44 |
< |
2) The Scalable Parallel Random Number Generators Library (SPRNG). You |
| 45 |
< |
can obtain SPRNG here: http://sprng.cs.fsu.edu/ |
| 41 |
< |
SPRNG is a *requirement* for compiling OOPSE. |
| 44 |
> |
Compilers that are known to fail on OOPSE: g77, Gfortran, Older |
| 45 |
> |
Portland Group compilers (pgf77, pgf90). |
| 46 |
|
|
| 47 |
< |
3) MPI. We like MPICH. Other implementations might work, but we |
| 47 |
> |
Compilers that are known to work on OOPSE: Intel's ifort, |
| 48 |
> |
Pathscale's pathf95, IBM's xlf95, Portland's pgf95 (version 6 or |
| 49 |
> |
higher), Sun's f95. There may be others that work also. |
| 50 |
> |
|
| 51 |
> |
2) GNU make (also known as gmake). Regular make won't work. |
| 52 |
> |
Really. We've tried. Don't bother with regular make. |
| 53 |
> |
Seriously. You need GNU make. Did we mention that you |
| 54 |
> |
need GNU make? |
| 55 |
> |
|
| 56 |
> |
3) Perl. Compilation dependencies in Fortran95 are somewhat |
| 57 |
> |
complicated, so the build process uses a perl script called |
| 58 |
> |
filepp to do this job. You need perl for filepp, so you |
| 59 |
> |
need perl to build OOPSE. |
| 60 |
> |
|
| 61 |
> |
4) MPI is optional for the single processor version of OOPSE, |
| 62 |
> |
but is required if you want OOPSE to run in parallel. |
| 63 |
> |
|
| 64 |
> |
We like MPICH-1.2.*. Other implementations might work, but we |
| 65 |
|
haven't tried. You can get MPICH here: |
| 66 |
|
http://www-unix.mcs.anl.gov/mpi/mpich/ |
| 46 |
– |
MPI is only required if you want a parallel version of OOPSE. |
| 67 |
|
|
| 48 |
– |
4) Assorted unix utilities (lexx, yacc, make) or their GNU |
| 49 |
– |
equivalents. The Gnu version of make is pretty much a requirement on |
| 50 |
– |
SGI machines. |
| 51 |
– |
|
| 52 |
– |
|
| 68 |
|
INSTRUCTIONS |
| 69 |
|
|
| 70 |
|
1) Get, build, and test the required pieces above. |
| 71 |
< |
2) ./configure |
| 71 |
> |
2) ./configure (or ./configure --with-mpi=/usr/local/mpich) |
| 72 |
|
3) make |
| 73 |
|
4) make install |
| 74 |
|
|
| 75 |
< |
That's it. Documentation will be forthcoming after the paper is |
| 61 |
< |
published. |
| 62 |
< |
|
| 75 |
> |
That's it. |
