Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>The result you are getting is off because of both aberration <em>and</em> nutation. If you were to compile PyEphem yourself and comment out lines lines 271 and 272 of <code>circum.h</code> then you would find that you get exactly the result that you expect — with those edits, the code would look like:</p> <pre><code> /* correct EOD equatoreal for nutation/aberation to form apparent * geocentric */ /* nut_eq(mjed, &amp;ra, &amp;dec); */ /* ab_eq(mjed, lsn, &amp;ra, &amp;dec); */ op-&gt;s_gaera = ra; op-&gt;s_gaedec = dec; </code></pre> <p>When you ask PyEphem to "go backwards" from an observed RA and dec to the sky-position behind them, it merely reverses refraction (which you have already turned off) and precession to generate its answer.</p> <p>Why does it stop there? Why does it not try to reverse nutation and aberration? (Besides the practical reason: that those quantities are estimated through expensive polynomials that cannot be easily reversed!)</p> <p>The reason why it does not attempt to reverse-compensate for nutation and aberration is that it does not know the range to the object that sits at the RA and dec you are asking about. If you are asking about that RA and dec because you saw a satellite passing overhead, for example, then aberration would be irrelevant — earth satellites travel in the same relativistic frame as the Earth does — and nutation would also be irrelevant, since you would not be interested in where the "ideal" pole of earth points — you would be interested in where the pole was pointing on the particular night that you looked up and observed the satellite passing overhead.</p> <p>So without knowing whether the object you saw is an earth satellite, or the Moon, or a planet out in the different relativistic frame of the solar system, or something even farther away, the "libastro" library does the simplest thing possible and stops there, rather than mucking up the answer with reverse-effects that might not even apply to your situation. I will keep this in mind, though, as I approach PyEphem's next version, and think about whether multiple <code>radec_of()</code> techniques might not be appropriate.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload