systemic

Janus and Epimetheus Source: JPL

Last week, I wrote a post about the negative heat capacity of self-gravitating systems. I never cease to find it remarkable that if you drain energy out of a system that is held together by its own gravity (such as a giant planet, or a cluster of stars), then that system gets hotter. There really is such a thing as a free lunch, brought to you courtesy of the attractive gravitational force.

A collection of bodies orbiting a larger body is a self-gravitating system, and therefore will also display a negative heat capacity. We illustrated this with the idea of a satellite running through a cloud of dust. Friction between the satellite and the dust heats both bodies up, and they radiate energy away to space. The satellite simultaneously spirals into an orbit with higher velocity, and hence a higher kinetic energy, or temperature.

A family of orbital trajectories known as horseshoe orbits present a riff on this basic principle. A horseshoe orbit occurs when two bodies, with slightly different orbital periods, start off in near-circular orbits on opposite sides of a large central mass. The body with the shorter orbital period eventually attempts to overtake the body with the longer orbital period.

As the short-period body catches up with the long-period body, an attractive gravitational force is exerted between the pair. This force pulls the short-period body forward, and pulls the long-period body back. That is, the gravitational interaction leads to an exchange which drains orbital energy from the long-period (leading) body, and gives energy to the short-period (trailing) body. This exchange causes the bodies to swap orbital periods. The long-period body gets a shorter period, and the short-period body gets a longer period. In a frame that rotates with the average orbital velocity of the pair, the two bodies eventually come in to contact again on the opposite side of the star, and the process is repeated. Again and again in an mindlessly delicate cycle.

The orbital trajectory in the above figure is lifted and adapted from a paper in the Astronomical Journal that I wrote with John Chambers. In that paper, we studied a number of weird co-orbital planetary configurations, and speculated that they might eventually be observed using the radial velocity method. If you can’t fit a particular data set with the console, the horseshoe configuration is always a good thing to check.

In our own solar system, there are two small Saturnian moons, Janus and Epimetheus, which are caught in a horseshoe-like orbit. The splash picture for today’s post shows a Cassini photograph of these moons taken near the time during which they exchange periods.

One of the most useful features of systemic console is its ability to sonify radial velocity waveforms. The soundfiles are produced by making a full integration of the equations of motion, hence all of the nonlinear gravitational interactions between the bodies are incorporated into the sound. When the console is used as a nonlinear digital synthesizer, the horseshoe orbits provide a method for producing amplitude modulation of a tone. To see how this works, launch the downloadable console, and set up the following system (just ignore the radial velocity data, since we’re not interested in fitting, but rather just in waveform generation):

That is, set up two 0.2 Jupiter mass planets with mean anomalies of 0 and 180 degrees. Make the period of one planet 10.1 days, and the other 10.0 days. For simplicity, keep the eccentricities at zero. Clicking the integration box shows the resulting radial velocity waveform. When the planets are on opposite sides of the star, their radial velocity influences on the star cancel. When they are on the same side of the star, their radial velocity influences are additive. This gives an overall modulation envelope on top of the fundamental ~10.05 day period. Use the sonify button to create a 220 hz tone out of this system:

Here’s a link to the resulting .wav file. The amplitude modulation (or tremolo) can clearly be heard.

Try building some more complex sounds by nesting horseshoe orbits, and using unequal masses. If you get something cool, e-mail me at laughlin ucolick edu.

Thanks to everyone who has created an account on the systemic backend, downloaded the console, and submitted fits to the HD 69830 data sets. It’s gratifying to see the collaborative effort coming together. We’re starting to get a better understanding of which aspects of the HD 69830 data set seem secure, and which aspects are uncertain.

That outer planet seems to me to be leaning toward the latter category.

For example, I just had a look at data set #17 for HD 69830. Guided first by the console’s periodogram and then by the console’s residuals periodogram, I worked up a two planet fit to the data. I kept the orbits of the resulting 8.66 and 31.7 day planets circular. In the absence of strong planet-planet gravitational interactions or resonant disk migration, I don’t see a clear rationale for assigning non-circular orbits unless the data really demands it.

The residuals periodogram of the 2-planet fit above has peaks near 200 and 400 days. The 200 day peak is a little higher, and indeed, corresponds to the outermost planet announced in the Nature paper published last week.

Use the folding window to look at the case for the 200 day planet. Try updating the period in tiny increments, and watch the data congeal into a relatively sinusoidal pattern. The third planet in the published fit is based on this configuration:

