speculations

Image Source.

Hey Everybody, if you’ve been working on your fits to the second Systemic challenge system, send them to the e-mail address listed on the web-page given in the Sky and Telescope article.

I’ve been hearing many rumors floating around that there’s going to be a big planet announcement next week. Unfortunately, oklo.org has not yet joined the privileged ranks of the mainstream science press, so I haven’t been privy to any advance looks at the result that’s gonna come off the wire. I did hear, though, that it’s going to be an STScI announcement, so I did a little anticipatory detective work.

STScI runs HST, which means that the result will be the product of Hubble observations. In order to make Hubble observations, one needs to manage to get a block of fiercely competitive Hubble time, which means you need to write a successful Hubble proposal. The abstracts of winning Hubble proposals are posted publicly on NASA ADS. A quick search yields the following accepted proposal abstract (Proposal ID #10466), submitted by Dr. K. C. Sahu:

We propose to observe a Galactic bulge field continuously with ACS/WFC over a 7-day period. We will monitor ~167, 000 F, G, and K dwarfs down to V=23, in order to detect transits by orbiting Jovian planets. If the frequency of “hot Jupiters” is similar to that in the solar neighborhood, we will detect over 100 planets, more than doubling the number of extrasolar planets known. For the brighter stars with transits, we will confirm the planetary nature of the companions through radial- velocity measurements using the 8-m VLT. We will determine the metallicities of most of the planet-bearing stars as well as a control sample, through follow-up VLT spectroscopy. The metallicities of the target stars range over more than 1.5 dex, allowing for a determination of the dependence of planet frequency upon metallicity–a crucial element in understanding planet formation. We will be able to discriminate between the equally numerous disk and bulge stars via proper motions. Hence we will determine, for the first time, the frequencies of planets in two entirely different stellar populations. We will also determine for the first time the distribution of planetary radii for extrasolar planets for both these populations. Parallel observations with NICMOS will provide ultra-deep near-infrared images of a nearby bulge field, which will be used to determine the stellar luminosity and mass functions down to the brown-dwarf regime. The data will also be useful for a variety of spinoff projects, including a census of variable stars and of hot white dwarfs in the bulge, and the metallicity distribution of bulge dwarfs.

I looked at Sahu’s web page at STScI, where he writes:

At present, my research is mainly focused on a large HST program which involves monitoring of about 300,000 stars towards the Galactic bulge using the Advanced Camera System (ACS) on board HST, to search for extra-solar planets. The results are due to appear in the October 5, 2006 issue of Nature.

So clearly, the ACS data have been reduced, and it’s an excellent bet that they’re planning to announce the transit candidates that have emerged from their 7 days worth of ACS photometry. The number of transits to be announced is almost certainly more than two. This week’s announcement of WASP-1b and WASP-2b certainly didn’t produce a noticeable media splash, so there must be a lot of planets in the announcement. And given the past history of HST microlensing planet detections, I bet it’ll be the case that some of the parent stars of the soon-to-be-announced new transiting planets have indeed undergone a fairly rigorous spectroscopic follow-up with the VLT.

I think that spending a whole week of ACS time to stare at stars in the galactic bulge is a fairly worthwhile use of the HST (although I bet a lot of extragalactic astronomers might disagree). Here’s my take: In the mid-1990’s, it was believed that the stars of the galactic bulge are very metal-rich. In 1994, for example, McWillian and Rich 1994 reported an average bulge star metallicity of 0.2 “dex”, that is, ~60% greater than the solar value. More recently, however, Fulbright et al. 2006 have revised the average metallicity of the bulge downward to a value of -0.1 dex (~80% of the solar value). It thus appears that the metallicity distribution of the stars in the bulge is roughly similar to the metallicity distribution of stars in the solar neighborhood.

We know from Debra Fischer and Jeff Valenti’s work that the rate of short-period giant planet occurence is a strong function of stellar metallicity:

the planet metallicity correlation

All other things being equal, we can use the above diagram to inform an estimate of the number of planets that Sahu and company will announce. The hot Jupiter occurence rate in a solar-neighborhood type metallicity population is of order 0.7%. About 10% of hot Jupiters will be observable in transit. About half of those transits will be clobbered by the effect of a binary companion sharing the pixel and driving the detection below threshold. For a 7-day survey, about 60% of the hot Jupiters will actually get picked up, given constant coverage and good control of detector systematics (which HST certainly has). This means that Sahu should see (167,000)x(0.007)x(0.1)x(0.5)x(0.6)=35 transiting planets.

The problem, however, will be that there are many events which will look like planet transits, including grazing eclipsing binary stars, transiting M-dwarf stars, and the surprisingly common situation where a background eclipsing binary star shares the pixel with a foreground target star, a so-called blend situation. Dave Charbonneau and his collaborators have written extensively about all of the different pitfalls that can cause a wide-field transit survey to turn up false positives.

So my guess is that there will be of order 200 transit candidates in the ACS data for 167,000 stars. The brightest and most promising of these will have been sent to the VLT for spectroscopic follow-up. If the sensitivity limit of the survey (as stated in the proposal abstract) is V~23, then the candidate stars will likely have V~20-21. Even with the VLT, it’s tough to get accurate radial velocity measurements for stars this dim. So a lack of an observed binary stellar companion will probably be taken as a confirmation of the presence of a planet. (This is all complete speculation on my part.) Going even further out on a limb, my guess is that they have ~100 stars that show transit signatures, and which do not have a spectroscopically detectable binary stellar companion. Although it’ll be hard to further sort the wheat from the chaff, I’ll harbor a guess that 1/3 of the planets that will likely be announced are bona-fide.

Assuming that this is what actually occurs at the press conference, then we’ll have a very interesting result — not so much about the planets (which will be hard to characterize owing to the dim parent stars) — but because of what it tells us about the formation of the galactic bulge. Right now, there are several competing theories for how the bulge formed. One possibility is that scattering of stars by the Milky Way’s galactic bar has populated the Milky Way’s bulge with stars. Another possibility is that the bulge stars are the result of many disrupted globlular cluster or dwarf-galaxy like objects.

A measurement of the planet population of the bulge stars can allow us to distinguish between these two possiblities. If the planet occurance rate is similar to the galactic neighborhood (which I’m guessing will be the gist of the press conference) then the bulge stars are likely to have formed under low-density conditions. This would favor a bar-scattering type of scenario. If the planet occurence rate is zero or very low (which is unlikely, given that they are having a press conference) that would imply that the stars formed in a high-density environment. A crowded star formation leads to a ultraviolet ionizing radiation field that makes it difficult for planets to form and then migrate inward to become hot Jupiters.

There was a remarkable study done with HST in the late 1990s, and published by Gilliland et al. 2000. HST obtained a 8.3-day photometric time series for 34,000 stars in the globular cluster 47 Tucanae. The data, when reduced, show a total absence of transiting planets. This result shows the power of both the environment variable (the 47 Tucanae stars formed in an intensely irradiated region of star formation) and the metallicity variable (the metallicity of the 47 Tucanae stars is about 20% the solar value).

Finally, it’s always good to look at costs. According to the Wikipedia, the total cost of building, launching, servicing, and running HST has been of order 6 billion dollars. It started working as planned in 1994, and will thus have ~15 years of fully functional use. The seven days of ACS time were therefore worth 7.6 million dollars. This is comfortably more than the cost of building a special-purpose telescope to probe the terrestrial planets that are almost certainly orbiting Alpha Centauri B. (For more information, see these oklo.org posts: 1, 2, 3, 4, 5.)

HJD

These thumbnails show 42 of 56 photos taken during the interval from 6:56:27 PM to 7:00:26 PM CDT on September 16th, 2006, at spacing of roughly 3.2 seconds per frame. We were northbound on Interstate 57, north of Tuscola, Illinois.

I’ve processed the frames into animations, which can be accessed in mov and mp4 formats: tuscola.mov (200 kB) and tuscola.mp4 (600 kB). There’s an interesting sense of high-speed motion imparted by the differential blur and the decreasing altitude of the Sun above the horizon. I used a zoom factor of 10x, and was aided by the extremely level landscape. It was very flat because we were just north of the maximum southern extent of the Wisconsinan glaciation, which retreated just 13,000 years ago.

The animation demonstrates that just south of 40 degrees north latitude, the duration of Sunset near the equinox is just under three minutes. As I watched the Sun go down, I was thinking about the fact that the Earth’s motion through its orbit is creating transits observable (in September) to observers located on planets orbiting specific stars lying in Pisces.

Here on Earth, observations of transiting extrasolar planets are mediated by a complex beat pattern between the diurnal and seasonal cycles of the Earth, and the alien periodicity of the transiting planet. Assuming clear weather, in order to catch a complete predicted transit it needs to be dark, and at least a transit duration before dawn. In addition, the target star needs to maintain a sufficient altitude above the horizon during the course of the transit.

These constraints have restricted the aggregate of known transits to objects with periods of 4 days or less. From a single location on Earth, it’s very hard to find and confirm transiting planets with longer periods. With a global network, however, the problem is more manageable, essentially because it’s always 5pm somewhere. Several years ago, we published a detailed analysis which shows quantitatively how a network of small telescopes gains in advantage over a single large telescope at a fixed location as the planetary period increases.

and then there were fourteen…

In June 2002, I saw Keith Horne give a review talk at the Scientific Frontiers in Research on Extrasolar Planets Meeting at the Carnegie Institute of Washington. He showed a slide (an updated version of which is here) that listed 23 planetary transit surveys that were in operation at that time. He had asked the investigators running each survey to send him the number of new transiting planets per month that could be expected to turn up. The grand total rang up to a whopping 191 fresh planets per month, or 2,292 planets per year.

For a number of reasons, those numbers haven’t quite panned out, but it nevertheless finally looks like we’re entering a phase where the planetary yield from wide-field transit surveys is starting to ramp up dramatically. Today’s astro-ph mailing has a paper by Collier Cameron et al. entitled “WASP-1b and WASP-2b: Two new transiting exoplanets detected with SuperWASP and SOPHIE”, describing the discovery of P=2.15 d and P=2.52 d planets transiting ~12th magnitude stars. As of this month, astronomers have been hauling in transits at a rate of one per week.

Dave Charbonneau at CfA dropped me an e-mail this morning:

Great chance to catch WASP-1 tonight from the western US. We will pursue it from Mt. Hopkins and Palomar, but thought you might want to give a heads up to transitsearch.org. This one is very much in need of a great light curve, as the current estimates of the planetary radius range from “smallish” to “huge”, with an error bar that is depressingly large.

He’s definitely right about all that. Multiple photometric data sets will be of considerable use in constraining the system parameters. It’s also going to be very important to get a better handle on the properties (Mass, Radius, and metallicity) of the WASP-1b and 2b parent stars. We’d really like to know how these two new planets fit into the overall trends that are starting to emerge among the aggregate of transiting planets.

Ephemerides for both of the WASPs have been added to the transitsearch.org candidates table, and the (rather meagre) published tables of radial velocity measurements have been added to the Systemic back-end. Given the short orbital periods, I don’t think it’ll be very long at all before small telescope observers start producing confirmation light curves.

lightcurves

Image Source.

As we work to get the systemic collaboration off the ground, I’ve been letting transitsearch.org coast along on basically its own devices. That will change fairly soon as we incorporate the transitsearch.org site into the oklo.org backend. This will allow for (among other things) creation of transit ephemeris based on submitted fits, and a tighter collaboration among observers.

In the interim, there’s an important opportunity coming up on October 20th, 2006 for transitsearch.org observers to see whether the highly eccentric planet HD 20782 b can be observed in transit. The a-priori probability is 3.6% that we’ll make a huge (and I mean big deal) discovery. Here’s a link to the oklo post from last April describing the system. I’ll be sending out a campaign notice to the transitsearch.org e-mail list shortly, and I’m hoping that AAVSO will want to collaborate on this campaign as well.

A large number of amateur and small-telescope observers have been catching transits recently. Here’s an overview of some of the results that have showed up in my in-box over the past two months:

Last year, transitsearch.org got an important opportunity to follow up on a high-probability transit candidate. The target was the P=3.34 d planet in the close triple star system HD 188753 that was announced by Konacki, 2005 and which received quite a bit of notice in the press.

Konacki’s planet, which has a minimum mass of 1.14 Jupiter masses, and a predicted radius of ~1.1 Jupiter radii, orbits a 1.06 solar-mass star (HD 188753A) at a distance of ~0.05 AU. The star A is in turn separated by 12 AU (e=0.50) from a binary pair (HD 188753B “a” and HD 188753B “b”). The binary pair B consists of stellar components with 0.7 and 0.9 solar masses in a 155-day e=0.1 orbit (separation of 0.67 AU). The presence of a hot Jupiter orbiting HD 188753A was very surprising, because the presence of the binary B leads to severe difficulties for conventional planet formation theories.

Observations in 2005 by Ron Bissinger and other transitsearch.org observers indicated that it is very unlikely that HD 188753A “b” is transiting (the a-priori probability was 11.8%). Further confirmation of a lack of transits came this July from Joe Garlitz of Elgin Oregon, who writes:

Attached is a chart made from data on HD 188753 taken from 04:45 to 09:30 July 21 [UT]. There is no suggestion of a transit during this time within the capacity of this data. It is difficult to get a good data set since there are no stars within the field at a magnitude similar to HD 188753.

Garlitz’s full figure is here, and his website is here.

One disadvantage of having 200-odd planets rattling around in the planet catalog, is that it’s getting hard to keep all the HD numbers straight. HD 188753 doesn’t show transits, but HD189733 most dramatically does. On July 30th, Donn Starkey, of Auburn, Indiana sent a nice light curve of HD 189733 during the JD 2453946.7 transit:

More detail regarding Starkey’s results can be found on his website.

On August 27th, I received a dispatch from Veli-Pekka Hentunen of Varkaus Finland. Summer has finally wrapped up in Finland, and Taurus Hill observatory (featured in this post from last May) is again open for business:

Last weekend, we began to continue exoplanet transit observing after the long Finnish light summer. On the night of August 26-27 w observed our first XO-1b transit at the Taurus Hill Observatory, Varkaus (obs. code A95). We were able to catch only about half of the entire transit because the object was quite low in the north-western sky, and the altitude decreased from 30 to 15 degrees during the course of observation. Our light curves and observing information are given on our English website.

In a follow-up e-mail on September 17th, Hentunen reported that they had observed a full transit for HD 189733 on the night of September 16th-17th:

Starting on September 9th, Tonny Vanmunster, Kent Richardson, and Ron Bissinger all reported observations of the newly discovered TrES-2 transit. Tonny and Kent’s observatons are detailed in this oklo post, whereas Ron’s TrES-2 light curve looks like this:

Don Carona at Texas A&M also sent a light curve of a TrES-2 transit, obtained (under less-than-ideal weather conditions) from the Physics Dept. at College Station. Here’s an unbinned excerpt from his reduced high-cadence time series:

Notice the the lack of a flat bottom for the TrES-2 transit (which is more obvious to the eye when the data is binned). TrES-2 crosses the star with a high “impact parameter”, which means that the planet does not occult the central portion of the star as seen from Earth. Stellar Limb Darkening is responsible for the remarkable smoothness of the dip.

On September 19th, Bob Buchheim of Altimira Observatory sent a very nice HD 189733 lightcurve:

Along with the photometry, he sent a report of an entirely new strain of transit fever:

Last night I monitored HD189733 for a photometric transit signature. A bit of an embarassing story: I noticed that it was nicely placed and “in window”, so I set up the telescope and went to bed … but I forgot to check if transits had already been detected for this star. Imagine my surprise at the resulting deep transit signature! (See attached graph). Oh, well, now that I’ve checked, I see that I’m a year late with this “discovery”.

Bob’s experience reminds me that I’ve got to update the various results pages for the transiting candidates. The transitsearch results page for HD 189733 b reports (erroneously, and by default) that “No photometric transitsearch has yet been reported for this system”. Yikes!

Finally, just a few minutes ago, I got an e-mail from Arto Oksanen, who was the first amateur to observe an HD 209458b transit (on Sept. 16th, 2000). Six years later, it looks like he’s also the first amateur to observe HAT-P-1b

I observed the end of transit of HAT-1b last night at Hankasalmi Observatory, Finland. The weather was not very good, but the egress was well visible. The observing instrument was a 40 cm RC telescope. I used V-filter with SBIG STL-1001E CCD.

Oksanen’s light curve is plotted is at this link, and is reproduced just below:

Oksanen notes that the egress seems to occur 30 minutes early relative to the published ephemeris. This could well be the case. The longer the time baseline for transit observations, the more accurate the ephemeris become. Small-telescope observations have an important role to play in this regard.

The golden ratio

It was gratifying to watch the first systemic challenge unfold.

After a week of accepting fits, we tallied the entries and determined that Chris Thiessen had obtained to the lowest submitted chi-square. Way to go Chris! Eugenio then added the “challenge001” data set to the systemic backend, so that users can continue to improve and submit fits.

So what was the underlying synthetic planetary configuration that generated the data set?

Both Eugenio and I have had a long-running interest in the GJ 876, a 15-light year distant red dwarf star that is now known to harbor at least three planets. The two outer worlds in the system, which were discovered in 1998 and 2001, are in 2:1 resonance, and form the classic example of a configuration that demands a self-consistent (as opposed to Keplerian) model. Last year, Eugenio led the discovery and characterization of a third planet in the system, which has a mass only 7.5 times that of Earth, and orbits the star every 1.94 days. (Here’s a link to the NSF press release for Rivera et al. 2005.)

We’ve been looking into the possibility of detecting another planet in the system, and in order to do so, we’ve been studying synthetic data sets that contain the three known planets, as well as a fourth, potentially habitable planet in a potentially habitable orbit. The following table gives the parameters of our hoped-for system (which, like the real system, has its invariable plane inclined by 40 degrees with respect to the line of sight.)

(JD 2452490)
Parameter Planet 1 Planet 2 Planet 3 Planet 4
Period (days) 1.937747 7.106642 30.45123 60.83227
Mass (M_Jup) 0.025101 0.016193 0.791650 2.531229
Mean Anomaly (deg) 308.84845 169.44032 312.3738 159.1070
eccentricity 0.000000 0.000000 0.262795 0.033979
omega (deg) 0.000000 0.000000 195.8324 191.9573

The first 155 points in the challenge data set used the actual observing times given in Rivera et al 2005. The remaining 32 points were generated using the version of Eugenio’s Keck_TAC program that we use to produce the systemic synthetic data sets. We then subtracted off the the first epoch time from all 187 observing times and multiplied each of the resulting times by the golden section, 1.618033989. This gives a system that has the dynamical characteritics of the real GJ 876 system, but with orbital periods that are all 1.618 times longer.

After setting up the uploads page on the backend, Eugenio uploaded the best fit that he was able to obtain, which had a chi-square of 3.13. A lot of computation went in to getting this fit, which took several days on a fast desktop machine.

Amazingly, the next day, user Roseundy submitted an even better fit,

which brought the chi-square down to 2.82, with the following comment:

Arrrggghh!!!!!!!! I had this fit on Sep 13, but I thought the ChiSq was too high to bother to submit. Lesson learned.

Eugenio and I were quite excited. Systemic users have clearly gotten at least as good at fitting with the console as we are, and we have been thinking carefully about the problem for quite a while. In the comments section on Roseundy’s fit, Eugenio wrote:

Hi Roseundy, That is awesome work!! All the challenge systems will be based on some known model, possibly a random draw, some noise, and possibly other effects. The random draw and the noise complicate the situation for the modeler (me), so that knowledge of the model will not always result in the best fit. Actually, your result is a major success for the idea behind the systemic collaboration — distributing the process of fitting radial velocity data sets. Because I really don’t know precisely how the random draw and the noise affected the model, it may still be possible to get even lower chisq values. I encourage everyone to continue fitting this system (as well as others). It does require patience and perserverence.

Chris Thiessen wrote:

Roseundy, I’m very impressed. The two major planets have such different Keplerian and integrated fits that I was never able to get them to work well together. How did you get the two planet solution? I’m not sure I would have let the 48 day planet develop that much eccentricity if I’d seen a trend. Maybe I missed out that way. Great work!

Whereupon Roseundy revealed the secrets of his fitting method:

Once I saw how close the planets were, I realized I needed to work with integration turn on. This, of course, slowed things down painfully. To make progress, I cut down the dataset (the middle third of the velocity data) and played with that until I got a good (chi^2 of 7 or so) fit. I backed that out to the full data set (very painful) and then added additional planets based on the residuals. I polished until I got the fit you see. I’m sure it can be improved, but I lost patience with it. I would like to see three improvements to the console to make this easier in the future: 1. be able to subset the data 2. be able to select which planets are to be integrated together, using Keplerian calculations for the rest. this would help with systems where only a few planets substantially interact with each other 3. (my vote for the most important) a natively compiled console. java byte code may be portable, but I don’t it’s very optimized. Having optimized binaries (x86 on Linux preferably) would be a win, I think.

We agree. After the next release of the console, I think it would be a good idea to migrate to a strategy where the systemic community of users can work on the console code open-source style. This is clearly another area where a distributed attack will get important and interesting results.

In any event, thanks to everyone who has been reading the oklo blog and collaborating in the backend. We’ve had over 6,000 unique visitors so far this month, and the project is really starting to show promise.

The Second Challenge System

Image Source.

The second systemic challenge radial velocity dataset is now included on the downloadable systemic console. This system is dynamically quite interesting, and also possibly quite scientifically relevant. It’s non-trivial to fit, and integration is required in order to produce a viable model. The computational demands, while modestly high, are nowhere near what was required to crack the first challenge system.

Send your entries to me at the e-mail address given on the web page listed in the Sky and Telescope article. (Same procedure as previously).

Note that the downloadable console currently does not include the massive synthetic data sets for Alpha Centauri. These data were causing download times to become excruciatingly slow. Later this week, I’ll write a post which explains how the Alpha Centauri data sets can be accessed, and which also explains how the console can be updated without downloading an entire new package. (For the time being, though, you are best off just downloading a fresh copy.)

The first challenge system is now included in the systemic backend, with Eugenio’s solution posted. (Chris Thiessen was the winner of the contest). Feel free to submit additional fits, and in the next post or two, I’ll give a discussion of what’s going on dynamically in that system.

flight

Image Source.

I always think that I’ll get a bunch of work done on transcontinental flights. Finish up those overdue articles, prepare classes in advance, read papers from the literature.

Then I end up staring out the window for most of the flight.

Over Utah, I was struck by how much the landscape resembled the views radioed to Earth by the Huygens probe as it drifted down to its final resting spot. There are networks of channels cut by intermittent streams, ridgelines, clouds, and dry lake beds.

Image Source.

As a result, everything that I’ve been promising — the next contest dataset, a description of last week’s winning system, an overview of the updates to the downloadable console, the launch of Systemic’s second phase — it all gets pushed back by one more day.

And the Winner is…

I’ve evaluated the fits submitted for the first Systemic Challenge radial velocity data set, and the winner is Chris Thiessen.

In addition to being dynamically interesting, the configuration proved to be very tough to crack. The challenge 001 system is one where a Keplerian model can reach a low chi-square, which then skyrockets when the planets are actually integrated through their orbits.

I’m travelling today, without full access to the Internet. In the next day or so, once I get back to the office, I’ll put up a more detailed post which looks at what’s really going on in the first challenge system. We’ll also release the second challenge data set (which is equally interesting, but a lot more tractable).

A HAT trick

inter tidal

Image Source.

Chalk another transiting exo-planet up on the board. In a preprint released today, Gaspar Bakos and his colleagues in the HATnet project are announcing HAT-P-1b, a large-radius, low-density planet transiting one member of a relatively nearby, relatively bright solar-type binary star.

HAT-P-1b (which orbits the star BD+37 4734) is quite interesting for several reasons. Its 4.46529 day orbit is the longest period yet detected for a transiting extrasolar planet, and its measured radius of 1.36 Jupiter radii is alarmingly larger than the baseline theoretical prediction. The planet contains 0.53 Jupiter Masses, and has a surface temperature near 1100 K, so our models predict that it should have a radius of 0.94 Jupiter radii if it contains a 20 Earth-mass heavy-element core, and a radius of 1.09 Jupiter radii if it’s made of pure solar-composition gas. It’s thus roughly 20-30% larger than it “should” be, which means that something is providing it with a very significant source of extra interior heat.

The large radius of the planet means that the transits exhibit a ~1.5% photometric depth. Deep transits make it easier to obtain data with high signal-to-noise, which means that we can look forward to very accurate follow-up measurements for this system. The presence of a nearly identical companion star at a separation of 11 arc seconds should also help observers obtain good differential photometry. The star is up now, and its well-placed for Northern Hemisphere observers. I don’t think it’ll be long before we see confirmations rolling in from small-telescope observers worldwide. If you’re interested in observing it, the ephemeris table is here.

Where could the extra source of heat be coming from? One possibility is tidal dissipation related to the circularization of an eccentric orbit.

The theory of tides can rapidly slip into thousands of pages of detailed mathematical analysis. Many of the interesting ideas, however, are close to the surface. In the introduction to his still-useful 1898 popular book, “The Tides”, Sir George H. Darwin, the son of the naturalist, and Plumian Professor at Cambridge, wrote:

A mathematical argument is, after all, only organized common sense, and it is well that men of science should from time to time explain to a larger public the reasoning behind their mathematical notation. To a man unversed in popular exposition it needs a great effort to shell away the apparatus of investigation and the technical mode of speech from the thing behind it.

I would actually argue that the situation is quite the opposite. I think it’s easier and better to get a colloquial, heuristic understanding first, and then make an attempt to put the ideas on a sound mathematical basis.

For a planet that (like Hat-P-1b) has an orbital period of less than a month or so, it’s expected that tidal forces will rapidly bring the planet into synchronous rotation, in which the planet spins once on its axis every orbital period. For a circular orbit, this means that the planet always keeps one face to the star, just as the Moon keeps one side toward the Earth. If the orbit is eccentric, however, the planet will not manage to keep one side directly facing the star. Because the planet spends more time at the far point of its orbit, it does more “turning” there, and remarkably, it turns out that the planet always keeps one face pointed toward the empty focus of its elliptical orbit. From the point of view of the star, a fixed point on the planet is seen to librate. The Moon’s orbit is slightly eccentric, and so we can see this effect in time-lapse animations of lunation. See here and also (if you’re not inclined to motion sickness, here).

The tidal bulge of the planet, on the other hand, is forced to always point toward the star, as it’s the star’s gravity that is producing the differential gravitational attraction. This means that once per orbit, the tidal bulge is rocked back and forth across the planet, which produces serious internal heating. The size of the bulge also increases and decreases once per orbit due to the varying distance between the planet and the star, and the resulting oscillation also contributes to the amount of internal tidal heating.

how tidal heating works

The amount of tidal energy deposited in the planet increases with the square of the orbital eccentricity. A reasonable model for the physical properties of HAT-P-1b indicates that an eccentricity e=0.09 is adequate to generate enough tidal heating to expand the planet to its observed size of 1.36 Jupiter radii. The problem, is that the orbit should circularize on a timescale of less than 1 billion years, whereas the system seems to be about 4 billion years old. Therefore, if a significant orbital eccentricity exists, then there must be a mechanism to maintain the eccentricity. The best candidate is another planet further out in the system.

We can take a quick look to see whether such a situation holds water. A second planet in the system will exert gravitational perturbations of HAT-P-1b, which will cause its eccentricity to vary with time. The picture to have in one’s head is to imagine that the planets are viewed on a timescale that is much longer than an orbital period. If one takes the long view, the motion of the planet is effectively blurred out along the orbit, and one can model the planet as an elliptical wire of varying mass density — heavy near apastron where more time is spent, and light near periastron where the planet spends less time. The interaction between the two planets can then be modeled as the interaction between two flexible elliptical wires. When one does this, and ignores the moment-by-moment motion of the planet, one is making a “secular approximation”. Secular theory was developed to a high art in the 1770s by Laplace and Lagrange, and we can make use of their work to quickly look at how the eccentricities of two mutually interacting planets vary with time.

Over at the transitsearch.org, I have a program which computes a 2nd-order secular theory for each of the known multiple-planet systems, and plots the resulting eccentricity variations as part of the candidate information table . (To see the plots of the secular variations, click on the “planet column” for a multiple planet system such as Upsilon Andromedae).

An advantage of using the secular approximation to the dynamics is that one can quickly scan through a range of planet-planet configurations and find out what the perturbative interactions look like. If I add a second planet to the HAT-P-1 system with a period of 50 days, a mass of 0.06 Jupiter masses, and an orbital eccentricity of e=0.30, I get the following long-term variation in eccentricities, in which the eccentricity of planet b has a time-averaged value close to e=0.09:

possible secular variation

Is it possible to hide a second planet in the system while remaining consistent with the (still sparse) set of published radial velocity measurements? The downloadable console is ideally suited to quickly answering such a question. It turns out that it’s very easy to get a perfectly adequate 2-planet fit to the data in which a hypothesized perturbing outer planet is capable of maintaining a time-averaged eccentricity e=0.09 for the inner planet. One such fit looks like this:

possible secular variation

corresponding to a system configuration that looks like this:

possible secular variation

It would be exciting if a planet like the one in the above diagram (or its dynamical equivalent) could be detected. This would tell us that we’re on the right track in obtaining a better understanding of the wide range of observed radii among the known transiting planets. Probably the fastest way to detect the perturbing planet is through accurate timing of the intervals between successive transits. If an outer planet is tugging on the inner planet, then the orbit will fail to be perfectly periodic, and variations will be observed in the amount of time that passes between transits. Matt Holman and Norm Murray have written a paper that describes how this works. They give a rule-of-thumb equation for the transit-to-transit variations that one can expect. For a planet similar to HAT-P-1b, with semimaor axis a1 and period P1, and a pertubing planet with simimajor axis a2 (where a2>a1), period P2 and mass M2, they find that the typical variation of the interval between successive transits is given by

where

For HAT-P-1b and HAT-P-1c (as hypothesized above) delta T works out to about 5 seconds. Variations of this magnitude are readily detected from the ground, and a number of research groups will probably jump right on this problem.

last call

If you’ve been working on the first systemic challenge system, please submit your fit as an ascii file to the e-mail address listed on the web-page given in the Sky and Telescope article. At 00:00 UT Sept. 14th (JD 2453992.5) I’ll close the submissions and see who wins the Star Atlas.

Don’t hesitate to submit if your chi-square is still far from 1.00. Our first challenge system turned out to be a bit harder than we anticipated. Next week’s system will be equally interesting from a dynamical point of view, but will be a lot easier on the ol’ CPU.

HD 208487

Image Source.

An relevant paper showed up on the astro-ph preprint server this morning, “A Bayesian Kepler Periodogram Detects a Second Planet in HD 208487” by P. Ç. Gregory of the University of British Columbia.

Gregory employs a technique known as the parallel tempering Markov Chain Monte Carlo algorithm to argue that the HD 208487 data set contains two planets. The first planet (which was previously announced by Tinney et al. 2005, and confirmed by Butler et al. 2006) has a period of 130 days and a minimum mass 37% that of Jupiter. The second planet in Gregory’s model lies out at a period of 908 days, and has 46% of Jupiter’s mass.

Interestingly, the console does not recover Gregory’s parameters precisely, but it does find a fit that’s extremely similar. (I just uploaded the fit to the systemic back-end.) The radial velocity reflex curve looks like this:


wheras the planetary configuration (at the moment when the first radial velocity data point was obtained on Aug. 8th, 1998) looks like this:

It’s interesting to look at the fits for the latest HD 208487 dataset that have been submitted by participants in the systemic collaboration. At the moment, there are six different fits:

On September 4th, mikevald submitted a 2-planet fit that is a close analog of the one published by Gregory. In the last several days, dstew and andy have also turned in fits that have essentially the same configuration as obtained by Gregory. That’s definitely cool.

In addition to the five fits that look like the Gregory configuration, with the outer planet at a period of P~1000 days, there’s also a completely different take on the system that was submitted this morning by Olweg. In the Olweg fit, the second planet lies interior to the known planet, and has a period of only 29 days. The chi-square is less than one, indicating a slight degree of overfitting. When overfitting occurs, it can easily be remedied by a slight random perturbation of the parameters. It’s very interesting that this fit was completely missed by the Bayesian Kepler Periodogram, so I thought I would have a closer look at Olweg’s model system.

The Olweg radial velocity curve is radically different from the Gregory fit:

The 28.68 day inner planet has a mass of 0.16 Jupiter masses (about 50 Earth masses) and travels on an orbit of modest (e=0.18) eccentricity. There’s a fair amount of planet-planet interaction in this system over the time scale of the radial velocity observations. By the time the fit reaches the end of the data set, there’s a noticeable difference between the keplerian model fit and a self consistent (integrated) model fit:

The system is stable, however, when I did a short test integration of 100,000 years. The secular interaction between the two planets causes the two orbits to execute a complicated dance over a timescale of several thousand years, with the periastron angle of the inner planet orbit mostly librating around an anti-aligned configuration.

As I’ve remarked in an earlier post, we’re currently in the progress of upgrading the downloadable console so that it will be capable of computing estimates of the uncertainties in the orbital elements of a fit. A good way to generate uncertainties in this context is to use the so-called bootstrap method. In the bootstrap, one re-draws the original radial velocity data set with replacement, thus producing alternate realizations of the data in which a fraction of the points appear more than once, and in which a fraction do not appear at all. One then fits to these new datasets, thereby building up distributions for each orbital element. (For more detail, see this paper, which describes in detail how this procedure was applied to the radial velocity data set for HD 209458.) When I run a self-consistent bootstrap analysis based on the Olweg fit, I get the following mean values and standard deviations for the parameters:

This fit is thus quite well constrained, and is a completely viable competing model for describing the hd208487 planetary system. I think the situation here really underscores the value of the systemic collaboration. Many radial velocity data-sets can be fitted by completely different models that offer equally robust fits to the data, while simultaneously maintaining small uncertainties on their bootstrap-estimated parameters.

So how do we know which HD 208487 system (if either) is correct? I’m hoping that the Monte Carlo simulation that will make up phase II of the systemic project will give a great deal of insight into when a particular orbital model can be deemed secure.

desiderata

strands of wheat

Image Source.

It’s good to see that users are still streaming into the systemic collaboration, and activity on the back-end is staying strong. The catalog of submitted radial velocity fits is now approaching 1,000 entries, and nearly every data-set has at least one fit. We need more users, though. Both Stefano and Eugenio have been working very hard behind the scenes to engineer improved usability for the site. There are a lot of items that are still on our plate, but progress is definitely being made.

We can now internally query the database of submitted fits to statistically characterize the planetary models that are being submitted. Once this functionality is fully tested, it’ll be made available to all users on the site. For example, here’s a plot of eccentricity vs. period for all of the fits submitted with 0.8 < chi-square < 2.0: aggregated P-e diagram

It’s interesting to compare this with the plot that one can produce at exoplanet.eu based on the static catalog of published planets:

One immediately notices that the diagram produced from the back-end data is populated in the upper left hand corner, whereas this region in the published catalog is completely cleared out. Note that planets in this region are known from theoretical arguments to be tidally circularized… (tune in soon for more on that issue).

One final note. The downloadable console is now much lighter. The large filesize of the previous version was due to the very extensive synthetic data sets for alpha Centauri. If you want the alpha Centauri velocities, the fully loaded console that contains the alpha Centauri data is here. Within a day or so, we’ll be updating the downloads page to reflect this change and to give more guidance for International Windows users.

TrES-2 follow-up

The transit game is getting to be a competitive global business. No sooner is a new transit announced than amateur astronomers worldwide are on the sky to obtain follow-up observations. Tonny Vanmunster, of Landen Belgium and Ron Bissinger of Pleasanton California are generally among the first to check in with confirmations. Vanmunster nailed TrES-1 a mere week after its announcement in 2004. Last summer, Bissinger caught HD 149026b on literally the day it was announced. In the case of TrES-2, which was announced yesterday, it looks like Vanmunster has snagged the prize. “What’s up, Cali?”

[Actually, it was both cloudy and the middle of the day in Pleasanton while Vanmunster was on the sky. But there’s a transit tomorrow night, Sept. 10/11 PDT, that Ron’ll likely catch.]

Here’s Vanmunster’s light curve. The transit was in progress at dusk in Belgium, so he was able to observe only the latter part of the event.

Vanmunster writes:

Here are some technical details : observations were made at CBA Belgium Observatory, using two 0.35-m f/6.3 Celestron telescopes, each equipped with an SBIG ST-7XME CCD camera. I simultaneously made unfiltered and R-band observations (hence the 2 telescopes). The included light curve is unfiltered, and each dot in the curve is the average value of 5 successive observations (binned). The gray lines show the standard deviation (about 4 millimag on average). Exposure time was 15 to 20 sec.

The egress is very evident in the light curve, and happened right at the predicted time. The transit depth was approx. 0.0155 mag, which again corresponds well with the value published in the discovery paper.

Follow-up observations such as the ones made by Vanmunster and Bissinger can be very scientifically useful. For example, Vanmunster’s 2004 observations allowed us to get an improved estimate of the TrES-1 planetary radius, and he co-authored a journal article with us on that topic. Both Vanmunster and Bissinger were involved in the discovery of X0-1, and both are co-authors on the recent Shankland et al. paper which I’ll talk up in an upcoming post.

TrES-2

TrES-2

Image Source.

When I teach Astronomy 101, I like to brag about my weight early and often during the class. For example, when I introduce the concept of energy, I’ll tell the students, “Let’s say you have a guy like me. You know, six foot three, 285 lbs (129 kg)… pause… If I’m running down the street at 9 meters per second, then my kinetic energy is 10,449 Joules.”

The first time that I floss my weight, there’s usually a slight rustle through the lecture hall, but generally nobody says anything. Students in the back row glance up slightly startled from their online poker games, then adjust their hoodies and ante up for the next hand.

As the quarter progresses, I’ll find other opportunities to claim an outrageous heft. “Take me, for example, I weigh 287 lbs… pause… solid muscle.”

Usually, that line finally gets a rise out of someone, “You don’t weigh 287!” they’ll blurt out, “You’re more like 150!”

“Are you challenging me?” I’ll roar, “Anyone want an F on the next exam?” Nervous laughter. Eventually, a few more classes in, everyone just rolls their eyes when I remind them of my outrageously high mass.

Eventually, when I get all the way out to the galactic scale, I reach the topic of dark matter and I can cash in on the long set-up. “Look at that rotation curve!” I’ll say, “The orbital velocities of the galaxies in this cluster suggest that there’s many times more mass present than we can observe in the form of stars. It’s like [pause] It’s as if some guy who looks like he weighs 160 steps on the scale and it turns out that he actually weighs 285.”

They laugh and the joke works because we’re able to look at a person and make a mental estimate of their mass. When it comes to extrasolar planets, however, judging mass by size has proved to be effectively impossible. If you are in the vicinity of a hot Jupiter, and are able to measure its radius, you’ll have little basis for judging how massive it is. That is, the mass-radius relation for hot Jupiters isn’t a single-valued function, and we don’t know why. Indeed, understanding the radii of the known transiting planets is one of the most currently interesting exoplanet research topics.

I’ve written several oklo posts about the size problem for the short-period extrasolar planets [see here, here, here, here and here]. In a nutshell, within the aggregate of transiting exoplanets that orbit stars bright enough for high-precision follow-up, there’s a full range of size discrepancies. HD 149026 b is much smaller than would be predicted for a standard-issue Jovian planet of its mass and temperature. TrES-1 has a radius that agrees very well with the theoretical predictions. HD 189733 is somewhat on the large side, and HD 209458 b, famously, is much larger than predicted. [In tomorrow’s post, I’ll give an update on the hydrodynamical simulations that we’ve been doing with the goal of eventually sorting out whether HD 209458 b is caught in Cassini state two.]

It’s therefore still a big deal whenever a new transit is discovered in association with a bright parent star. Today, the TrES collaboration, (who bagged TrES-1 back in ’04) are rolling out a new transiting planet — TrES-2.

TrES-2 is a more-or-less standard-issue hot Jupiter. At 1.28 Jupiter masses, it’s a little more massive than the average short-period planet, and its orbital period of 2.47 days is slightly shorter than the 3-day average period exhibited by this class of objects. The TrES-2 parent star is very similar in mass, radius, and temperature to the Sun. It lies in Lyra, and has a V-band magnitude of 11.4 (making it ideal for follow-up observations by amateurs — check out the transitsearch.org ephemeris table here).

Turns out that TrES-2 is on the large side. Our theoretical models predict a radius of 1.07 Jovian radii if the planet has a core, and 1.11 Jovian radii if it is core-free. The measured radius is 1.24 Jovian radii, with a lower error bar of 0.06 Jovian radii. The planet is thus a bit more than 2-sigma larger than the core-free model, and provides evidence that the mechanism responsible for providing extra heat (and expansion) to these planets is a relatively generic and commonplace phenomenon. It’s hard to invoke special purpose explanations for HD 209458 b’s radius when there’s a slew of other transiting planets that suffer a similar bloat.

One reason I like transiting planets is that they can be drawn to scale with their orbits and parent stars. In TrES-2’s case, the geometry looks like this:

TrES-2 system to scale

With Illustrator’s scale tool, it’s easy to insert TrES-2 into our planetary police line-up:

Five for the show

Curiously, the TrES-2 paper makes no mention of the metallicity of the TrES-2 parent star. The metallicity is of great interest because it will allow a test of the Guillot et al. hypothesis that the planetary radii are the result of a concentration mechanism that greatly amplifies the overall solids content of short-period exoplanets that orbit high-metallicity stars. I asked Dave Charbonneau if his team had anything up their sleeve in the metallicity department. He told me that they haven’t had time to get an accurate measurement, and that the number will be released in a follow-up paper.

Amazingly, TrES-2 lies in the field of view of the Kepler Mission. This means that the Kepler satellite will make repeated high-precision measurements of the TrES-2 light curve, with a photometric precision of about one part in 10,000 and a cadence of 15 minutes. This data will allow for very accurate determinations of the durations between transits. By observing small variations in the orbital period, you can detect other bodies in the system, in many cases with masses down into the terrestrial regime. The process by which this is done is highly analagous to the multiparameter fitting process that one uses when running the console, with transit intervals playing an analogous role to the usual radial velocity measurements. Once we get our plate cleared of current console improvements — integrator, bootstrapper, multi-threading, etc. etc., we’ll reconfigure it to enable a look at planet detection via transit timing.

New Texas V’s

Image Source.

Data data data. Robert Wittenmyer and his colleagues at the University of Texas have just posted a paper on astro-ph that contains a slew of new radial velocities for several famous planet-bearing stars, including 47 UMa, 14 Her, and 16 Cyg B. The velocities are all tabulated in the paper, so we’ll have them up on the systemic backend very shortly. [I’ll post a comment to this post when they’re up on the site. If you’re totally gung ho to get them right away, you can extract them from the posted latex file at astro-ph, and then add them manually to systemic’s datafiles directory.]

We always try to add new radial velocity data sets as soon as they become publicly available, and lately, these updates have been occurring roughly once per week. For the time being, the simplest way to get your fresh V’s is to rename your old systemic directory, and then download a new console. When the new console and catalog data are downloaded and unzipped, you can copy any previous fits and soundfiles that you’ve created into the new fits and soundClips directories.

The data in the Wittenmyer paper come from both the Harlan J. Smith 2.7-meter telescope and the Hobbey-Eberly 9.2-meter telescope. The cadence of the Smith telescope observations typifies the usual pattern of radial velocity survey data. The individual points are spaced essentially randomly in time, with many days separating each point. The Hobbey-Ebery data, on the other hand, are quite different. These data are much more densely sampled, and many nights contain several velocities in succession. In many stretches, the star is observed every few nights. This pattern results from queue-scheduling, which enables very intensive monitoring of systems that are of particular interest. I think queue scheduling is the wave of the future, and in the systemic simulation, we’ll have many synthetic data sets whose cadences correspond to the queue-scheduled approach.

The most prominent planet orbiting 14 Her has been known since the late 1990s. This world, known as 14 Her “b”, has a minimum mass about 4.6 times that of Jupiter, and a period of ~1770 days. If it were in our solar system, it would orbit in the asteroid belt. The parent star 14 Her is about 90% as massive as the Sun, and is more than twice as metal-rich. Given the planet-metallicity connection, it’s absolutely no surprise that 14 Her has a heavy-duty planetary system. I bet that 14 Her “b” has a very interesting system of satellites.

It’s pretty clear from the one planet fit that 14 Her “b” is not the only planet in the system, and over the weekend, several systemic users have submitted interesting fits to the data that reduce the chi-square by adding a second planet. For example, on August 30, user mikevald uploaded a two-planet fit in which the second planet, 14 Her “c”, has a period of 6159 days and an eccentricity e=0.52. This model currently fields the lowest chi-square statistic of any of the submitted 14 Her fits. The orbits in this best-fit system are crossing, however, indicating that the model may not be dynamically stable over the long run. On September 5th, allanfloering submitted a fit with nearly as good a chi-square, in which the outer planet has a 14,669 day period and an eccentricity e=0.09. Allanfloering’s world, if it exists, lies 11.77 AU from 14 Her, out at a Saturn-like distance.

Wittenmyer et al. show that the addition of their new 14 Her data suggests that 14 Her “c” has a period of order 6900 days, albeit with a low eccentricity. In their models, “c” and “b” may be participating in 4:1 resonance. A quick fit on the console with the Wittenmyer et al data included gives a radial velocity curve that looks like this:

corresponding to a planetary configuration that has an outer planet with a modest eccentricity e=0.20.

As soon as the data go up on the site, feel free to try working up improvements. It will be interesting to see how many fits to the full 3-telescope data set are participating in 4:1 resonance.

Web 2.0

fenceposts at ucsc

Hey ya’ll, there’s a whole lotta fittin’ goin on out there in the back 40.

Seriously, though. We’re really seeing a great response from users who are contributing their efforts. Nearly 200 people have registered on the back-end during the past few days, and over 750 different radial velocity fits have been uploaded. Hopefully we’ll see that work continue to flow in, and everyone has been showing admirable patience as we smooth out the inevitable rough spots which began to show up as soon as we had a surge of real users on the site.

If you’re arriving by way of the Sky and Telescope article, you’ll notice that the full universe of 100,000 synthetic stars is not yet listed on the systemic backend. During September, we’re still carrying out the first phase of our planned research effort, which consists of accumulating a wide variety of fits to the full collection of actual, published radial velocity data sets. Very soon, we will have accumulated enough fits to be able to present a dynamic, interactive catalog of candidate planets. A query-based dynamically generated planetary catalog will allow a variety of very interesting questions to be answered. For instance, by how much can one deflate the famous eccentricity-period diagram, while still demanding a prespecified goodness-of-fit for all of the candidate planets?

generated at exoplanet.eu

At the moment, such questions are hard to answer, because (other than here at oklo) there is no consolidated repository of radial velocity data and associated self-consistent fits.

In order to make dynamically generated planet catalogs scientifically useful, we’re going to have to provide several more tools to the users. As I mentioned yesterday, the console will soon be multi-threaded, which will make it easier to use for high-performance work. In the interim, however, you can have the console print a stream of diagnostic messages by launching it from the command line. For example, on linux or OSX architectures, open a terminal (shell), cd to the systemic directory, and type java -jar systemic.jar at the prompt . The diagnostics provide a running update of the progress of the console as it produces fits to the data set.

We’ll also soon be providing a long-term integration window that will allow users to verify that their model systems are dynamically stable. It’s alarmingly easy to find multiple-planet fits to radial velocity data sets that have low values for the reduced chi-square statistic, but in which the planets experience dynamical disasters (collisions, ejections, close encounters, etc.) on a time scale that is short in comparison to the known age of the parent star. Indeed, most of the candidate stars in the back-end catalog are more than 2 billion years old. Young stars tend to be rapidly rotating, which broadens their absorption lines and makes radial velocity measurements less accurate. Rapidly rotating stars also tend to have elevated levels of magnetically driven chromospheric activity, which adds additional noise to the velocity estimates.

And finally, the console needs to provide error estimates on the orbital parameters that it generates. This is best done using the so-called bootstrap method, which we’ll discuss in an upcoming post.

Systemic Challenge — data set #1

Image Source.

We’re continuing to see a strong influx of new users and activity on the systemic backend. Thanks to everyone who’s taking part! If you’re a first-time visitor to the Systemic Project website, please read the weblog entries that follow this post. They contain the information you need to start participating, and they give a recent day-by-day overview of the project developments.

Now that we’ve got an active user-base for the systemic console, we’re pleased to release the first Systemic Challenge synthetic radial velocity data set. This data set corresponds to a realistic simulated planetary system that is both scientifically interesting and non-trivial to fit.

Sky and Telescope is sponsoring the world’s first radial velocity fitting contest in connection with our challenge system. The person who submits the self-consistent (integrated) fit to the data having a chi-square value closest to one will receive a paperback edition of the Millennium Star Atlas (a $149.95 value).

Continue reading

consolidation

Image Source.

Wow! The American Scientist and Sky and Telescope articles are clearly getting the word out. We’ve been seeing a significant increase in traffic on the oklo.org site, both in terms of visits (yellow bars) and bandwidth and page views (green and blue bars). The bandwidth increase is especially gratifying. It reflects the fact that many users are registering on the back-end, downloading the console, and submitting fits. As I write this, new and interesting fits for a variety of different radial velocity data sets are rolling in to the star catalog. Our goal of fostering original, public-participation exoplanet research is starting to be realized, and I want to thank everyone who’s lending a hand.

Late August stats.

If you’re a first-time visitor to the Systemic Project website, please read the blog entries that were posted prior to this entry. They contain the information you need to start participating, and they give an overview of the current project status. If you are a return visitor, please have a look at the updated back-end. Stefano has made a number of code and design improvements that streamline the workflow and make the site easier to navigate.

On to some planet issues. The Mu Ara (HD 169061) system, which contains four known planets, is shaping up to have significant implications for the systemic project. Intense interest in the system has been spurred by a recent paper from the Swiss group (Pepe et al. 2006) that presents a self-consistent 4-planet model. Pepe et al.’s orbital fit (given in their Table 1) provides an excellent match to the radial velocity data sets, but when they carried out a long-term integration of the system, they found that the gravitational interactions between the planets lead to catastrophe after 76 million years. The parent star Mu Arae has an estimated age of 6.4 billion years, so clearly we don’t yet have a full understanding of what’s going on with this system.

The discord within the Pepe et al. model is provided by the two middle planets, one of which has a 310 day orbit, and the other which orbits in 643 days. The planets are on the edge of the 2:1 mean motion resonance, with the practical consequence that they experience a strongly chaotic orbital evolution. The orbits change eccentricity and orientation on a timescale of only decades:

I’ve made a movie that tracks the evolution of the orbits over 528 years. Here are links to a .mov version (288 kB) and an .mp4 version (1.5 MB). It’s clear from the movie that the interaction is both complicated and unpredictable. The planets display no catastrophic excursions on the 500 year timescale of the movie, but eventually, they experience orbit crossings leading to a likely ejection of the inner 0.5 Jupiter mass planet.

The Mu Ara dataset HD169061_B06P06CH on the console back-end combines both the Pepe et al. data as well as the most recent data from Butler et al. 2006. I’m hoping that someone can get a stable, self-consistent, low chi-square fit to this combined data set. Such a fit would give the best available view of what’s going on with the system, and would underscore the scientific relevance of the systemic project.