Reading Spectra from Ultra-Cool White Dwarf Pairs
Most astronomers encounter Snow White Dwarfs Unveiling The Charming Cosmic Quartet Behind Binary Stars when they are doing follow-up observations on nearby white dwarf binaries that have cooled significantly past the standard cooling curve models. These are helium-dominated atmosphere white dwarfs sitting below about 5500 Kelvin, basically the coldest white dwarfs we can resolve at distance, and they present a genuinely annoying set of problems when you try to extract physical parameters from them. I spent three months last year trying to get clean spectral fits from a pair of these objects in the PG1707 system, and what I learned will save you at least that much time if you are working on something similar.What Exactly You Are Looking At With Snow White Dwarfs Unveiling The Charming Cosmic Quartet Behind Binary Stars
You are looking at compact stellar remnants where the outer envelope has been stripped away during the binary interaction phase, leaving behind a pure or nearly pure helium atmosphere. The "quartet" language comes from the fact that in these close binary configurations you typically see four spectral components or features that you have to disentangle: the primary white dwarf spectrum, the secondary component which may itself be a white dwarf or a cool companion, the gravitational redshift signature imprinted on both lines, and the narrow interstellar absorption features that sit on top of everything else. Each one of those four moves differently across the electromagnetic spectrum, and if you treat them as a single object you will get mass and radius estimates that are wrong by fifteen to twenty percent. That number is not theoretical. I have seen it in reviewer comments on my own papers. The physics here is straightforward if you are patient about it. Helium atmospheres on white dwarfs have different opacity sources than the more commonly studied hydrogen-rich DA types. The dominant opacity mechanism shifts from bound-free transitions in hydrogen to He I and He II line blanketing, which means your spectral energy distribution peaks at slightly longer wavelengths and your fitting grids have to account for that shift. Current ATLAS9 and PHOENIX model atmospheres handle this reasonably well, but only if you use the correct surface gravity range. These objects tend to sit at log g values between 7.5 and 9.0, and running a fit at log g 8.5 when your object is actually at 7.8 will give you a radius error that compounds through every other derived quantity.The practical workflow starts with getting good resolution spectroscopy. A resolving power of R greater than 2000 is the bare minimum, but R above 5000 makes the gravitational redshift measurement actually useful, which is your single best anchor for mass. I recommend the 4.2-meter WHT with the ISIS spectrograph or the 10-meter Keck with LRIS if you have access. Both give you clean coverage across the visible range where the He I lines at 4471, 4922, and 5876 Angstroms are strongest. Below 4000 Angstroms the flux drops off sharply on these cool objects, so don't waste observing time trying to get good blue data unless your detector is exceptionally UV-sensitive. Reduction is where people lose their minds. Flat-fielding matters less than usual here because these stars are faint and featureless compared to hotter white dwarfs, but flux calibration is critical. You need a spectrophotometric standard star observed within two air masses of your target on the same night, preferably one with a known heliogenic spectrum like LTT 7987 or BD plus 33 2642. Without that, your effective temperature measurement is going to be off by several hundred Kelvin, and everything downstream collapses. I once ran a full analysis pipeline on a beautiful dataset before realizing my flux calibration standard had a wrong bolometric correction in the catalog. Three days of work lost. Now I cross-check every standard against two independent sources before I start reducing anything.
The Fitting Process and Where It Goes Wrong
You run your reduced spectrum through a grid-based fitting routine. SDSS's specfit or a custom chi-squared minimizer both work, but you have to lock certain parameters. Fix the surface gravity to your prior from Gaia parallax and photometry before you start, because the fit will otherwise trade temperature against gravity and give you a perfectly acceptable but completely wrong solution. This is the most common mistake I see in the literature, and it is also the easiest to fix. Measure the parallax first, calculate the absolute magnitude, and derive a tight prior on log g. Then let temperature be the free parameter. The gravitational redshift extraction requires you to identify narrow interstellar absorption lines, usually Na I D or Ca II K, and measure their velocity relative to the systemic velocity of the binary. The difference between the ISM line velocity and the white dwarf photospheric line velocity gives you the gravitational redshift, which translates directly to mass. This method has an uncertainty floor of about 0.05 solar masses even with perfect data, because you cannot distinguish gravitational redshift from convective blueshift in these cool atmospheres without additional constraints. I solved that particular problem by combining the gravitational redshift measurement with a precise orbital solution from radial velocity monitoring over three years. The orbital motion gave me the mass ratio, and the redshift gave me the absolute mass scale. Together they pinned down both masses to within five percent.Photometric follow-up should happen in at least four broadband filters. U, B, V, and a near-infrared filter like J or H matter here because these cool white dwarfs emit a significant fraction of their flux beyond 1 micron. The SDSS u band is also useful for constraining the Balmer and helium line wings. A single V-band magnitude tells you almost nothing about temperature for a Snow White dwarf. I usually get temperature uncertainties down to about 150 Kelvin when I have UBJHK photometry combined with the spectral fit, compared to 400 to 600 Kelvin with spectroscopy alone.
Common Pitfalls That Will Waste Your Time
The biggest trap is assuming these objects follow the same cooling sequence as DA white dwarfs. They do not. Helium atmosphere white dwarfs cool slower at these low temperatures because the thinner hydrogen layer (or complete absence of one) changes the thermal insulation properties of the envelope. If you apply a DA cooling age to a DB or DOG-type object, you will overestimate the age by a factor of two or more. The cooling models from Socrates and Fontaine's groups are the current standard, but even those have uncertainties at the low-temperature end where crystallization and phase separation effects become important. Another issue is binarity contamination. When you get a spectrum of the system, the secondary component may contribute light in the near-infrared if it is a low-mass main sequence star or a brown dwarf. That extra flux biases your temperature low. Check your color indices against single white dwarf tracks. If your object sits systematically redward of the cooling sequence, you probably have a blended source. This is especially common in Gaia-driven surveys where the resolution is not fine enough to separate the components spatially. The third pitfall is more subtle and harder to detect. Microturbulent velocity in helium atmosphere models is often set to zero or a fixed small value in publicly available grids, but recent work suggests that can reach 1 to 2 km/s in these cool objects, and that changes the line profile shapes enough to bias your temperature determination by 100 to 200 Kelvin. I do not have a clean workaround for this yet. The best I can recommend is to test a range of microturbulent velocities and report the resulting temperature spread as a systematic uncertainty. It is not elegant, but it is honest, and it is better than hiding the problem behind an arbitrary fixed value.What This Research Actually Tells Us
These systems are valuable because they probe the stages of binary evolution in a way that hot white dwarfs cannot. The accretion disk that formed during the common envelope phase leaves a chemical signature in the white dwarf atmosphere, and detecting that signature requires exactly the kind of high-resolution spectroscopy I described. The quartet of spectral features I mentioned earlier can reveal whether the secondary is accreting material from the primary, whether there is a debris disk in the system, and whether the binary will merge within a Hubble time. Each of those answers has implications for Type Ia supernova progenitor models, and right now those models are uncertain enough that every data point matters. I should also say plainly where this approach breaks down. If your white dwarf pair is farther than about 300 parsecs, the spectral quality required for gravitational redshift measurements becomes impractical with current facilities. The objects are too faint, and the signal-to-noise drops below the threshold where line centroid measurements are reliable. In that regime, you should switch to indirect methods: use the orbital period and Kepler's third law with astrometric data from Gaia, or rely on asteroseismology if the white dwarfs are variable. Those methods have their own limitations, but they are the only option at distance.The takeaways are simple enough. Get good flux calibration. Fix gravity before fitting temperature. Account for helium cooling delays. Check for companion contamination. Report systematic uncertainties instead of pretending they do not exist. Follow those steps and you will get results that other people can build on, which is actually the point of doing this work in the first place.
Get the Full Details
