FWIW - accounting for the dust cover - it looks pretty much how Mars has always felt in my head.

This - also - is exactly how it looks in my head. http://mars.jpl.nasa.gov/msl/multimedia/ra...E1_DXXX&s=0

It's a judgement call at the end of the day. Even dragging a single JPG between two monitors that are not calibrated can result in dramatic changes. Ditto printers etc etc.

We'll be going the other way, it was intentionally thrown away from the science. And we'll almost certainly have HiRISE before we have MastCam of it.

No - MastCam (and or HiRISE) will tell us if the descent stage is right behind the rover ( which it should be ) but it can't tell us if the feature in those two RHAZ 256x256 from Sunday night are actually the impact plume.

Given the rover heading being approx ESE - the descent stage would have headed 'backwards' from the rover - into the rear-haz FOV.

Personally, I consider it a very likely candidate. What I've not been able to establish is if those pre-cover deploy images will ever be returned at higher res than 256x256

Doug's guess. 400 meteres from the rover on a bearing of 292 degs.

Turned the MARDI movie into an ANIM Gif at 4x the speed it was on NTV

Be that as it may - I can tell you they ARE turned in - toe in - 40ish degrees.

The front wheels are turned in 40ish degrees - they have been since final ATLO.

www.nasa.gov/ntv
http://www.ustream.tv/nasahdtv
www.ustream.ntv/nasajpl

First website if you Google NASA TV

ODY doesn't need to go 'back' to Opportunity - it's perfectly capable of doing daily relay for both Opportunity and Curiosity. The plan is to use both, regularly. Why turn down an opportunity for an extra 100Mbits or so per sol?

Well - Eyes on the Solar System was off by half a dozen seconds we think - and it was running OD142, a several week old predict.

Currently running on about 3 hours of sleep. Back to the office for the 9am press conf

I had 2 minutes during the last ORT

Personally - I agree with you We must be facing east given the shadow, and Sharp should indeed be visible to our east. A nominal touchdown toward the center of the ellipse would put the dunes in view also.

It's not really a Gigapan ... but it seemed the right place to host it and tag people in it ... I took that

I'm afraid you're getting ahead of the game, Craig.

There hasn't been another UHF pass with the vehicle since that second ODY pass - so expect nothing new from the surface. I think social media is fairly in-tune with the HiRISE team and that they do indeed have something special to show us.

It not even midnight of Sol 0 yet - no HGA deployment details. No MARDI yet (we will get a few thumbnails later today - it will take weeks to get the full image sequence)

There has certainly been some fascinating discussion about what we can see in those early Hazcam images - hopefully some analysis of that as well.

No - firstly, the ground is clearly has pebbels on it. Secondly - the FHZ image, small though it is - shows the dune field a dark linear feature to our east.

For those who might have had Java issues, we've retained the classic Unity browser plugin version that we're calling 'Classic' Eyes...

There's a little link bottom right of the page - http://eyes.nasa.gov/

And so will I - but much earlier than Rob. I'll be on at about 8.50pm local time during the educational pre-show to talk about Eyes on the Solar System and the AR App. Infact, my colleague Jon and I will be sat about 6 feet behind Gay, the presenter of the EDL broadcast, on Sunday night. Rob - I promise not to heckle. :-)

And - tomorrow morning ( at 10am and 11am local ) there is a Science, and an Engineering pre-landing conference. Both should be worth watching.... usual links apply - www.nasa.gov/ntv or www.ustream.tv/nasajpl or /nasajpl2

No - it doesn't do that. It will land where it lands - and it's simply a statistics game as to how likely it is that there will be a problem.

All the radar does is plot altitude, vertical and horizontal velocity

Our cunning Java guru developer had this to say....

"predictions - ddeerrff is behind a proxy and imipak is using a 64-bit version of IE {which does not load the java plugin}."

He's putting some more bug-reporting stuff in place tonight.

D

Those are called rover-traps and they were taken into account during the landing site selection process thru Paolo's amazing work

There are some, but not many - they represent a tiny tiny fraction of the ellipse.

For me it works fine on Win7 with FF or Chrome, OSX 10.6 on Safari, FF and Chrome, and 10.8 took some tricking (you can only activate java by spotlighting for java preferences) - but then it worked great. Infact, my little 13" Macbook Air is getting 30fps+

Yeah - that's a symptom of a double-precision world being rendered on top of the normal 'Eyes..' - it's a mega kludge to get this thing working. We're going to just disable the zoom for the time-being. This one was on our list but needed a reminder - thanks.

I'm sending one of the Dev's this way to look at the Java based issues.

Java >>>>>> Unity browser plugin.

It's normal terra-firma miles. Of course, you can switch to KM under visual controls

But yes - I think spoots/second is probably the best