Anonymous wrote:selden wrote:Does that imply that the current maps would be correctly alighed if the EAN were corrected?
No, the RotationOffset I give is also required to bring the prime meridian into the correct position.
Celestia seems to orientate the planets at J2000.0 with their equators aligned with the ecliptic, and their prime meridians pointing towards 12h RA. The Obliquity setting then tilts their north poles towards 18h, and EquatorAscendingNode screws them around in the plane of the ecliptic. To finally orientate the prime meridian, you need to insert a RotationOffset, too, which requires a bit of fiddly calculation because the position of the prime meridian is given in the books with reference to the ascending node of the planet's equator
on the plane of the Earth's equator, not the ecliptic plane.
So the RotationOffset I give also plays an important part.
Your explanation of Obliquity, EquatorAscendingNode, and RotationOffset is exactly correct . . . An important thing to note is that in an .ssc file, the obliquity is the angle between the rotation axis of a planet and the ecliptic, whereas many tables of solar system data list the angles between rotation axis and orbital plane. I'm not certain--but it's likely--that my use of 'obliquity' for the angle between rotation axis and ecliptic is incorrect. In any case, the incorrect value for the tilt of Mars is due to my confusion (many months ago
) about the reference plane for the obliquity. In anyone's interested, I have a small C program that I use to convert J2000 RA and declination into Obliquity and EquatorAscendingNode.
There's also a PrecessionRate parameter that gives the rate at which the rotation axis rotates about the normal to the plane of the ecliptic. One other useful parameter is Orientation, which is an axis-angle rotation applied before Obliquity, etc. that doesn't affect the axis of rotation; it's helpful for adjusting spacecraft and irregular satellite models so that they face the right way.
--Chris