-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Show ☊ and ☋ with respect to the equator in body-centred inertial frames #1841
Comments
This sounds mostly useful, except for the Sun; the inclination of the Earth's orbit with respect to the Sun's equator is about 7°, and most other planetary orbits would be similarly inclined. Perhaps we should use the invariable plane of the solar system for the sun? The Sun's equator would be a useful reference plane in a system with a highly oblate star, but hopefully in such a system the invariable plane would match the stellar equator better (consider, for instance, the low inclinations of the large moons of Jupiter). |
Unfortunately, a similar problem applies to any body with meaningful obliquity, and there is no clear solution when the body is oblate or can be landed on.
Perhaps the solution is to offer two different body-centred reference frames:
We could make the x axis point to the ascending node of the orbit with respect to the equator of the orbiting body; this puts the x axis at the equinox, close to |
Relevant to the "show the inclination" part of this feature request: https://www.reddit.com/r/KerbalSpaceProgram/comments/9jug8y/mods_that_help_out_with_principia/. |
Further thoughts: showing nodes with respect to the invariable plane or with respect to the ecliptic in the heliocentric or geocentric frames respectively does not seem all that critical: for a heliocentric orbit, one can care about its deviation from the plane of the orbit of a planet, e.g. for a transfer, or for an Earth-trailing orbit (Spitzer, Kepler, STEREO-B, etc.), but we have more appropriate reference frames for that (body-centred fixing the direction of the Sun). We still do not want to show nodes with respect to the equator of the Sun, but we would want to do so for a very oblate star, and we want to show nodes with respect to the equator of Jupiter, so that showing nodes only in reference frames centred on a body with a landable surface is not the answer. Perhaps we should display the nodes:
|
Using the
The values seem large enough for the gas giants (in particular, they encompass the major satellites), and small enough as to not be a concern for the Sun (even the Parker Solar probe does not come close enough). For comparison, here are corresponding thresholds for some telluric planets:
These have a surface, so the thresholds would not actually be used. |
This is a bad criterion: as adding a technically-landable surface beneath a thousand kilometres of atmosphere should not change the way we display orbits. A possibility would be to take the maximum of
This means that we show the nodes for synchronous orbits (for these and lower orbits, the surface may matter), and when 𝐽2 is relevant. The table becomes
While this leads to slightly absurd results for the slowly-rotating planets (Mercury and Venus), where a threshold based on the synchronous altitude is picked even though the synchronous altitude would be outside the Hill sphere, and thus synchronous orbits would be impossible, this is fine: the body-centred non-rotating frame is irrelevant outside the Hill sphere anyway. The important thing is to avoid showing irrelevant nodes where the reference frame itself is relevant, which happens because the reference plane is not a dynamical property of the reference frame. |
This came up during the design discussion in #1840.
This is not quite as simple as changing the conditions for prediction nodes and flight plan nodes, since the xy plane for the body-centred inertial frames is currently the global reference plane (Earth's equator in RSS, Kerbin's in stock) rather than the plane of the equator of the relevant body.
Perhaps it would be easiest to change the definition of
BodyCentredNonRotatingDynamicFrame
so that it uses the same z axis asBodySurfaceDynamicFrame
, making the y axis the node Q rather than making the x axis the point B from figure 1 of the 2009 report of the IAU WGCCRE.Note that Q≠
♈︎
for Earth, since α₀=0; this motivates making the y axis the node Q, rather than the x axis, so that the x axis points towards♈︎
for Earth (in other words,BodyCentredNonRotatingDynamicFrame
for Earth would be the same asBarycentric
in RSS).Addendum: it seems GitHub ignores VS-15 on U+2648 ARIES unless it is within a code block.
The text was updated successfully, but these errors were encountered: