Also, the AMD-compatible Intel 64-bit processors are just around the corner:
http://news.com.com/2100-1006_3-5150336.html?tag=n efd_top
They will demo a 64-bit Xeon next month at IDF. The new 64-bit instructions will be referred to as 'CT' (ala HT) but the important thing is that they are binary compatible with AMD's current x86-64 instructions. Now, as soon as they get past the 'demo' stage and release some chips, we can expect Microsoft to cough up its' 64-bit Windows for AMD64.
Yeah, they do have a clone of the two rovers in their lab and they have already been able to duplicate on it the 'fle jam' that brought Spirit to a halt.
I suspect that the 'files' they are talking about are all very small files (but now large in number), log entries and that sort of thing. The image data they pull in each day through the cameras would have to be deleted pretty quick as 256 Mb of flash RAM won't hold too many days worth of picture taking (though, like digital cameras, the rovers probably store image data in some 'raw' format that takes up less space than a TIFF).
I bet the people at Wind River, whose VxWorks OS runs the rovers, are sweating blood right now. Their home page currently has a Spirit panorama with the title "Mars 360. Not another OS in sight". Now, if we lose one or both of the rovers due to a file handling deficiency in their software, they're going to have a lot of egg on their face.
The delivery system is essentially the same as used on the 1997 Pathfinder mission. Same cubic space, though some modifications to account for the greater weight. As for the rovers, I agree that they should try to standardize on a basic platform. Over time they could improve the instruments, power system, and onboard computer but the chassis could stay the same, reducing development and production costs.
And today they explained that Opportunity actually rolled around in the crater like a dice tossed into a bowl. Made a figure eight before settling down. That explains a few of those 'imprints' that were off at odd angles. So while the odds of landing in a crater are supposedly incredibly low, once a bouncing rover intersects one its' odds of staying in the crater go up dramatically.
Here's a detailed, blow-by-blow from Jennifer Trosper, on how they have worked through Spirits' problem so far.
http://www.spaceflightnow.com/mars/mera/040126spir it.html
NASA engineers reported on Monday that they reproduced in their test facility the same error that hit the Spirit Rover last week. Basically, the file system didn't have any proper limits set and had created too many files, leading to a situation where the software would gag. They are now deleting older files such as those generated while traveling to Mars.
see:
http://www.nytimes.com/2004/01/27/science/space/27 MARS.html
I suspect that the teaming of NASA scientists with the spy satellite analysts that produced those results probably has a lot to do with their current ability to display Spirit and it's accessories in recent MGS photos. The spooks taught NASA a few new camera tricks.
Does anyone have any idea about the interior of the nearby large crater(seen in the descent images)? There appears to be two parallel light colored strips down inside it. They aren't perfectly parallel or uniform but they sure are odd!
Actually, I think the 'ROM' is an EEPROM and flashable. If they conclude they have a permanent problem with the Flash RAM they will likely reprogram the boot EEPROM with the work-around.
The latest comments, though, suggest buggy file system code - good because they can correct it - bad because for the moment Opportunity has the same bug waiting to spring...
Slashdot Mirror
Also, the AMD-compatible Intel 64-bit processors are just around the corner: http://news.com.com/2100-1006_3-5150336.html?tag=n efd_top
They will demo a 64-bit Xeon next month at IDF. The new 64-bit instructions will be referred to as 'CT' (ala HT) but the important thing is that they are binary compatible with AMD's current x86-64 instructions. Now, as soon as they get past the 'demo' stage and release some chips, we can expect Microsoft to cough up its' 64-bit Windows for AMD64.
Yeah, they do have a clone of the two rovers in their lab and they have already been able to duplicate on it the 'fle jam' that brought Spirit to a halt. I suspect that the 'files' they are talking about are all very small files (but now large in number), log entries and that sort of thing. The image data they pull in each day through the cameras would have to be deleted pretty quick as 256 Mb of flash RAM won't hold too many days worth of picture taking (though, like digital cameras, the rovers probably store image data in some 'raw' format that takes up less space than a TIFF).
I bet the people at Wind River, whose VxWorks OS runs the rovers, are sweating blood right now. Their home page currently has a Spirit panorama with the title "Mars 360. Not another OS in sight". Now, if we lose one or both of the rovers due to a file handling deficiency in their software, they're going to have a lot of egg on their face.
VxWorks, the software from Wind River used to run the Rovers, is proprietary commercial code. You want it, you pay them.
The delivery system is essentially the same as used on the 1997 Pathfinder mission. Same cubic space, though some modifications to account for the greater weight. As for the rovers, I agree that they should try to standardize on a basic platform. Over time they could improve the instruments, power system, and onboard computer but the chassis could stay the same, reducing development and production costs.
And today they explained that Opportunity actually rolled around in the crater like a dice tossed into a bowl. Made a figure eight before settling down. That explains a few of those 'imprints' that were off at odd angles. So while the odds of landing in a crater are supposedly incredibly low, once a bouncing rover intersects one its' odds of staying in the crater go up dramatically.
Here's a detailed, blow-by-blow from Jennifer Trosper, on how they have worked through Spirits' problem so far. http://www.spaceflightnow.com/mars/mera/040126spir it.html
NASA engineers reported on Monday that they reproduced in their test facility the same error that hit the Spirit Rover last week. Basically, the file system didn't have any proper limits set and had created too many files, leading to a situation where the software would gag. They are now deleting older files such as those generated while traveling to Mars. see: http://www.nytimes.com/2004/01/27/science/space/27 MARS.html
I suspect that the teaming of NASA scientists with the spy satellite analysts that produced those results probably has a lot to do with their current ability to display Spirit and it's accessories in recent MGS photos. The spooks taught NASA a few new camera tricks.
Does anyone have any idea about the interior of the nearby large crater(seen in the descent images)? There appears to be two parallel light colored strips down inside it. They aren't perfectly parallel or uniform but they sure are odd!
Mars Polar Lander, which was lost in 1999, was designed to land on the edge of the polar ice cap and dig for ice.
Actually, I think the 'ROM' is an EEPROM and flashable. If they conclude they have a permanent problem with the Flash RAM they will likely reprogram the boot EEPROM with the work-around. The latest comments, though, suggest buggy file system code - good because they can correct it - bad because for the moment Opportunity has the same bug waiting to spring...