


Mars Rovers Have Incorrect Instruments Installed 294
Christopher Reimer writes "The New Scientist is reporting that the twin Mars rovers, Opportunity and Spirit, has instruments installed in the wrong rovers. From the article: 'While the bungle does not undermine the main scientific conclusions drawn from the data collected by the rovers, it is an embarrassing slip-up for a space agency that once lost a Mars spacecraft because engineers mixed up metric and imperial units.'"
Man (Score:5, Funny)
Cain't never tell them kids apart... (Score:5, Funny)
Re:Cain't never tell them kids apart... (Score:5, Funny)
Actually, one of the rovers just crested a hill and beamed back this photo of a sign that says "Death Valley 7-11"...
Re:Man (Score:5, Funny)
In Other News.... (Score:5, Funny)
Two for two (Score:5, Funny)
Puddnhead Wilson Goes to Mars (Score:2, Funny)
Re:Puddnhead Wilson Goes to Mars (Score:3, Informative)
From The Tragedy of Puddnhead Wilson:
He was a homely, freckled, sandy-haired young fellow, with an intelligent blue eye that had frankness and comradeship in it and a cover
Confusion...Why differing configurations? (Score:3, Interesting)
Re:Confusion...Why differing configurations? (Score:5, Informative)
Of course, it becomes a problem when you use the wrong calibration curve for the sensor.
Re:Confusion...Why differing configurations? (Score:5, Informative)
This is not a major thing. Yes, all the data collected from these sensors will have to be re-analyzed, but that should be a simple thing.
Re:Confusion...Why differing configurations? (Score:2)
Re:Confusion...Why differing configurations? (Score:2)
Re:Confusion...Why differing configurations? (Score:2)
Fortunately, now that the goof-up has been spotted, it is easily fixed by reanalysing the raw data with the right calibration. Corrected values for the first year's data will be available soon, says Steve Squyres, the chief scientist for the rovers.
Re:Confusion...Why differing configurations? (Score:5, Insightful)
It isn't a big deal. Instead of "Mars Rovers Have Incorrect Instruments Installed", a better headline would have been "Mars Rover Data Analyzed With Incorrect Calibration Data Files". But the editors would have rejected a headline like that.
It's true that the swap occurred when the instruments were installed. But it's really just a matter of semantics whether you consider the instruments to be swapped in the rovers on Mars, or their calibration files to be swapped in a computer's filesystem on Earth. Once the swap is discovered, it's over.
Re:Confusion...Why differing configurations? (Score:5, Insightful)
The lesson to learn here: if small problems exist, dig at them to see how far you can get and then fix *all* of the problems that you uncover. There are many other examples (including the 9/11 incident) but I think the point is obvious: there are problems at JPL that are not being looked at because *nothing* happened. They should be examined and corrected prior to a medium or large problem occuring.
Re:Confusion...Why differing configurations? (Score:5, Insightful)
No, small problems lead to no serious consequences. That's why they're called small problems. If they can lead to serious consequences then by definition they are not small problems. The magnitude of the problem is determined by the worst case scenario (Murphy's Law being what it is and all). Let's look at your example:
In the early 70's plant managers at a nuclear power plant in Alabamba, Browns Ferry Nuclear Power Plant, received reports that their insulation connecting to a cable room was not in accordance with fire specifications (small problem).
What is the worst case scenario if there should be a fire and the cables fail? If this is the cabling to the coffee pot, not much (small problem). If this is the cabling to the non-redundant control features of the nuclear reactor then this is a BIG problem and should have been treated as such.
Later workers testing the air-tightness of the room failed to follow the correct procedures by using candles to check the air tightness
What is the worst case of using this alternate procedure? In this case, there is an increased likelihood of fire. Even if the cabling was not faulty ANY fire is bad, so this should have been flagged as a BIG problem as well.
Both of these should have been recognized as big problems and not ignored. The fault is not that small problems were ignored, it was that they were not properly classified and prioritized. It sounds like there may have been many other problems as well, but they are not related to your main point.
The lesson to learn here: if small problems exist, dig at them to see how far you can get and then fix *all* of the problems that you uncover.
This sounds very profound but it is a fallacy. The lesson to learn from your example is to properly classify and prioritize potential problems. It is a major waste of time and effort to address every single tiny problem which creeps up, especially in highly complex systems it is close to impossible. There are only a limited amount of resources available. You must prioritize the truly important vs the trivial or you will never accomplish anything. BTW, way to pull out the nuclear bogeyman to help make your case.
Of course, this really has nothing to do with the NASA screw up since it really is a small problem. I doubt that the sensors were really that far off to begin with, and now that the problem has been discovered it can be 100% fixed with no loss of data. No harm no foul. Problems like this will continue to happen because everything NASA builds is a prototype! These are not mass produced items. When you build something (or write code) for the first time, is it perfect? I am also suspect of your conclusion that this problem indicates that "there are problems at JPL that are not being looked at." There may very well be problems in the bureaucracy, however this problem is indicative of nothing more than "shit happens." Of course, don't let this get in the way of a good NASA/JPL bashing.
Re:Confusion...Why differing configurations? (Score:4, Insightful)
When did I say this primarily applies to software developement? I don't even work in software developement. Your point was that every problem, large or small, needs to be addressed with the same diligence. This is ridiculous and impossible. Problems must be categorized and prioritized. This applies to everything, including software, hardware, as well as high-risk high-value technologies. Actually more so in this case since the system is more complex. If you do not evaluate and prioritize nothing will get done.
By your definition this isn't a problem because a reactor meltdown didn't occur.
Nice strawman, when did I ever say anything like that? My exact words were "Both of these should have been recognized as big problems and not ignored." That seems to be the exact opposite of claiming that there wasn't a problem. My point was not that there was no problem (obviously there was), my point was that the problem was not what you said it was (a small problem being ignored leading to an almost catastrophe).
I work as a reactor operator.
And I assume you spend your days tracking down and solving every problem, no matter how trivial? If someone forgets to change the water in the coffee pot you track it down and fix it, because any small problem could lead to catastrophe, right?
Wrong attitude.
Sorry, that's reality, where things do not always go according to plan, no matter how carefully you plan or test.
When you build something, you build it to specification, and you write procedures for it.... And then you test your product to verify that it meets the standards.
Of course you do, however sometimes you don't foresee everything when you write the spec or procedures, or sometimes you have a new assembler or mechanic come on board and something is not done quite correctly and the tests don't catch it, or any of a hundred other things. I am a mechanical engineer working in aerospace and I can tell you that SHIT HAPPENS, no matter how much we wish it didn't, and no matter how many tests you plan or steps you take in order to make sure it doesn't. Engineers are not supermen, and the people who actually put it together and test it are human too.
If it ever deviates, you carefully analyze the problem and fix it. If something breaks, you determine why it broke, because you might have a bigger problem.
Of course you do, I never said you just ignore the problem. However, my point was that this is a prototype, some problems are expected. What if your tests don't catch the problem and it isn't discovered until it is out in the field? In my field we fix the part and sometimes retrofit the fix back to units in the field, however NASA only has one shot at this. If NASA manufactured hundreds of these rovers you can bet that they would become super reliable and all of these issues would be caught and fixed. However, it is simply impossible to catch all of the potential issues in the lab, and a one off prototype is going to has a few mistakes.
You never say that "shit happens". "Shit happens" is just a codeword for "I'm too lazy to determine the real cause".
I'm getting pretty sick of your strawman arguments and misrepresentation of my position. Once again, I never said the problem should be ignored, I just said that this is properly classified as a small problem. It does not impact the mission success, and in fact it can be corrected 100%. Obviously NASA should still investigate the cause and take steps to prevent it in the future, however to expect an experimental prototype to be perfect is ridiculous, and taking NASA to task for this error is equally ridiculous.
Re:Confusion...Why differing configurations? (Score:5, Informative)
However, nothing is perfect, and each sensor has slight imperfections. Before they were sent up, each sensor was measured so that those imperfections could be accounted for. This calibration data is unique to each sensor. They used the calibration data for Spirit on the data from Opportunity, and vice versa. Luckily, since they still have the original(un-corrected, raw) data, it is easy to correct.
Re:Confusion...Why differing configurations? (Score:5, Informative)
Re:Confusion...Why differing configurations? (Score:5, Interesting)
This doesn't work for +/-5% and the next grade (+/-1%) because the parts are built differently.
Re:Confusion...Why differing configurations? (Score:5, Informative)
As a science teacher, I weep. For any instrument, it's important to perform calibration: to check the instrument against known samples, values, whatever, so that you can take the unique response of the instrument and convert it into a believable interpretation of the data. Every instrument has its own peculiarities, resulting from the (essentially unknowable) history of the construction of the instrument. Most of these features are entirely unimportant, if you know about them. So you run calibrations and figure out how to correct for the individual features.
NASA did its job here, in that the instruments were calibrated. Yay. Then they mixed up the instruments and installed package A into rover B, meaning the calibrations were in fact wrong. Luckily they keep all the raw data, so they can simply run it through the correct calibration filter now. Double yay.
But for all those saying "This is a small thing.": Wrong. They mixed up an entire package. Didn't it occur to anyone to actually, you know, label the two? Or to in fact make sure they weren't in the same lab at the same time? Or if that proved impossible, to keep track of which was which? Or to -- oh, I don't know -- check which package they were installing?
Excusing this as "just a minor thing" is akin to minimizng a case where you fall asleep while driving and are awakened by the rumble strips on the side of the road. Sure, you fell asleep. But you woke up and no one was hurt. No harm, no foul, right?
A minor screw up on its own, it still speaks volumes about NASA's continuing inability to cross all the t's and dot all the i's. And it's a pretty close relative to the error that cost us Mars Observer.
Re:Confusion...Why differing configurations? (Score:2, Insightful)
Oops, you just blew up a spacecraft with that spelling error. See how easy that was?
Unless you've tried this you have no idea how hard it is. Try designing a flight program to make sure all the i's are dotted and t's are crossed, then having the budget slashed over and over again until you can barely manufacture, test, and launch. Then try the same thing in a three-shift environment that goes on for a couple of years, and m
Re:Confusion...Why differing configurations? (Score:2, Insightful)
What got me is that surely you'd calibrate it after putting it in the rover. You don't calibrate something, install it, and then test it, you install it, test it, and then calibrate it. (Then test the calibration.)
So maybe they're confused, and the probl
Re:Confusion...Why differing configurations? (Score:2, Interesting)
Makes you wonder what happened to scientific methods, where the results drive the conclusions. I thought the case of fudging the measured data to fit the desired conclusions was limited to 'fixing' high school labs gone awry. I didn't realize
Re:Confusion...Why differing configurations? (Score:3, Insightful)
nah... (Score:5, Funny)
A very minor issue... (Score:5, Insightful)
Re:A very minor issue... (Score:5, Insightful)
When companies like Lockheed Martin finally have to start paying for all of their multi-billion dollar screwups in space, then this stuff will stop happening. Until then, people will continue to make a fuss because we're sick of a corrupt system allowing this crap to continue.
Only a minor issue because of luck (Score:5, Insightful)
So scientists would have spent the next 10 years developing their theories of martian geology based on incorrect data if either one of those rovers hadn't deployed and you call this a minor issue?!
This kind of error is inexcusable. But of course, it'll get brushed over because NASA was lucky enough to be in a position to fix it.
Re:Only a minor issue because of luck (Score:4, Insightful)
Not wrong, but swapped (Score:5, Informative)
Re:Not wrong, but swapped (Score:2, Insightful)
It is only by virtue of the luck that both Rovers are functional that NASA discovered this problem. If either one had end up dysfunctional after landing, this error would have remained uncorrected and scientists would be basing the next decade of Mars geology on incorrect measurements!
Re:Not wrong, but swapped (Score:4, Funny)
For that matter, WTF is Slashdot about?
No big deal... (Score:5, Informative)
They're the same device on each machine, with the same function. The only problem has been that the data received has been interpreted with the wrong calibration adjustments. Swap the calibration adjustments and rerun the data, and it'll be correct.
It would have been far worse if, say, one had a spectroscope and the other had a *drill*, and they were swapped, and each rover couldn't use the other's tool. And in that kind of a switch, it would be really bad, because the two devices would be visually distinct. But the swapping of two devices that are 99.99% identical, on two rovers that are identical, is no big thing.
Compared to the fact that the rovers are still running long after they were expected to die, this is a tiny, tiny thing.
Re:No big deal... (Score:3, Insightful)
See, that's what I thought happened at first. I assumed it was something like one had an X-Ray detector while the other had a mass-spectrometer or something (I would think NASA could tell the difference between a drill and a spectroscope). It was nothing of the sort, they got the calibration files mixed up between the rovers (technically the rovers mixed up between the calibration files, but it's the same end result).
This isn't journalism, this is headline mongering. Espe
Re:No big deal... (Score:5, Interesting)
Except for the fact that the same organization that made this error is designing other spacecraft. If they don't get to the root causes of the problem, like the failure of the technicians to properly follow the correct procedure to install the instrument and the failure of any other engineer or management to catch their failure to follow procedure, much larger problems could occur. Lets examine a couple of JPL's problem's in the last couple of years:
Galileo: High power antenna failed to deploy resulting in a much lower data transfer rate. This was due to technical specifications in the lubrication of the antenna not being reviewed when the project was delayed.
Mars Climate Orbiter: Burned up because the technical requirements were not met (converting from BES to metric).
Mars Polar Lander: Lost on landing. Cause is not known. Project team was rushed in accordance with faster, better, cheaper plan.
Genesis: Failed to deploy parachute and crashed on landing due to technical requirements not being met (backwards specification for G-force meters).
Mars Exploration Rovers: Software glitch early in mission due to failure to test software for its entire expected lifespan. Instruments swapped due to failure to follow procedure.
Some things we can get out of this analysis are that the QA was unsatisfactory. Procedures were not followed. Technical specifications were not verified. The culture was rushed (go-fever or product push environment). None of these are small problems, but they also point to much bigger problems: failure of the leadership to properly plan the project so that rushed timelines would not occur. This same culture is building new spacecraft. While JPL is a great agency and they do tremendous and incredible feats, they are not perfect and have lost several spacecraft and have had severe faults in others. These problems did not have to occur and more importantly these problems do not have to occur again in the future.
Re:No big deal... (Score:2, Interesting)
The Trashy Fucking File System (TFFS) has bitten many projects, and the response from WindRiver is "We can't fix it." Which they can't. They bought TFFS from someone else. And they can't fix it.. for some reason. It's really a pain in the ass and the "loss of a flash file system" happens infrequently enough that it is possibl
Re:No big deal... (Score:2)
Hedley
Root Cause (Score:5, Insightful)
Even though this minor event that has had no impact on the mission, it has shown that there are holes in JPL's QA system, their monitoring system, and their training program for building these rovers. If you want to dig further you might find that all of these problems were caused by an unnecessary sense of urgency which may have been caused by poor project planning. These exact problems have caused the loss of spacecraft before (and many of them were cited for the loss of Challenger and Columbia).
No investigation? The lead scientist really needs to take a look at his project management priorities. Having experience working in nuclear power I have learned and have been trained that small problems are many times the only symptoms of much larger problems. The lead scientist's attitude on the problem gives me no confidence in his ability to run a more complicated mission. Like in gambling, one or two successes doesn't mean that you are going to win on the next roll.
Re:Root Cause (Score:2)
Re:Root Cause (Score:5, Insightful)
Re:Root Cause (Score:3, Insightful)
Re:Root Cause (Score:2)
(official disclaimer: I work for the company, and yes please forgive the site ugliness, I'm working with a web dev as we speak)
Re:Root Cause (Score:2)
Actually what is worse, is it's possible there is no procedure to follow, so it could be an even bigger issue. From my experience in commercial industry a mixup like this is a big deal, no impact doesn't mean no problem. Every little problem should have a full investigation, and should have system improvements to address it; otherwise it eventually will happen again.
Re:Root Cause (Score:2, Interesting)
A more complicated mission? Landing two rovers utilizing air bags on another planet isn't complicated enough for you?
He was the PI but he cannot be expected to observe everyone's work personally. This sort of thing should n
Re:Root Cause (Score:3, Insightful)
"[He is] not embarrassed at all".
"It was an easy mistake to make. It happened during some very busy and stressful times."
The article says that he also says it is not fair to compare it to past mishaps because the spacecraft suffered no damage.
"There isn't going to be an investigation. We know when it happened."
He doesn't get it. The big problem here isn't that a technician goofed. The big problem is that noone caught it. The purpose of the investigation i
Cat calls from the cheap seats (Score:5, Interesting)
Let the New Scientist criticize from the cheap seats. It is hard to argue that the rovers have been anything other than a resounding success for over 400 days. I would have hoped /. would
instead print the recent story of the Spirit Rover
discovering
salty soil. [spaceflightnow.com]
Something fishy here... (Score:2, Insightful)
Wouldn't they have been labeled, what does this have to do with anything?
This doesn't effect results (Score:3, Informative)
As Lore said.... (Score:2)
Mixed up units (Score:4, Informative)
I'm getting pretty tired of this sound (text?) bite the media throws out. It wasn't mixed up units; it was error accumulation from switching back and forth between the units.
Re:Mixed up units (Score:5, Informative)
The cause of the loss wasn't mixed up units, though they contributed. The loss was caused by ignoring a growing discrepancy between the precalculated navigation values and the actual navigation values. The errors were well within the correctable range, but for a variety of reasons the subtly different but incorrect values were ignored until it was too late to correct for them.
Re:Mixed up units (Score:3, Insightful)
No, it wasn't. Yes, there was error accumulation. But the accumulation was due to a metric-english conversion factor that had been dropped during the port of the flight software from a previous program. The lack of decent documentation for the software meant that the folks assigned to do the port were unaware of the significance of the conversion factor. without the conversion factor thruster burns were executed incorrectly, resul
Re:Mixed up units (Score:3, Informative)
Re:Mixed up units (Score:3, Informative)
Do you happen to have a source for that? Wikipedia says the following:
http://en.wikipedia.org/wiki/Mars_Climate_Orbiter # The_metric_mixup [wikipedia.org]
The Mars Climate Orbiter's reaction wheels were kept within their linear (unsaturated) range through thruster firings in a procedure called Angular Momentum Desaturation (AMD). When an AMD event occurred, relevant spacecraft data was telemetered to the ground, proces
Not informative, but wrong (Score:5, Informative)
"On September 27, 1999, the operations navigation team consulted with the spacecraft engineers to discuss navigation discrepancies regarding velocity change (V) modeling issues. On September 29, 1999, it was discovered that the small forces V's reported by the spacecraft engineers for use in orbit determination solutions was low by a factor of 4.45 (1 pound force=4.45 Newtons) because the impulse bit data contained in the AMD file was delivered in lb-sec instead of the specified and expected units of Newton-sec."
Hats Off to NASA (Score:5, Insightful)
This stuff isn't easy. Just because you reap the benefits of the entire space program from your living room couch via the TV without actually contributing one bit does not mean you have any understanding of how complex and spectacular these great accomplishments are.
To the NASA / JPL engineers and scientists: Thanks.
Re:Hats Off to NASA (Score:4, Insightful)
Re:Hats Off to NASA (Score:2)
In other news: (Score:5, Funny)
Finish giggling about poor, dumb NASA... (Score:3, Insightful)
And can we tone down the headline sensationalism a bit? You'd think the rovers have a core drill where there should be a camera or something. They somehow managed to switch two spectrometers, as identical as modern metallurgy can make them, destined for two similarly identical rovers - and now the error's been uncovered and the data recomputed. Jeesh...
Hit it! (Score:4, Funny)
Identical rovers, you will find...
They look alike, they rove alike,
They even calibrate alike!
(Should I put this alpha-particle X-ray spectrometer in you...or you? Whoooaaaa!)
You will lose your mind!
When rovers...are two of a kind!
Identical Rovers! Tuesdays at 8 on SCTV!
... (the subject isn't missing... it's just dots) (Score:2)
bugs (Score:2)
'Bungle' is a bit too harsh... (Score:3, Informative)
Once the mistake was realized, they could easily accomodate it through other calibration techniques. I think the parent article is trying to raise a sandstorm in an otherwise rarefied atmosphere.
Speaking of slipups... (Score:4, Informative)
They should have... (Score:2, Interesting)
In further news (Score:2)
thinKMetric (Score:2)
[..]an embarrassing slip-up for a space agency that once lost a Mars spacecraft because engineers mixed up metric and imperial units.
Which wouldn't be a problem if the US would get with the program and switch to metric. Most of the rest (if not all of the rest) of the world has already done it. I don't know how scientists and engineers there can stand having to deal with that outmoded, ridiculous imperial system.
People do make mistakes (Score:2)
It's a very common concept in business, so why can't NASA seem to get it down?
I'm sure that there are many things to double check when it comes to spacecraft, but NASA has so many of these "human error" problems all the time, it seems. They really need to hire such a group now. If there's already a QA group for the project (w
"The rovers has instruments"? (Score:2)
Re:"The rovers has instruments"? (Score:2)
Beagle 2 had the correct instruments installed (Score:3, Insightful)
Spirit and Opportunity have performed incredibly well. These guys deserve nothing but respect.
Could be worse (Score:2, Funny)
Oops. (Score:5, Funny)
I recommended that one package should be marked with an "O" for "Spirit" and the other with an "S" for "Opportunity". I even donated the Sharpie marker and masking tape for this purpose.
It's not my fault that the implementation was screwed up. It's those numbnuts in the Vehicle Assembly Department who can't read a bloody memo.
Fortunately, I've left NASA for a position at the Department of Defense. My team is tasked with identifying sites related to the constructon of weapons of mass destrucion in South Korea.
k.
Re:Oops. (Score:4, Informative)
I know you were joking, but keep in mind that the names "Spirit" and "Opportunity" were chosen very late into the mission, as the result of a contest. Within JPL, the probes were known as MER-A and MER-B, and the rovers were known as MER-2 and MER-1. To make things even more confusing, for various sensible reasons they ended up putting MER-2 inside MER-A, and MER-1 inside MER-B, even though that made things more confusing.
So, considering that they were otherwise identical, can't you see how easy it would have been to get otherwise identical parts mixed up...was it supposed to go in MER-B? Or MER-2? I just remember it was the second one of something...
I've noticed that the more people earn (Score:2)
I guess being... (Score:3, Funny)
Re:If... (Score:2, Flamebait)
Re:If... (Score:3, Interesting)
Re:If... (Score:2)
Re:If... (Score:5, Informative)
when you have 100 resistors at 0.5% tolerance, you are gonna have drift, and you will have to calibrate them to the right parts, you can make 100's of those cars of the same make and model, but none will be exactly the same, especially when you have sensitive equipment. (Think odometer)
Re:If... (Score:5, Informative)
It's a calibration, the whole concept is no two things are the same. Any piece of instrumentation needs to be calibrated and that calibration is set for that device. No manufacturing can produce 2 identical things, just not possible since the two items could not share the same time and space in the universe together thus both are going to be slightly different.
Anytime you get a piece of gear, you get it setup, then you take some means of calibrating it and test it with something that has deemed to be as accurate as possible. Maybe some source such as a rock. But basically anything that will provide a common test basis for the device.
So say you are measuring temperatures on something in a lab. You set up a big system for collecting data off a bunch of thermocouples. Each one has it's own channel through it's own voltage modules and thermocouples and so forth. So you take a calibrator and have it feed a signal through the system to mimic a thermocouple. you get a calibration curve for a channel, then you go to the next channel with the same device and do the same for the next channel, this will be a different calibration. and then you work through them all. I have system set up with 16 channels at work and all use the same parts, but there is about 4 closely similar calibrations across the channels, but no two channels follow the same calibration.
NASA did the same, they built the devices, then calibrated them with the same rocks, and developed a calibration curve for each system, and that was to be kept with each rover, they swapped the instruments, so now they switch the calibrations and everything is fine.
This all goes back to simple accuracy and how close you can get things, but bottom line no two things are the same. Look at computers, you can have 100 computers, exactly the same built right in a row, with the exact same software and so forth. Turn them on and let the run under exact same conditions, some will have hardware failures, some will have software get wacky on them and so forth. It's just the way it works.
Re:If... (Score:3, Funny)
Oh, come on! It's easy!
ln rover_1 rover_2
See?
Re:If... (Score:2, Funny)
"you're".
you get it setup
"set up". ("setup" is a noun.)
something that has deemed to be
"has been deemed".
Each one has it's own channel through it's own voltage modules
"its" (both places).
but there is about 4 closely similar calibrations
"there are about".
Re:If... (Score:2)
Also, a single digit number should be spelled out: four, not 4
Re:If... (Score:2)
Damn you're Dumb!
Re:I want to fight for NASA but come on... (Score:4, Insightful)
No one outside the community even noticed this until recently, and in the end it really made no difference. So where's the beef?
Re:I want to fight for NASA but come on... (Score:2)
Re:I want to fight for NASA but come on... (Score:4, Funny)
How can I possibly listen to you when you cant even used the shift key properly.
Re:I want to fight for NASA but come on... (Score:2)
If you had enough intelligence to use the apostrophe key in the word can't maybe your opinion would have merit.
Those in glass houses......
Re:I want to fight for NASA but come on... (Score:5, Informative)
How can i possibly advocate for a mars mission when they can't even get this shit right?
The Mars mission is stupid but not for the reason you give.
Re:No, it's still stupid (Score:3, Insightful)
Post-Its are not static dissipative. You could have a static discharge damage components and you wouldn't even know until the rover had landed on Mars. You could accidently leave a Post-It on the spacecraft and cause damage. How do you know residue from the glue on the Post-It won't cause damage? Now you have to test for that. It is amazing how one s
Re:No, it's still stupid (Score:2)
Re:No, it's still stupid (Score:2)
The point is, these researchers knew that the spectrometers were measurably different -- that's why they had to be calibrated at all. They knew that it was important that spectrometer A went in probe A and not in probe B. Yet they somehow made a bone-headed mistake that w
Re:No, it's still stupid (Score:2)
Yes, but only if you buy them at OfficeMax. However anyone working in electronic industry can tell you that there are hundreds of types of antistatic labels, tapes, bags and markers that are designed to conduct current. This is a non-problem. Besides, most of the instrument is likely to be a flat, smooth metal, and you can stick anything you want to it.
In fact, compliance with basic ISO 9000 (9002, for one) requirements simply mandates that every single part is marked
Re:I know the REAL cause calibration Errors. Hirin (Score:2)
Re:I know the REAL cause calibration Errors. Hirin (Score:2)
Ever hear the saying "shit rolls downhill"?
If you put an incompetent leader up top, the bad decisions will trickle down. Anyone who
Re:Grammar? (Score:2)