Ok -- this goes without saying, but... I've only tested this with the toy examples you guys have sent etc. Please verify the results on real data before relying on it.
Anyway, it's great to have contributed even such a small part to such a great undertaking! Cheers, Mike Ted Drain wrote: > Everyone, > I just wanted to say thanks for tackling this problem so quickly. It's > great to see that problems can be worked out like this and we really > appreciate it. > > Here is some background on what we're using this for: The current NASA > mission to Mars (Phoenix) will be landing at the end of May. They > normally view their current trajectory and associated uncertainty as a > plot of an ellipse projected on a plane that extends out from the center > of the body (with time to impact the plane being another parameter). > The spacecraft has to hit a very narrow entry flight path angle corridor > at the atmosphere - too steep and it burns up, too shallow and it skips > out. When this corridor is projected onto the plane mentioned above, it > forms a large circle around Mars. So those large circular plots we're > making are the safe entry corridor that the trajectory needs to hit and > the smaller ellipses are the possible trajectory entry points and > uncertainties. As you can imagine, it's fairly critical to get those > ellipses plotted accurately :) > > Thanks again, > Ted > > At 08:23 AM 12/21/2007, John Hunter wrote: >> On Dec 21, 2007 9:11 AM, Michael Droettboom <[EMAIL PROTECTED]> wrote: >> >> > > Porting this back to the trunk is non-trivial -- but I know John would >> > > like to do it, so I think it will happen once one of us has time. >> >> > I have ported this arc stuff to the trunk. It is in r4783. Please let >> > me know how that works, particularly wrt performance, for you. Some >> > things that are in C on the branch were done in Python on the trunk for >> > convenience. >> >> Awesome -- thanks again Michael. You keep stealing my holiday >> projects :-) >> >> I added a check to make sure the 'axes' instance was present at draw >> time, since patches can be added directly to the figure also, and >> noted in the docstring that this is an axes only object. >> >> I also added unit support, which is fairly trivial, and added Arc to >> the unit/ellipse_large.py test case and >> examples/unit/ellipse_with_units.py >> >> Great work! >> JDH >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Microsoft >> Defy all challenges. Microsoft(R) Visual Studio 2005. >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> _______________________________________________ >> Matplotlib-devel mailing list >> Matplotlib-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel -- Michael Droettboom Science Software Branch Operations and Engineering Division Space Telescope Science Institute Operated by AURA for NASA ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
