2.4. Limitations of Tracks and Recipes
Alice: Let me come back to my previous objection. You admitted that we
know rather little about the evolution of contact binaries. What is
the point of computing detailed stellar evolution models if there are
vast areas of stellar evolution where we don't even have a clue of
what is going on, beyond a qualitative hand-waving hunch? Take the
case of common envelope evolution. If a white dwarf starts to spiral
in toward the core of a red giant, it seems plausible from an
energetic argument that the envelope of the giant might be lost before
the white dwarf reaches the core, leaving behind a tight pair of what
will look like two white dwarfs. And it seems equally plausible that
not enough mass is lost not fast enough, and that the white dwarf will
merge with the core. Detailed 3D calculations of this process are
very hard to do, given the fact that the initial stages cover very
many dynamical crossing times.
Given this fundamental uncertainty, why bother doing detailed
calculations elsewhere in a simulation? A chain is as weak as its
weakest link. It seems like a waste of computer time and software
effort to build some very strong and detailed links as long as other
links such as common envelope evolution are too weak to contemplate.
Bob: To some extent I agree with you. First of all, okay, I see no
use for live stellar evolution codes to compute the evolution of
single stars, within a stellar dynamical simulation. And as a second
okay, I agree that even the evolution of primordial binaries can be
treated adequately through a combination of recipes and stellar
evolution tracks. Where I differ from you is in my view of the
treatment of merger products.
Alice: Before we get to differences, let me point out that your first
and second okay are very different types of okay. The first one
applies to the use of relatively accurate and robust information.
There is pretty good agreement between different stellar evolution
experts as to the quantitative behavior of the tracks of normal stars,
apart from perhaps the very most massive stars. Your second okay
addresses the use of rather ad hoc and rough treatments of binary star
evolution, where quantitative certainty is far less good, some would
say almost absent.
Bob: Yes, I agree with all that, but what can a poor boy do? We do
the best we can. And in order to get at least some new insight in the
evolution of star clusters, I think those tracks and recipes are good
enough, even though the latter are far from ideal, of course. But let
me move on to my main difference with your view. Whenever two stars
collide with each other and merge, you wind up with a merger product
that is totally unlike the type of normal ZAMS (zero age main
sequence) star that stellar evolution tracks all start with.
A merger remnant has not only a very different metallicity than
ZAMS stars in the same cluster had, what is worse, the chemical
composition is different at different radii in the star, due to
incomplete mixing during the collision, which in general will be
significantly off center. In addition, for a hundred million years
or so, the merger product will be out of thermal equilibrium, and
therefore will have a quite different structure from a normal star.
The only way you are getting even roughly close to determining the
structure of such a star is to use not only a live stellar evolution
code, but also a live hydrodynamics code to follow the collision.
So what I envision is that when two stars come close together within
the stellar dynamics part of the simulation, these point particles are
handed over to a hydrodynamics code, which replaces them with blobs of,
say, SPH particles, layered in the proper way as specified by the
stellar evolution information in the simulation. From this point on,
the power of SPH is let loose until we arrive at a dynamically settled
merger remnant. A stellar evolution code will then follow the thermal
settling, as well as the subsequent more normal evolution.
But if this does not convince you, consider what happens subsequently
with a merger remnant. It will be formed in the core of the cluster,
most likely, since there the chance for collisions is highest. It
will remain in the core, since on average it will be more massive than
typical single stars. Therefore, it will stand a significant chance
to undergo yet another collision, or be captured as a binary member in
an exchange reaction. Even if it avoids collision through such a
three-body dance, subsequent evolution is likely to lead to mass
overflow. How can you possibly use recipes to treat mass overflow
between stars that are not parametrized only by mass and chemical
composition, but by the full functional dependence of weird
composition gradients, and are possibly still out of thermal
equilibrium?
To sum up, while it is possible to make tables of stellar evolution
tracks for unperturbed stars, and while it is just possible to combine
pairs of these tracks with elaborate prescriptions for any conceivable
combination of two stars in orbit around each other, it is utterly
impossible to prepare beforehand for all types of strange merger
remnants that can be formed, let alone for their subsequent interactions.