Astrophysical Multipurpose Software Environment. This is the main repository for AMUSE
AMPL Fortran Objective-C C Python C++ Other
Clone or download
Permalink
Failed to load latest commit information.
.github/ISSUE_TEMPLATE Add issue templates Jun 7, 2018
data Working on EVtwin interface: data directory Jun 13, 2014
doc possible fix for documentation generation Jul 11, 2018
examples updated rad_minimum smaller than sign change Jun 21, 2018
lib fix copy of libs (no src files) and fix hash test for python 3 Jul 6, 2018
m4 working on better configuration for python dev Apr 11, 2017
src/amuse fix for distributed amuse failure to parse config Jul 10, 2018
support removal of unused mail notifier Jul 11, 2018
test Merge pull request #272 from egpbos/dynamic_build_tests Jul 10, 2018
.gitignore small edits to gitignore Jun 28, 2018
.travis.yml fix parse error Jul 10, 2018
CONTRIBUTING.md Add missing reference to AMUSE style guide Jun 8, 2018
LICENSE added license and notice Jun 16, 2017
MANIFEST.in Update build files to not use support3/ modules anymore Jun 28, 2018
Makefile some extra cleanup in Makefile Jul 7, 2018
NOTICE update year May 1, 2018
README.md Merge pull request #244 from egpbos/add_travis_ci Jun 26, 2018
aclocal.m4 experimental code to run amuse without mpi_comm_spawn Feb 26, 2016
amuserc.example document the AMUSERC environment variable in amuserc.example Oct 6, 2016
build.py.in Update build files to not use support3/ modules anymore Jun 28, 2018
config.mk.in only export if exists... Jul 10, 2018
configure Update build files to not use support3/ modules anymore Jun 28, 2018
configure.ac Update build files to not use support3/ modules anymore Jun 28, 2018
cuda_self_help rename legacy_tests directory to codes_tests directory, see ticket #182 Jan 17, 2011
ez_setup.py updated ez setup from upstream repository Jun 19, 2015
setup.py fix configurecodes Jul 6, 2018
slowtests Added script to also run slowtests, tests turned off by default for s… Jul 5, 2010

README.md

Build Status

This directory contains the AMUSE software. With AMUSE you can write scripts to simulate astrophysical problems in different domains.

The documentation and the software can be found at:

Getting Started

To build amuse you need a working build environment and install some prerequisites. This document contains the quick install instructions, if these fail please look at the detailed descriptions of the installation procedure in the documents in the 'doc/install' directory.

Compilers

To build AMUSE from source you need to have a working build environment. The AMUSE build system needs a C++ and a fortan 90 compiler. Please check first if you have a working build environment on your system.

In Ubuntu you can setup the environment with (as root):

apt-get install build-essential curl g++ gfortran gettext zlib1g-dev

In Fedora you can setup the environment with (as root)::

yum groupinstall "Development Tools" "Development Libraries"

In OS X you can install homebrew or macports package managers (both need the Apple Developer Tools). If you do not want to use any of these package managers you will need to install a fortran compiler as the Apple Developer Tools do not include a fortran compiler, you can find one at:

Installing Prerequisites

This document describes installation of the pre-requisite software packages to a user directory. If you have a recent Ubuntu or Fedora distribution you can follow the installation instructions in doc/install/howto-install-prerequisites.txt to install the packages as part of the system.

  1. Make a prerequisite software directory (can be set to any directory)

    mkdir ~/amuse/prerequisites
  2. Set the PREFIX, PATH and LD_LIBRARY_PATH environement variables

    export PREFIX=~/amuse/prerequisites
    export PATH=${PREFIX}/bin:${PATH}
    export LD_LIBRARY_PATH=${PREFIX}/lib:${LD_LIBRARY_PATH}

    2b. If you have ifort and/or icc, or if you encounter problems with NetCDF (optional dependency) you may need to set also:

    export LIBRARY_PATH=${PREFIX}/lib:${LIBRARY_PATH}
    export CPATH=${PREFIX}/include:${CPATH}
  3. Download and install python

    cd doc/install
    ./install-python.sh
  4. Download and install the other pre-requisites (script is also in the doc/install directory)

    ./install.py install

Set Environment

You can set the the PREFIX, PATH and LD_LIBRARY_PATH environment variables in you bashrc file. Please make sure the ${PREFIX}/bin directory is first in the path.

In bash, you can extend your .bashrc file with:

export PREFIX=~/amuse/prerequisites
export PATH=${PREFIX}/bin:${PATH}
export LD_LIBRARY_PATH=${PREFIX}/lib:${LD_LIBRARY_PATH}

Building AMUSE

All modules can be build with a configure and make command. Start make from the main amuse directory (directory this README file lives in). The main task of the configure script is to check if the prerequisite packages have been installed.

  1. Configure the source code

    ./configure
  2. Build the code with make

    make

Running the tests

AMUSE comes with a large set of tests, most can be run automatically. To run these tests start the nosetests command from the main amuse directory (directory this README file lives in).

To run these tests do:

  1. Run the automatic tests
nosetests -v