Posts by author vanelteren

Amuse version 7.1 released

Today we created a new minor release of AMUSE (version 7.1).

This is a minor release, mostly focussed on fixing bugs in the binaries:

  • Detection of binary release in tests and skipping of tests that need a compiler
  • Update of the mocassin radiative transfer code to 2.02.70
  • Implementation of AMUSE storage format v2.0 (work in progress, not recommended for production use). The default format in this release is still 1.0
  • Update of SeBa to the latests code

The code can be download from the amuse site:  http://www.amusecode.org/

  • Posted: 2012-12-06 14:11 (Updated: 2012-12-06 14:13)
  • Author: vanelteren
  • Categories: (none)
  • Comments (0)

Amuse version 7.0 released

Today we created a new release of AMUSE (version 7.0).

Main items in this release:

  • Several bug fixes and some stability improvements.
  • Updated radiative transfer codes, based on two workshops we have upgraded the integration of two radiative transfer codes (Simplex and SPHray)
  • Enabled support for the pre-main-sequence stellar evolution in the MESA community code.
  • Updated all grid based hydrodynamics codes (Athena, Capreole and MpiAmrVac?). Both Athena and Capreole now support custom user defined boundary conditions, see the grid boundary tutorial.
  • Binaries for Linux and OS X are provided, although not all community codes are fully functional yet (see notes)

The code can be download from the amuse site:  http://www.amusecode.org/

Amuse binary build

Today we announce the availability of AMUSE binary builds.

The binary builds do not depend on any support packages and can be run right after unpacking.

We currenlty provide the following binary builds:

Linux 64bit amuse-latests-Linux_x86_64.tar.gz
OS X 32bit amuse-latests-Darwin_i386.tar.gz
OS X 64bit amuse-latests-Darwin_x86_64.tar.gz

These binaries are updated every day.

Usage:

  1. unpack the package (tar -xvf amuse-latests-Linux_x86_64.tar.gz)
  2. cd to the directory
  3. run ./amuse

This will open an interactive python shell with amuse in the python path.

An example session to run a simple nbody simulation

from amuse.lab import *
code = Hermite()
code.particles.add_particles(new_plummer_model(100))
code.evolve_model(1 | nbody_system.time)
print code.kinetic_energy
print code.potential_energy

You can continue by following the Getting started with AMUSE documentation.

The binary release should run but is still a work in progress, if you encounter any problems please contact us.

  • Posted: 2012-03-01 11:00 (Updated: 2012-03-01 11:02)
  • Author: vanelteren
  • Categories: (none)
  • Comments (0)

Amuse version 5.2 released

Today we created a new release of AMUSE (version 5.2).

Main items in this release:

  • Several bug fixes and some stability improvements.
  • The treatment of multiples and the coupling of gravity forces between codes (BRIDGE) has been improved.
  • The number of community codes in AMUSE has increased. Several researchers have included their gravity codes in AMUSE.
  • Removing unnecessary units (not finished yet). The string unit has been removed from the system. Particle sets and Grids can now store attribute values without units.

The code can be download from the amuse site:  http://www.amusecode.org/trac/wiki/releases

Changes in several names in the AMUSE code-base

state attributes

We have removed the concept of "state" and "normal" attributes. The difference between "state" and "normal" attributes was never completely worked out.

Originally a code could have "state" attributes that captured the minimal state of the particles or gridpoints of a code. For example a gravitational dynamics code will have "position", "mass" and "velocity" for the state attributes, but the particles can also have "acceleration", "radius" or "potential". In practice we never made good use of this facility and it only made the code hard to read.

Most of this removal is internal to the AMUSE code and should not impact users. The most public change is in the method copy_values_of_state_attributes_to. This method is now called copy_values_of_all_attributes_to. For all scripts in subversion we have updated the code.

evolve and evolve_model

We renamed evolve to evolve_model. The evolve method was defined on most low-level code interfaces. And evolve_model was used in all high-level code. This made it harder to remember the right method to call. We changed all the evolve methods on the low-level interfaces to match the name used in the high-level interfaces. As most scripts will use the high-level interface this should not impact most existing scripts.

Exceptions:

  • sse: evolve was renamed to evolve_star
  • bse: evolve was renamed to evolve_binary

If you're scripts should fail to work after an svn update please send an e-mail to the amuse  mailinglist.

Announcement: Third AMUSE workshop June 27th - July 1st 2011

We are organizing the next AMUSE workshop in Leiden (June 27th - July 1st 2011).

Details can be found on the Third Workshop Page.

AMUSE Weekly Summary, March 28 / April 1, 2011

Last week we saw the release of AMUSE 4.0 amuse-4.0.tar.gz. In this weekly, we will give a short overview about the major changes in this release.

The AMUSE 4.0 release contains an almost complete set of codes and supports multiple methods of interaction between these codes.

New codes

We added support for 2 radiative transfer codes (Mocassin and Simplex), see the iliev test 5 for an example of coupling Simplex with a SPH code.

The gravity domain got extended with added MMC (a Monte Carlo gravity code) and ph4 (Parallel Hermite 4 gravity code). We also integrated AMRVAC (an AMR hydrodynamics code).

Coupling

We implemented a generic function to transform a stellar evolution 1d shell model (from EVTwin or MESA) into a SPH particles model (for an example see hydro_star example). Work is underway to do the reverse.

Gravity and SPH codes can be coupled using a method (bridge) based on Hamiltonian splitting. This method can be used to couple gravity codes (see the validate bridge example ) or provide and external gravity field on a code (see the galactic center example)

The hydro grid codes can be supplied with an external acceleration (Capreole and MPIAMRVAC) or potential field (Athena). For a steady state example see the plummer sphere on grid example.

  • Posted: 2011-04-04 10:47 (Updated: 2012-12-06 14:27)
  • Author: vanelteren
  • Categories: (none)
  • Comments (0)