marcus said:
The update just showed the simulated image of Dawn turned so as to be in picture taking mode.
http://neo.jpl.nasa.gov/orbits/fullview2.jpg This happened at around 1:30 PM Pacific time as far as I can tell.
The distance range is given as 149 thousand km.
The table copied back in post #45 estimated that the picture would be taken at 146 thousand km, today.
(EDIT: actually the current status distance changed to 146 thousand km later today. Maybe there is no discrepancy. Unsure about this.)
A discrepancy could suggest that some unexpected factor entered in, but most likely I think it just says what we may have guessed already that the table distances are just estimates. And it's all more or less approximately consistent. I'm very glad we have both the table, and the current status simulated views, and they match up tolerably well.
...
Dawn induced panic attack #47.
Just checked "fullview2.jpg", and it's still in photo/data x-mission alignment.

Checked the DSN, and no data was being received.

Somethings wrong!
Just rechecked DSN, and data is streaming in at 125 kb/sec.
Phew!
Anyways, Dr. Rayman, in his last email said;
Hi Om,
...
The Where is Dawn Now? feature is not accurate enough to warrant using so many significant figures. See this recent point. And I've explained in many Dawn Journals, sometimes we thrust and sometimes we coast, and the coast periods are neither regular nor of uniform duration. ...
I don't mean to be discouraging. Quite the contrary! I love doing the kind of thing you are having fun with, and I admire your creativity and insight. I would simply point out that it's worth being careful and recognizing the limitations. I'm too busy to provide details, but I hope you find some more in my prior Dawn Journals and, most importantly, that you continue to be so interested in the mission!
Sorry, I'm not a fan of TMBG. I love your PPS! Thank you for being considerate with my time. And now, I will indeed stop responding to your emails.
Marc
As if he could discourage us! And the limitations are only exacerbated by the fact that I lazily didn't bother to note the UTC times, so, in the following excerpt from my spreadsheet, corresponding to the published projected dates and distances, I included both the previous and following days data. Which, up until February 19th,
is completely accurate, +/- a day.
Columns B, C, & D are my projections. Column E is Dawn published projections.
And as I mentioned, please ignore all of
my data after Feb 19th.
I probably should have changed the "Distance 1000 km" functions after the 19th, as the "x vs y" components of the velocity get really big, inducing planetoid crashing results.
(The "x vs z" number was based on the published distance(hypotenuse) vs 20,000 km, if that makes any sense.)
Though, looking at the projected data and images again, I probably should have used a number closer to 40,000 km as my "x" orbit intercept value.
Oh well, I guess they're lucky I'm not flying the vessel.
And thank god for Emily:
She's averted panic attack #48.