 |
|
Документ взят из кэша поисковой машины. Адрес
оригинального документа
: http://www.adass.org/adass/proceedings/adass00/P1-39/
Дата изменения: Tue May 29 19:51:53 2001 Дата индексирования: Tue Oct 2 05:44:30 2012 Кодировка: Поисковые слова: п п п п |
NEMO (Teuben 1994) and Starlab are traditional programming environments with which N-body simulations can be setup, run, and analyzed. NEMO also has a number of tools to import and export data in tables, CCD type images, FITS files, and a large number of other N-body formats. NEMO is geared more towards collisionless stellar dynamics, while Starlab has more sophisticated programs to deal with close encounters, and can now also incorporate stellar evolution through the SEBA package (Portegies Zwart et al. 2001). NEMO and Starlab present themselves to a user as a large set of programs, often glued together using pipes in shell scripts to set up and run complex simulations. For the programmer, a large set of classes and functions are available to construct new integrators and analysis programs. For example, in the following Starlab example an anisotropic King model with 2048 particles has been evolved with 50% binaries (i.e., 3096 actual stars) and stellar evolution:
mk_aniso_king -i -n 2048 -u -w 4 -F 3 |\ mkmass -i -u 100 -l 0.1 -f 3 |\ mksecondary -f 0.5 -l 0.1 |\ addstar -Q 0.5 -R 2.5 |\ scale -M 1 -E -0.25 -Q 0.5 |\ mkbinary -f 2 -l 1 -u 1000000 -o 2 |\ kira -a 0.1 -d 1 -D 25 -n 25 -t 4000 -Q -G 2 -u -B -z 1 > run001
The GRAPE special purpose hardware (Hut & Makino 1999), now running at 100 TerraFlops speed, has been successfully interfaced with Starlab, and now is starting to produce massive datasets. Analysis and visualization techniques of those dataset are becoming increasingly challenging.
|
The American Museum for Natural History (AMNH) in New York City has recently renovated its planetarium, and converted it into a state-of-the-art digital planetarium with capabilities for scientific visualization. Their computer system consists of an Onyx2, with 28 CPUs, 14GB of memory, 2TB diskspace and 7 graphics pipes. Each graphics pipe controls one of 7 projectors which illuminate the dome in a dodecahedral pattern. The software that drives most visualization is an NCSA product called Virtual Director ( virdir), that we have now been using during a number of night sessions in the dome, much like optical observers (during daytime the planetarium is of course used for public viewing). It allows us to ``fly'' through the data, in space and time. By adding complete orbital information for a select number of stars we have started fully interactive data mining of our 4-D spacetime histories of these star cluster simulations runs. In order for us to test new visualization techniques, algorithms and interfaces with the Starlab environment, we used an existing program partiview, which had been derived from virdir, and which can be run on a normal workstation or laptop. It uses the FLTK and MESA/OpenGL libraries for its user interface and fast graphics. A screenshot of partiview in action can be seen in Figure 1. We have modified partiview to understand our Starlab simulation data, and added interfaces that allow this workstation version to animate and move in time and space. partiview comes with a small but powerful set of commands with which dataselections and viewing can be made, and we hope to expand this into a more mature scripting language. It is also fairly straightforward for other packages to benefit from using partiview.
In the spirit of the federated model of archiving observational data, recently proposed by the National Virtual Observatory (NVO) initiative, we will develop a Starlab-based archive. A simulation of a globular cluster with a million stars stars for ten billion years will generate 100TB of raw data, of which we would like to store at least 1TB, and preferably more, for 4-D visualization of the full history of the evolution of a star cluster. Although our main goal will be to enable rapid and intelligent access to our simulation output files, we will simultaneously develop a flexible and transparent interface with the NVO database and protocols. Our Starlab policy will be to make all simulation results freely and publicly available to `guest observers.'
Hut, P. & Makino, J. 1999, Science, 283, 64
Portegies Zwart, S. F., McMillan, S. L. W., Hut, P., & Makino, J. 2000, MNRAS, 321, 199
Teuben, P. J. 1994, in ASP Conf. Ser., Vol. 77, Astronomical Data Analysis Software and Systems IV, ed. R. A. Shaw, H. E. Payne, & J. J. E. Hayes (San Francisco: ASP), 398