The 400 day data also looks good (although the power is not quite as high). Notice, too, that the phase coverage near 400 days is not as good. This is due both to the limited time baseline of the whole data set, as well as to the fact that the star can be observed only when it is not too near the Sun in the sky.

Apparently, the Las Vegas bookies are giving 3:1 odds in favor of the 200 day planet being correct. That said, however, the 400 day planet rounds out a very nice all-circular fit to the data.

Hats off to everyone who’s downloaded the console, logged into the backend, and submitted fits for the HD 69830 data sets. The process now seems to be working smoothly, but we need more users. Don’t be shy! We won’t make fun of you if you turn in high-chi-square fits.

First, a follow-up note to yesterday’s post: Some of our original HD 69830-based data files did not have all their radial velocities listed in time-ascending order. This caused the periodogram generator to fail when asked to analyze these data sets. If you downloaded the console yesterday, please download a fresh copy. The version on the site now has the correctly bundled data files.

The published radial velocity data sets consist of lists of times (in Julian Days), radial velocities (relative to an average baseline velocity), and uncertainty estimates for each velocity. These uncertainty estimates give an indication of how much imprecision is introduced at the telescope and by the measurement process itself. An additional source of velocity error, generally referred to as stellar jitter, is not contained in the published uncertainty estimates. Stellar jitter is produced by various processes that are occurring on the star itself. For example, at any given moment in time, there may be a larger portion of the stellar surface upwelling than downwelling, leading to a slight, temporary, net negative radial velocity. It has generally been assumed that for a Solar-type star, stellar jitter contributes roughly 3-5 meters per second of radial velocity error, and it is certainly true that stars somewhat more massive than the Sun (Upsilon Andromedae, for example) display close to 10 meters per second of intrinsic jitter.

Recently, however, as the radial velocity observational techniques have improved, it has become clear that some stars — low mass stars in particular — can have very small intrinsic jitter. Eugenio’s analysis of the GJ 876 radial velocities indicate that the jitter in that case is almost certainly less than 2-3 meters per second. HD 69830, however, seems to be in another category altogether. The published three-planet fit suggests that the star has considerably less than 1 meter per second intrinsic jitter. If this is indeed the case, and if there are a sizeable number of stars that are as quiet as HD 69830 seems to be, then it’s clear that high-cadence observations using the RV method are destined to eventually uncover potentially habitable planets, and likely sooner, rather than later. That’s a big deal.

The twenty alternate data sets for HD 69830 have been constructed to help us test whether the stellar jitter is really as small as the fit to the actual data suggests. Some of the synthetic data sets have been produced by adopting a model in which the stellar jitter is higher than 1 m/s. It should not be possible to find fully correct chi-square ~ 1 fits to these jittery data sets. In other words if we do find chi-square ~ 1 fits to these sets, then we’ve got a strong suggestion that overfitting might be occuring in the chi-square ~ 1 fits to the real data.

I’ll wrap up today with a set of screenshots showing how the backend environment operates. The best way to learn how it works, however, is to login and start using it. It’s quite self-explanatory.

After you’ve uploaded a fit from your own computer, you’ll get a response page that looks like this if the upload was successful:

Make sure that your fit file is appended with the suffix “.fit” before you upload it.

If you click on “view systems”, you’ll see a list of all the systems that have been added to the console thus far. All of the fits that have been uploaded by the systemic collaboration can be accessed from this catalog page. As of tonight, most of the systems have not yet been fitted…

Clicking on a system name brings up the corresponding system data page. There’s quite a bit of information available:

If you click on the icon next to a particular fit:

Then information about the planetary system corresponding to that fit is displayed:

Let’s see some activity! These planets won’t fit themselves…

I think we’ve finally got the pieces in place. Its time to really push the collaborative aspect of the systemic project. (1) Aaron’s downloadable console has been tested, updated, and is known to work on Mac, Linux, and Windows platforms. (2) Stefano’s systemic back-end collaborative space is tested and working. (3) Eugenio and Paul are standing by and ready to provide technical support. (4) We’ve got nearly 400 unique users visiting oklo.org every day, and (5) with HD 69830, we have an extremely interesting new system to subject to the analytical and computational power of the distributed oklo community.

The questions to be answered are (1) is the published HD 69830 fit unique? and (2) can we get an independent estimation of the errors?

To get an initial analysis of these questions, I’d like to invite (and encourage!) the oklo community to use the console and the back-end environment to obtain a wide variety of fits to a new set of 21 radial velocity datasets. These data have been uploaded onto the web-based console, and they are also packaged into an updated version of the downloadable console. The data sets include the published HD 69830 data, along with 10 bootstrapped datasets, and 10 model-based synthetic data sets. I’ll write much more about bootstrapping and synthetic data sets in upcoming posts. For the time being, we’re simply interested in finding a variety of fits to these data.

