Quote from: Hanol on 12/10/2010 05:51 amQuote from: Steven Pietrobon on 12/10/2010 04:51 amQuote from: mikes on 12/09/2010 06:50 amAssuming the image is cropped (rather than scaled), an 800mm lens on a Canon 5D Mark II (as listed in the EXIF) subtends 1.653 arcseconds per pixelhttp://www.howardedin.com/articles/fov.htmlThe Dragon in the image is about 16 pixels across, so 26 arcseconds for the 3.6m wide capsule.S=O/H, H=O/S, distance = 3.6m/sin(26/3600) = 29kmIntuitively that seems too far to me. Please could someone check my maths?Two small errors. Rounding 16*1.653 = 26.448 to 26 and using sine instead of tan. I get 3.6m/tan(26.448/3600) = 28.1 km.Also, from the press conference I thought I heard the spacecraft land within "a 100 metres" instead of "800 metres" of the target point.The whole point is wrong. Yes, image was scaled by the web server upon rendering. May be 10 times, may be more. You never know. So all the math doesn't make any sense.I downloaded the full image and worked from that, not the inline server-scaled version. It could also have been scaled, but that generally strips the EXIF data so I'm guessing it wasn't.Steven: Thanks for the confirmation. Given the vagueness of pixel counting, I'm comfortable with the rounding! Precision is likely +/- 2km.
Quote from: Steven Pietrobon on 12/10/2010 04:51 amQuote from: mikes on 12/09/2010 06:50 amAssuming the image is cropped (rather than scaled), an 800mm lens on a Canon 5D Mark II (as listed in the EXIF) subtends 1.653 arcseconds per pixelhttp://www.howardedin.com/articles/fov.htmlThe Dragon in the image is about 16 pixels across, so 26 arcseconds for the 3.6m wide capsule.S=O/H, H=O/S, distance = 3.6m/sin(26/3600) = 29kmIntuitively that seems too far to me. Please could someone check my maths?Two small errors. Rounding 16*1.653 = 26.448 to 26 and using sine instead of tan. I get 3.6m/tan(26.448/3600) = 28.1 km.Also, from the press conference I thought I heard the spacecraft land within "a 100 metres" instead of "800 metres" of the target point.The whole point is wrong. Yes, image was scaled by the web server upon rendering. May be 10 times, may be more. You never know. So all the math doesn't make any sense.
Quote from: mikes on 12/09/2010 06:50 amAssuming the image is cropped (rather than scaled), an 800mm lens on a Canon 5D Mark II (as listed in the EXIF) subtends 1.653 arcseconds per pixelhttp://www.howardedin.com/articles/fov.htmlThe Dragon in the image is about 16 pixels across, so 26 arcseconds for the 3.6m wide capsule.S=O/H, H=O/S, distance = 3.6m/sin(26/3600) = 29kmIntuitively that seems too far to me. Please could someone check my maths?Two small errors. Rounding 16*1.653 = 26.448 to 26 and using sine instead of tan. I get 3.6m/tan(26.448/3600) = 28.1 km.Also, from the press conference I thought I heard the spacecraft land within "a 100 metres" instead of "800 metres" of the target point.
Assuming the image is cropped (rather than scaled), an 800mm lens on a Canon 5D Mark II (as listed in the EXIF) subtends 1.653 arcseconds per pixelhttp://www.howardedin.com/articles/fov.htmlThe Dragon in the image is about 16 pixels across, so 26 arcseconds for the 3.6m wide capsule.S=O/H, H=O/S, distance = 3.6m/sin(26/3600) = 29kmIntuitively that seems too far to me. Please could someone check my maths?
Well it strikes me that Spacex must be doing something right. They launched after quick fix (successfully) , separated the dragon (successfully), orbited (successfully) , reentered (successfully) and splashed down (successfully). Not a bad day for people that criticize them for having limited or poor processes.
If replacing hoses, adding diffusers & having to toughen up strongback arms are their major issues after this flight...
I think that the original "process failure" comment by Jim and backed up by others was prompted by the initial reports of "weld porosity", which steered people toward the conclusion that good welds don't just fail and that SpaceX should have caught the bad weld during the manufacturing QC process.Now I'm not sure if welding or porosity had anything to do with the failure.
They have a different process. They trade exhaustive analysis for more flights to shake out the bugs, but they are well-informed by a considerable depth of analysis. Given the relatively benign bugs they've shaken out so far while still managing to rack up a 2/2 flight history with F9, it's a process that seems to be working.A couple more flights down the line with these initial teething bugs ironed out and a reliable launch vehicle in service with highly competitive pricing, they're going to look really smart for not analyzing everything to death on the ground. Maybe luck had something to do with it, but they've got a winner in Falcon 9, and from what we can tell from the first flight, Dragon is no joke of a spacecraft, either.
All these add up to costs creep and soon they will no different than ULA.
Quote from: mikes on 12/10/2010 06:29 amQuote from: Hanol on 12/10/2010 05:51 amQuote from: Steven Pietrobon on 12/10/2010 04:51 amQuote from: mikes on 12/09/2010 06:50 amAssuming the image is cropped (rather than scaled), an 800mm lens on a Canon 5D Mark II (as listed in the EXIF) subtends 1.653 arcseconds per pixelhttp://www.howardedin.com/articles/fov.htmlThe Dragon in the image is about 16 pixels across, so 26 arcseconds for the 3.6m wide capsule.S=O/H, H=O/S, distance = 3.6m/sin(26/3600) = 29kmIntuitively that seems too far to me. Please could someone check my maths?Two small errors. Rounding 16*1.653 = 26.448 to 26 and using sine instead of tan. I get 3.6m/tan(26.448/3600) = 28.1 km.Also, from the press conference I thought I heard the spacecraft land within "a 100 metres" instead of "800 metres" of the target point.The whole point is wrong. Yes, image was scaled by the web server upon rendering. May be 10 times, may be more. You never know. So all the math doesn't make any sense.I downloaded the full image and worked from that, not the inline server-scaled version. It could also have been scaled, but that generally strips the EXIF data so I'm guessing it wasn't.Steven: Thanks for the confirmation. Given the vagueness of pixel counting, I'm comfortable with the rounding! Precision is likely +/- 2km. All pictures on the web are scaled, unless it's a separate download not rendered by the web server to your browser. Resolution of the Canon 5D mark II is 5616x3744 pix. Was this what you've been working with? And scaling done by the server doesn't modify EXIF. Also if picture was smaller then this, it was either scaled, or was shot using low resolution mode. So all this arithmetic is just a guess.
Or maybe the strongback is in the wrong place to survive repeated launches. All these add up to costs creep and soon they will no different than ULA.
Or maybe the strongback is in the wrong place to survive repeated launches.
“we’re confident we could get a fully operational vehicle to the pad for $2.5 billion—and not only that, I will personally guarantee it,” Musk says. In addition, the final product would be a fully accounted cost per flight of $300 million, he asserts. “I’ll also guarantee that,” he adds, though he cautions this does not include a potential upper-stage upgrade.[/i]
I think he very well thinks he can build a 125 mT HLV from where he is right now with only $2.5 billion. That's his point.He may or may not be able to do that, but that's what he claims.
Quote from: luke strawwalker on 12/09/2010 04:33 pmThis willingness to look at the data, take a calculated risk, make the decision, do the fix, and suck it up and light the candle is VERY VERY REFRESHING-- reminds me of the "old days"... Hopefully some of that will "rub off" on NASA before NASA just completely becomes the "Amtrack of space", surpassed by everything around it... One could argue that such is what got both Shuttle crews killed, and that that is why a couple of cracks in the stringers of an external tank are being looked at with such care.
This willingness to look at the data, take a calculated risk, make the decision, do the fix, and suck it up and light the candle is VERY VERY REFRESHING-- reminds me of the "old days"... Hopefully some of that will "rub off" on NASA before NASA just completely becomes the "Amtrack of space", surpassed by everything around it...
Quote from: luke strawwalker on 12/09/2010 04:43 pmKudos to Elon Musk! This is patriotism, pride, and passion in action!Isn't Musk from South Africa? He moved to the USA when he was 17, according to wikipedia. So perhaps it's just passion on his part. He certainly does love space.edit to correct - that was when he moved out of South Africa, but initially he went to Canada, not the US.
Kudos to Elon Musk! This is patriotism, pride, and passion in action!
Quote from: MP99 on 12/09/2010 05:22 pmQuote from: luke strawwalker on 12/09/2010 04:33 pmThis willingness to look at the data, take a calculated risk, make the decision, do the fix, and suck it up and light the candle is VERY VERY REFRESHINGHave to disagree with this. If you increase your risk, eventually it will cause an unnecessary fail.At the press conference, the NASA guy said that every time they came up with another question, SpaceX could show that they'd already considered it & it was OK. I took that to mean that NASA were happy that they could do this without increasing risk.cheers, MartinMartin is correct. Luke, what you're admiring was not taking a "calculated risk," it was having the independence and ingenuity to make a quick repair on the pad. But the reason they were able to make the decision and proceed quickly with the repair was that, as Elon said, they know their hardware extremely well. They knew the stresses in that area were low, and that they could cut off that portion of the nozzle without risk, but they re-did all the analysis anyway, to be extra careful and to satisfy NASA as well. If, in their mind, there had been anything "risky" about cutting away a portion of the nozzle, they would have taken a lower-risk option, like replacing the entire nozzle extension.
Quote from: luke strawwalker on 12/09/2010 04:33 pmThis willingness to look at the data, take a calculated risk, make the decision, do the fix, and suck it up and light the candle is VERY VERY REFRESHINGHave to disagree with this. If you increase your risk, eventually it will cause an unnecessary fail.At the press conference, the NASA guy said that every time they came up with another question, SpaceX could show that they'd already considered it & it was OK. I took that to mean that NASA were happy that they could do this without increasing risk.cheers, Martin
This willingness to look at the data, take a calculated risk, make the decision, do the fix, and suck it up and light the candle is VERY VERY REFRESHING
What was truly incredible was Elon Musk saying that a future Dragon is being planned to do a full powered landing and land on a helipad similar to landing a helicopter. You would launch on the Falcon 9 achieve orbit and have a powered reentry to a pinpoint landing with parachutes as a backup. That's truly incredible and it totally negates the need for flyback plane type vehicles using runways. Sorry Sierra Nevada, you have just been outsmarted and outclassed. Why have runways when you can land on a pad? By the time Dreamchaser is developed it will have already been ruled unnessessary.
Quote from: marsavian on 12/10/2010 06:01 amNo, what he is saying is that he could build it for $12.5bn which is still very good. The $2.5bn only refers to his fixed-price rocket development/integration costs on top of the $10bn cost-plus for development of the constituent parts but it is disingenuous to just quote it by itself. It may also not include Raptor.http://web02.aviationweek.com/aw/mstory.do?id=news/awst/2010/11/29/AW_11_29_2010_p28-271784.xml&channel=space&headline=NASA%20Studies%20Scaled-Up%20Falcon,%20MerlinBased on a roughly evenly split $10 billion budget for heavy lift, with half for the boost stage and half for the upper stage, “we’re confident we could get a fully operational vehicle to the pad for $2.5 billion—and not only that, I will personally guarantee it,” Musk says. In addition, the final product would be a fully accounted cost per flight of $300 million, he asserts. “I’ll also guarantee that,” he adds, though he cautions this does not include a potential upper-stage upgrade.No. This part is talking about the plans for the current heavy lift program. "Based on a roughly evenly split $10 billion budget for heavy lift, with half for the boost stage and half for the upper stage,"The rest is talking about SpaceX doing it for a lot less. "we’re confident we could get a fully operational vehicle to the pad for $2.5 billion—and not only that, I will personally guarantee it,” Musk says. In addition, the final product would be a fully accounted cost per flight of $300 million, he asserts. “I’ll also guarantee that,” he adds, though he cautions this does not include a potential upper-stage upgrade.There's some other recent article out there where he talks about taking 20% of the current budget for heavy lift (2.5 billion) and doing the entire system, while the other 80% would go toward the currently planned heavy lift. That way NASA would have redundancy.
No, what he is saying is that he could build it for $12.5bn which is still very good. The $2.5bn only refers to his fixed-price rocket development/integration costs on top of the $10bn cost-plus for development of the constituent parts but it is disingenuous to just quote it by itself. It may also not include Raptor.http://web02.aviationweek.com/aw/mstory.do?id=news/awst/2010/11/29/AW_11_29_2010_p28-271784.xml&channel=space&headline=NASA%20Studies%20Scaled-Up%20Falcon,%20MerlinBased on a roughly evenly split $10 billion budget for heavy lift, with half for the boost stage and half for the upper stage, “we’re confident we could get a fully operational vehicle to the pad for $2.5 billion—and not only that, I will personally guarantee it,” Musk says. In addition, the final product would be a fully accounted cost per flight of $300 million, he asserts. “I’ll also guarantee that,” he adds, though he cautions this does not include a potential upper-stage upgrade.