Please register to participate in our discussions with 2 million other members - it's free and quick! Some forums can only be seen by registered members. After you create your account, you'll be able to customize options and access all our 15,000 new posts/day with fewer ads.
The Jet Propulsion Laboratory is a part of Cal-Tech, and has been for roughly 30 years before NASA even existed-although under a different name. The JPL is considered NASA, but it is more a part of Cal-Tech as most of the employees working there are employed by Cal-Tech as the JPL is managed by Cal-Tech with NASA only having a field office. If I remember correctly, NASA funds the JPL, though. The JPL has a long history of designing and building systems for the U.S. Military, so I suppose it made sense to transfer the JPL to NASA in...1958 I believe.
The JPL is the "team" that took on the Curiosity Mission.
I also believe that most, if not all, of NASAs laboratories are either a part of a research university or a private business. Like all Government agencies, projects tend to be contracted out.
I understand what you are saying about the lack of keeping the project local, but, research science tends to not be limited to a country's borders. It's generally a global affair with the originating country taking the bragging rights. Despite the international effort, NASA, and thus America, will take the credit.
JPL also does its own programming. They have published several books on the subject of software development. I read a few of those books back in the 1980s and have used their methods for the last twenty-five years developing software for various businesses. JPL's software standards are far more stringent than any business would ever consider using.
Siemens may have written the code for the Curiosity probe, but it was JPL that got the MSL to Mars and landed it safely.
NX CAD/CAM/CAE was Unigraphics, which got started in the late 60s from an American company. It stayed American all the way until Seimens bought EDS (aka Ross Perot's company).
So basically it's an American product that's now owned by a German company. But in reality, the Seimens branch that owns the PLM and CAD/CAM/CAE packages is based out of Plano, TX.
So before you start going and bellyaching that "OH NASA IS ANTI-AMERICAN!" "OH WOE IS UNTO AMERICAN BUSINESSES!" make sure you do some reading first. This is for all intents and purposes an American company supporting American jobs with American know-how ... it's just a few layers of management are now German at the top.
NX CAD/CAM/CAE was Unigraphics, which got started in the late 60s from an American company. It stayed American all the way until Seimens bought EDS (aka Ross Perot's company).
So basically it's an American product that's now owned by a German company. But in reality, the Seimens branch that owns the PLM and CAD/CAM/CAE packages is based out of Plano, TX.
So before you start going and bellyaching that "OH NASA IS ANTI-AMERICAN!" "OH WOE IS UNTO AMERICAN BUSINESSES!" make sure you do some reading first. This is for all intents and purposes an American company supporting American jobs with American know-how ... it's just a few layers of management are now German at the top.
I'd rather it be German than Chinese.
Thank you.
Some people wouldn't recognize sarcasm if it hit them over the head.....
Location: Mableton, GA USA (NW Atlanta suburb, 4 miles OTP)
11,334 posts, read 26,086,242 times
Reputation: 3995
Quote:
Originally Posted by Miker2069
I am loving everything about the Curiousity landing on Mars. I am a little disssapointed that NASA couldn't use an American company for the software which controlled all the critical components of the machines. Really not taking anything away from Siemens (who has this plastered all over their website, and deservedly so) but come on, no *American* company could have done this?
I know a number of people who have worked as software developers for Siemens in the US. The software could well have been written by American programmers. I would prefer that to software written in India or China for an American company, personally.
Location: Mableton, GA USA (NW Atlanta suburb, 4 miles OTP)
11,334 posts, read 26,086,242 times
Reputation: 3995
Quote:
Originally Posted by Glitch
JPL also does its own programming. They have published several books on the subject of software development. I read a few of those books back in the 1980s and have used their methods for the last twenty-five years developing software for various businesses. JPL's software standards are far more stringent than any business would ever consider using.
Perhaps, but I know from past experience that it took a long time for us to get software updates for our ACARS boxes back when I worked in flight ops IT for a major airline. Avionics firmware in civil passenger aircraft also has to go through some fairly rigorous testing.
Perhaps, but I know from past experience that it took a long time for us to get software updates for our ACARS boxes back when I worked in flight ops IT for a major airline. Avionics firmware in civil passenger aircraft also has to go through some fairly rigorous testing.
Very true. I used to work for Litton Aero Products out of Moore Park, California, during the 1980s and before anyone was allowed to write code, they first had to work as a debugger for a year.
Perhaps, but I know from past experience that it took a long time for us to get software updates for our ACARS boxes back when I worked in flight ops IT for a major airline. Avionics firmware in civil passenger aircraft also has to go through some fairly rigorous testing.
Ever since avionics and computers have found their way onto airplanes, they have been extensively tested. Transistors really allowed the boom in electronics on airplanes. There's so many regulations and standards to meet in testing software I have utter confidence in the code and firmware.
I work for a major aerospace firm, and worked on testing. I know. ... ... ... perhaps too well, stupid third shift test times.
Ever since avionics and computers have found their way onto airplanes, they have been extensively tested. Transistors really allowed the boom in electronics on airplanes. There's so many regulations and standards to meet in testing software I have utter confidence in the code and firmware.
I work for a major aerospace firm, and worked on testing. I know. ... ... ... perhaps too well, stupid third shift test times.
I recall a story I was told about a software bug in the attitude indicator. As soon as the plane crossed the equator the attitude indicator showed that the plane was flying upside down. I was told that the first plane to experience this software bug crashed into a mountain.
I do not know if the story was true, but it emphasized just how important it was to ensure the code functioned properly all the time.
Please register to post and access all features of our very popular forum. It is free and quick. Over $68,000 in prizes has already been given out to active posters on our forum. Additional giveaways are planned.
Detailed information about all U.S. cities, counties, and zip codes on our site: City-data.com.
Please register to participate in our discussions with 2 million other members - it's free and quick! Some forums can only be seen by registered members. After you create your account, you'll be able to customize options and access all our 15,000 new posts/day with fewer ads.