The rest of this post will take the form of a brief tutorial to get you going. We really need as many people as possible to participate in this effort.

First, download the console onto your computer. The link to the downloadable console on the right menu bar gives download instructions. If you’re using a non-US English character set on a Windows machine, you will need to switch to the US English set. (We’ll have a fix in for this shortly.) Launch the console on your computer.

Note that the console application, “systemic.jar” is contained in a directory (folder) that contains several subdirectories. These subdirectories are named “datafiles”, “fits”, and “soundClips”:

When the console is running, select one of the HD69830 data sets from the system menu, and obtain a fit. Once you’ve got the fit, use the “save” button (a new feature of the downloadable console) to save the fit in the “fits” directory. Use the suffix “.fit”, as shown below:

Next, point your web-browser to the systemic back-end. The full url is: http://www.oklo.org/php/login.php

You’ll see the login page. Register as a new user. Once you’re logged in, the environment is designed to be as self-explanatory as possible. In particular, you can upload your fit from your computer, and compare it with other users’ fits to the same system. Go ahead and explore! The back-end contains a number of very interesting features, which we’ll look at in the next post.

Source: Nicolle Rager Fuller NSF

HD 69830. What a difference a year makes. Last June, HD 69830 languished in the obscure backwaters of the Henry Draper Catalog. Now, however, like its buddy HD 209458, the star is a star. Google “HD 69830”, and the search returns 660 entries (and growing daily). Google “HD 69831” and (until the crawlers manage to find this post) your search does not match any documents.

In Thursday’s post, we gave an overview of the HD 69830 planetary system, which contains Neptune-mass planets in 8.67, 31.6, and 197 day orbits. Perhaps the most astonishing thing about this discovery announcement is the tiny radial velocity amplitude of the 197 day planet in the model. This object induces a radial velocity amplitude of 2.2 meters per second, with a reported error of only twenty centimeters per second. That’s about the speed your finger moves if you trace it quickly across the title of the discovery paper. This detection required a very quiet star and an extraordinary technique. The Swiss seem to have broken through to the next level.

I wonder what that outer planet looks like. Over at transitsearch.org, I have a Fortran cron job that processes all of the known exoplanets every night to produce updated transit ephemeris tables. In order to predict transit depths, the code needs an estimate for the planetary radius, which in turn requires an estimate of the effective surface temperature. The transitsearch model reports 262 K, just below the freezing point (273 K), suggesting a brilliantly reflective orb swathed in white water-based clouds.

In an upcoming post, I’ll delve into some responsible (and also some irresponsible) speculations about the world beneath those clouds. A responsible viewpoint has planet “d” forming at a larger orbital radius than it currently occupies, and then migrating in to position. In this formation-followed-by-migration scenario, there were plenty of ices available during planetary assembly, and the planet will have a structure (and size) very close to those of Neptune.

An irresponsible, more provocative scanario has planet d forming in-situ, out of refractory silicate and metallic materials. The final product in this case is a super Earth, smack in the sweet spot of the habitable zone, and endowed with ten Hubble times worth of geothermal activity. But more on that in the upcoming post.

A driving goal at oklo.org is to get our readers beneath the headlines and critically examining what the radial velocities themselves have to say. To do this, we need the data. The Lovis et al. discovery article in Nature contains a link to supplementary material, but when you click on the link you get a .pdf article about hydrothermal vent tubeworms:

Hmmm. Even if we adopt the most optimistic giant-Earth-like structural models for HD 69830 d, this supplementary material seems to be jumping the astrobiological gun. With tubeworms obscuring the radial velocities, we were compelled to resort to Dexter to extract as many velocities as we could from Figure 2 of the .pdf version of the paper. Eugenio managed to scrape 53 data points off the graph. We were busy using the console to work up fits to these dextered velocities when Darin Rogozzine at Caltech managed to guess the correct link and supplied oklo.org with the url.

In the next post, we’ll have a go at the rv’s. If you want an advance crack at them, they’re now on the web-based version of the console. We’ll get them on the downloadable version tomorrow.

Image source: designonline.se

