THE DARKSTAR PROJECT
The Structure of DarkStar


DarkStar Layout


Construction Details


The Makers of DarkStar


Our Sponsor


Get DarkStar
[GIF MAP: The DarkStar Poster] Using DarkStar


Solving Problems


Star Evolution


Software Spinoff


Warning !
Ignition !
(click around somewhere if you wish to do so)

Some words from our director:

"The aim of the software odysee baptised DarkStar was to provide a set of modern software modules to ease the development and improve the modularity of stellar structure and evolution computations.

Basically all stellar structure codes in use still today rely on the concepts developed and found feasible in the 1960s (almost all are based either on Kippenhahn's, Paczynski's, or Iben's philosophy). As generations of students modified and enlarged these codes they became increasingly more incomprehensible, prone for inconsistencies, and in particular hard to modify to tackle various differing questions in stellar physics.

With the availability of FORTRAN 90 the scientific computing community got a very handy and powerful software tool with all the benefits of the old numerical handiness of the old FORTRAN.

DarkStar as it stands at the moment provides its users with a set of modules on different levels (numerical solvers, equations, physics, and drivers for boundary-value solutions as well as time evolution) to solve initial-boundary value problems. As our aim was an improved numerical and conceptual dealing with stellar structure questions we concentrated the equation and physics section thereupon. However, any kind of boundary-value problem can be dealt with with DarkStar.

The modules are built in such a way that the user can either plug in the canonical ones provided by us or write his/her own ones. The implementation of own pieces of routines is standardized in such a way that it should stimulate experimentation with whatever the particular topic is which is to be investigated. The separation of the modules is designed in such a way that macrophysics, microphysics, and numerics are completely separated so that the user can really concentrate on *that* subject in which he is interested at a particular instance without worrying about the interaction and the remaining set-up of the program.

If the code could be used successfully for your applications, please drop us a note."

Home


last update 12 Nov 2008, U.Grabowski