Some Notes on Orbital Mechanics
tjradcliffe.com
tjradcliffe.com
Here's a couple of recent papers:
Using Graphics Processing Units to solve the classical N-body problem in physics and astrophysics http://arxiv.org/abs/1411.5234
The GENGA Code: Gravitational Encounters in N-body simulations with GPU Acceleration http://arxiv.org/abs/1404.2324
Remember - he's using only ~11 bodies. The problem remains mainly sequential for that number of bodies.
I happen to be a physicist too, and my stance on climate change is identical to yours. I don't think we'll ever have a climate model with detailed predictive ability: the system is too complex and the initial conditions too uncertain. But we really need to stop changing the composition of the atmosphere; mainly, we need to move quickly away from burning coal, for several reasons. I agree that we should do this through incentives and development of alternatives, not through a "revolutionary" approach.
It was refreshing to read something rational about climate. Everything I've seen lately (although this isn't my field) is either "we can't predict climate so we should stop worrying and just keep burning coal" or "it's already too late because the models are true and we have to shut everything down now or we're all going to die."
On your orbital simulations: you seem to be using physical units. Often people avoid some of the very big or small numbers by using, say, the Earth-Sun distance as the unit of length or the Earth mass as the mass unit. Do you just prefer physical units, or are you doing this and I missed it? Either way, very interesting demonstration of the effect of the Moon on the Earth orbit - would not have guessed this result.
P.S.: Go gnuplot!
We are in an era, aptly called the Anthropocene, where Humans, while spreading like cancer, are basically taking crucial breathing space away from our co-habitants.
I wish there were some sort of joint efforts underway to curb populations, in countries like India, and at the same time curb consumption in the Western world.
Sadly, the debates are all extremely partisan, and play by old - petty- rules of geopolitics.
Curbing consumption? Same again. Love to know what you have in mind to stop the buyers and how to re-employ the producers?
Finally, 'all' debates? You're that positive?
The best way to curb a population is to accelerate a Third World country into the First World consumption you so denigrate.
Suddenly, female fertility drops below replacement when being a female doesn't suck.
I will not deign fools with answers.
From his perspective, of course, using Runge-Kutta makes perfect sense. This is "Huh: I have this tool, and applying it to this problem wouldn't be too hard; would the tool work?", not "I should create a new tool."
ETA: couple of forgotten words.
Having said that, it is an adaptive RK scheme, and it seems to work pretty well, the article shows that the results match some reference data quite well, and it even captures some quite subtle effects, most notably the influence of the moon.
Probably he should have done research before he started, he would have found one of the several lecture notes that tell you how to integrate orbits. They tell you that symplectic methods are great for time reversible problems.
Or he would have found one of the public codes for integrating the solar system very far into the future.
I really didn't expect the RK4 thing to work at all, and once it was clear it kind of did decided to push on for fun.
It may be better to use a symplectic integrator.
Curiously, the comparisons I've seen between RK4 and symplectic integrators all use fixed step sizes. I used RK4 with adaptive step size because I had the code around, having written it for a different project about ten years ago that involved mostly smooth motion with a few tight turns that required a very small time step. By making the step size adaptive I could get decent run-time performance while retaining good accuracy.
I'm tempted now to write a symplectic integrator and see how it performs against adaptive RK4.
Also, I wouldn't call 10% error in an invariant "good accuracy".
http://onlinelibrary.wiley.com/doi/10.1029/2010GL045777/full
I forgot, as I often do, how common the fundamental attribution error is: https://en.wikipedia.org/wiki/Fundamental_attribution_error