Today’s astro-ph mailing contains a paper by McCollough et al. detailing the discovery of a new transiting planet orbiting a sun-like star lying in Corona Borealis. Dubbed “XO-1” — easily the coolest name yet for an exoplanet– this world has a year that lasts 3.941534 days, and a mass roughly 90% that of Jupiter. The temperature at the scalding, toxic, vortex-riddled cloudtops should be a torrid 1083 K. It ain’t no habitable world, folks, but as the fifth extrasolar planet found to transit a relatively bright (V=11) parent star, it’s big news nonetheless. Bright parent stars are great for planetary characterization, because they make detailed follow-up a lot easier to carry out.

The preliminary indications are that this planet, which has a measured radius of 1.3 plus or minus 0.1 Jovian radii, is somewhat larger than expected. Our theoretical models predict that XO-1 should have a radius of 1.05 Rjup if there’s a 20-Earth mass core, and 1.11 Rjup if the planet is core-free. If the large radius is confirmed, then we’ll be faced with the same radius problem that we’re facing with HD 209458 b (as explained in this oklo post from Dec. 2005). An interesting clue may be provided by the fact that the XO-1 parent star, like HD 209458 is not particularly metal rich.

The paper lists four amateur observers as co-authors. Three of them, Tonny Vanmunster, Ron Bissinger, and Bruce Gary, are long-time transitsearch.org participants. P.J. Howell is the fourth amateur co-author on the list. As usual, the photometry that these guys are getting is excellent:

Figure adapted from the McCollough et al. paper.

The paper describes in detail how the photometry from the amateur observers was able to effectively leverage and speed up the discovery, and how the ready-made network provided by the small-telescope observers eliminated the need for an expensive robotic follow-up observatory.

Sounds to me like it’s time to crack open a bottle of Hennessey XO. Congratulations all around, guys!

The published census of extrasolar planets grew by 1.57% today, with the Geneva Extrasolar Planet Search Teams’s announcement in the journal Nature that trois Neptunes orbit the nearby sunlike star HD 69830.

There are a number of reasons why the Swiss team’s paper is interesting. The HD 69830 system seems tailor-made for a detailed dissection with the Systemic Console. This dissection can get the oklo user-base up and running with the new beta version of the Systemic Backend. In addition, the configuration of this system has some fascinating consequences for the theory of planetary formation and evolution. It is definitely worth digging into this story for the next few posts.

First, the nuts and bolts of the announcement. The three planets, named — you guessed it — HD 69830 “b”, “c” and “d”, clock in with Msin(i) estimates of 10.2, 11.8, and 18.1 Earth masses respectively. Assuming that the system is co-planar and is being viewed close to edge-on, this places b and c squarely in the mysterious planetary mass range that falls between the ice giants (e.g. Uranus and Neptune) and the familiar terrestrial planets. Planet d is somewhat more massive, with a net bulk almost exactly equal to that of Neptune. [It’s important to remember that the inclination of any given planetary systems is more likely to be viewed edge-on (i=90 deg) than pole-on (i=0 deg) for the same reason that the Earth has more real-estate within a hundred miles of the equator than within a hundred miles of the poles.]

The published orbits of HD 69830’s planets are, however, distinctly unreminiscent of Uranus and Neptune. HD 69830 b orbits in 8.667 days, c orbits in 31.6 days, and d circles the star once every 197 days. All three have modest eccentricities.

For kicks, here’s a .wav format sound file which turns the reflex radial velocity waveform from the star into an audio signal. [Note: you can use the downloadable version of the Systemic Console to produce an audio representation of any planetary system, see this post from last week for the details.] In the sample file for HD 69830, I’ve pitched the innermost planet to a rather piercing 3 octaves above A 440. The period difference betwen the inner and outer planets leads to ~4.5 octaves of pitch difference. Planet d’s contribution can be heard as a bass drone about 2 octaves below middle C.

Indeed, the “chord” produced by these three new planets sounds terrible. Badly out of tune, to be precise. This immediately tells us that ther are no strong mean-motion resonances in the published configuration of planets. The human ear-brain system is good at on-the-fly calculation of whether the mean-motion resonance arguments are in circulation or libration. For example, this .wav file corresponds to a (synthetic) planetary system that is participating in several mean-motion resonances. When compared to HD 69830, it sounds awfully good.

As soon as I saw those periods — 8.667 days, 31 days, 197 days — I raced ahead through the paper draft to see if a photometric check for transits was carried out already by the discovery team… Excellent! There’s no mention anywhere in the paper of an attempt at a photometric search for transits of the planets. This will lend a challenging, high-profile opportunity to transitsearch.org. My guess is that the Geneva team was quite eager to get these three worlds out the door, and did not want to hold up the show with an exhaustive photometric check. There’s a real danger that you’ll wind up getting scooped if you cross all your photometric T’s before publishing your radial velocity-detected planets.

