Changes

Page history
Update migration authored by Rainer Weinberger's avatar Rainer Weinberger
Show whitespace changes
Inline Side-by-side
userguide/migration.md
View page @ d3a0eacf
# Related codes
# Related codes
The general code structure of AREPO is similar to the GADGET code, but with The general code structure of Arepo is similar to the Gadget code, but with
significant further developments and improvements. However, keeping in mind significant further developments and improvements. However, keeping in mind
that the code architecture originates from an Tree-PM-SPH code helps to that the code architecture originates from an Tree-PM-SPH code helps to
understand why certain things are done in certain ways. understand why certain things are done in certain ways.
...@@ -15,9 +15,9 @@ presence of the neighbour tree, a search-tree structure on gas cells. In ...@@ -15,9 +15,9 @@ presence of the neighbour tree, a search-tree structure on gas cells. In
practice this means that many of the routines that depend on the state of practice this means that many of the routines that depend on the state of
neighbouring cells, including sub-grid feedback models etc., can be based on neighbouring cells, including sub-grid feedback models etc., can be based on
this neighbour search. This makes it possible to port these models from earlier this neighbour search. This makes it possible to port these models from earlier
versions of GADGET to AREPO. versions of Gadget to Arepo.
However, it is important to realize that routines written for the GADGET code However, it is important to realize that routines written for the Gadget code
will in general not work directly when ported to Arepo. We encourage developers will in general not work directly when ported to Arepo. We encourage developers
to carefully test that the implementation is still having the same effect. to carefully test that the implementation is still having the same effect.
Apart from the differences in implementation, it is also important to realize Apart from the differences in implementation, it is also important to realize
...@@ -28,7 +28,7 @@ a sub-grid implementation. ...@@ -28,7 +28,7 @@ a sub-grid implementation.
Differences to the development Version Differences to the development Version
====================================== ======================================
This public version of AREPO was branched off from the development version in This public version of Arepo was branched off from the development version in
November 2017, substantially cut down, cleand up and the documentation completed November 2017, substantially cut down, cleand up and the documentation completed
by Rainer Weinberger. The main reason for doing this is to provide a code to the by Rainer Weinberger. The main reason for doing this is to provide a code to the
community that researchers are able to understand and use without the need of community that researchers are able to understand and use without the need of
...@@ -39,7 +39,7 @@ starting point for new developments. ...@@ -39,7 +39,7 @@ starting point for new developments.
The general idea for this public verson was to preserve the well-tested code The general idea for this public verson was to preserve the well-tested code
with a limited number of changes. However, some compile-time options have been with a limited number of changes. However, some compile-time options have been
eliminated and to recover the same running mode **in the development version eliminated and to recover the same running mode **in the development version
of AREPO**, the following compile-time flags need to be set in `Config.sh` of Arepo**, the following compile-time flags need to be set in `Config.sh`
* ``PERIODIC`` (has become obsolete over the years) * ``PERIODIC`` (has become obsolete over the years)
* ``VORONOI`` (the development version also has an AMR mode) * ``VORONOI`` (the development version also has an AMR mode)
... ...
......