On Sat, Mar 28, 2009 at 12:30 PM, Keith Lofstrom <span dir="ltr"><<a href="mailto:keithl@kl-ic.com">keithl@kl-ic.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Tony, good work!<br>
<div class="im"><br></div>
<font color="#888888"></font></blockquote><div><br>Ubuntu Hardy (8.04) seems to handle unicode OK. I stayed away from Greek and<br>other special characters, not being ready to assume that everyone would be able to<br>read them. The true anomaly I referenced is õ in the diagram, and argument<br>
of periapsis is ù, as you indicated. I also thought about using OO for<br>documentation, for better formula rendering.<br><br>Since I'm still skeptical about my code, there needs to be some independent<br>verification path, maybe an existing orbit simulator. The TLE data is snap shot,<br>
but a TLE history for a particular object might give a rough gauge. I don't know<br>yet how well a set ot TLE's populates an orbit.<br><br>I have access to the TLE data, and am playing with download options. One class of<br>
prepackaged data sets is a twice daily collection of all TLEs for objects with updates in the last 30 days. I've been using those sets (three-line to get the object name). The <br>first one I used had ~38k lines or ~13k entries. Of those, ~1k showed m288 <br>
intersection.<br><br>I'm using the c++ SGP4/SDP4 algorithm library that I modified to support my<br>development. It provides an orbit object that translates TLE to orbit description<br>including apogee, perigee, semi-major/semi-minor axes, useful angles and other<br>
stuff (added an entry on the wiki, and uploaded a set of source/build files).<br><br>- tony<br><br><br><br><br></div></div>