In the next post, we’ll look at what the radial velocities have to say.

Imagine leaving the front door open on a cold day, and having the inside of your house grow warmer as a result. Curiously, that’s exactly how self-gravitating systems such as stars, nascent giant planets, accretion disks, and globular clusters behave. Drawing energy from any of these systems causes them to heat up. The negative heat capacity of self-gravitating systems is one of the most central concepts in astrophysics.

The dynamics of the Keplerian orbit can be used to understand how this works. Imagine a particle initially on a circular orbit around a central star. The particle slams into a cloud of dust. As a result, the dust and the particle both heat up and radiate energy. The particle decreases its velocity and drops into an eccentric orbit with a smaller semi-major axis.

Here’s the key point: the smaller semi-major axis means that the average squared speed of the particle (averaged over an orbit) has increased. The fact that the particle is slow near apastron is more than compensated by the high speed near periastron. Since the particle’s kinetic temperature is proportional to its speed squared, the temperature of the system goes up. In effect, the reserve of gravitational potential energy gets double billed: once to provide the radiated energy, and a second time to increase the kinetic energy of the particle.

It’s a lot like taking a cash advance on your credit card and using half to pay late bills and the other half to buy a set of 22 inch rims for your Escalade. It’s a little sad to observe Nature operating on such a dissolute and spendthrift principle.

Hey all! This is Stefano, one of the Systemic team members. I’m an MSc astrophysics student at the University of Bologna, Italy, and will be transferring to the beautiful city of Santa Cruz next year to start working on PhD.

I just came back this evening (18 pm on the West coast) from the National School of Astronomy, Bertinoro, where I’ve been sent to last week. It takes place in an old little city, surrounded by walls and dominated by a castle. The castle has bedrooms and seminar rooms with frescoes and red carpets. I was sleeping IN the castle, when I woke up I could see the green planes of the pianura padana extending for acres and acres, and little rocky houses of farmers. The city is famous for its wine. Galla Placidia, daughter of the Roman emperor Theodosius, drinking a glass of the sweet white wine albana purportedly said to the wine “sei degna di berti in oro” (you deserve to be drank in a golden glass), from which the name of the city “Bertinoro” comes. The city itself is full of little places to drink wine (the amazing Sangiovese) and other kinds of alcoholic beverages, which of course we visited often, more than once a night! Whoever thinks scientists are grey, sad people should have come to one of these crazy nights.
That said, it was my first astrophysics school, and I felt so young and unexperienced! Everyone was working on their PhD, and was brilliant, accomplished, and just plain cool — at least to my eyes. I was feeling really out of place in the midst of these amazing minds talking about galaxies and AGNs citing models and theory with apparent ease.

Thankfully I soon realized that these scientifical “hierarchies” don’t really stop you to have your say and give your, even small, contribution! And anyone, from a last-year student like me to the famous astrophysicist, is collaborating in an amazing community to help develop our knowledge of where we are and what’s been before us.

All this to introduce the systemic Backend. The systemic Backend lets you have your say in the field of extrasolar planets!

Thanks to the systemic console, you can fit radial velocity data taken by real astronomers and as easily as possible try to discover the evidence of unseen planets around distant stars. And it doesn’t matter if you’re an astronomer, an high school student or an astrophile out of budget for a telescope: if your findings are consistent with the data and explains the observations better than before, you’ve done it!

The systemic backend lets you share your results with other enthusiastic people, showcase your results and interact with your fellow colleagues, just as you would do on a myspace-like network. You can upload the fits saved from the console online from your account, and have other people enthusiastically comment or bash your findings. You might be doing real astrophysics, while knowing other people.

Try out the beta version of the system now, help us iron the bugs and the improvements to make!

The systemic console and backend will be part of a bigger picture — Greg will be talking about it in a future post.

More soon,
Ste

The systemic team is pleased to announce the release of an updated systemic console. Thanks to Aaron Wolf for coding it into reality, and to Eugenio Rivera for troubleshooting the platform-specific installation issues.

Downloadable Console: systemic.zip

The new version of the console has been successfully tested on multiple Mac, Windows, and Linux machines. Specific download instructions and Java information for the three different platforms are available on our new downloads page.

We’re very interested in feedback from users. If you are able to download the console, or if you have problems, please register as a user and let us know via the comment space for this post. We need as much specific information as possible regarding your version of Java and your operating system.

Finally, if you are using a Windows-based browser, and you do not see the following links on the sidebar to the right:

You may have to scroll all the way down to the bottom of the window to see the links.

Thanks, and have fun fitting!

— The Systemic Team