Issue |
A&A
Volume 369, Number 2, April II 2001
|
|
---|---|---|
Page(s) | 706 - 728 | |
Section | Section $secnum inconnue | |
DOI | https://doi.org/10.1051/0004-6361:20010157 | |
Published online | 15 April 2001 |
A 3D MHD model of astrophysical flows: Algorithms, tests and parallelisation
Astronomy Division, Department of Physical Sciences, PO Box 3000, 90014 University of Oulu, Finland
Corresponding author: M. J. Korpi, Maarit.Korpi@oulu.fi
Received:
22
December
2000
Accepted:
24
January
2001
In this paper we describe a numerical method designed for modelling different kinds of astrophysical flows in three dimensions. Our method is a standard explicit finite difference method employing the local shearing-box technique. To model the features of astrophysical systems, which are usually compressible, magnetised and turbulent, it is desirable to have high spatial resolution and large domain size to model as many features as possible, on various scales, within a particular system. In addition, the time-scales involved are usually wide-ranging also requiring significant amounts of CPU time. These two limits (resolution and time-scales) enforce huge limits on computational capabilities. The model we have developed therefore uses parallel algorithms to increase the performance of standard serial methods. The aim of this paper is to report the numerical methods we use and the techniques invoked for parallelising the code. The justification of these methods is given by the extensive tests presented herein.
Key words: magnetohydrodynamics / turbulence / shock waves / methods: numerical / galaxies: ISM / accretion, accretion disks
© ESO, 2001
Current usage metrics show cumulative count of Article Views (full-text article views including HTML views, PDF and ePub downloads, according to the available data) and Abstracts Views on Vision4Press platform.
Data correspond to usage on the plateform after 2015. The current usage metrics is available 48-96 hours after online publication and is updated daily on week days.
Initial download of the metrics may take a while.