Author Topic: The CRS-2/SpX-2 "Junk in the Trunk" Party Thread (Read 159473 times)

wolfpack · « **Reply #180 on:** 03/01/2013 03:18 pm »

Quote from: mduncan36 on 03/01/2013 03:08 pm

They're gonna figure this out and it will be hailed as a testimony to the robustness of Dragon. Wait for it...

No, it's going to be a harsh reminder to be diligent about code coverage. Don't execute a line of code on orbit that hasn't been executed on the ground beforehand!

Just my guess.

Jason1701 · « **Reply #181 on:** 03/01/2013 03:19 pm »

Quote from: wolfpack on 03/01/2013 03:18 pm

Quote from: mduncan36 on 03/01/2013 03:08 pm
They're gonna figure this out and it will be hailed as a testimony to the robustness of Dragon. Wait for it...

No, it's going to be a harsh reminder to be diligent about code coverage. Don't execute a line of code on orbit that hasn't been executed on the ground beforehand!

Just my guess.

What if it's been executed in space three times before? Testing won't catch everything.

ugordan · « **Reply #182 on:** 03/01/2013 03:19 pm »

Quote from: wolfpack on 03/01/2013 03:18 pm

No, it's going to be a harsh reminder to be diligent about code coverage. Don't execute a line of code on orbit that hasn't been executed on the ground beforehand!

You're already placing the blame on software as opposed to a hardware issue. What's your rationale?

mduncan36 · « **Reply #183 on:** 03/01/2013 03:21 pm »

Quote from: Jason1701 on 03/01/2013 03:19 pm

Quote from: wolfpack on 03/01/2013 03:18 pm
Quote from: mduncan36 on 03/01/2013 03:08 pm
They're gonna figure this out and it will be hailed as a testimony to the robustness of Dragon. Wait for it...

No, it's going to be a harsh reminder to be diligent about code coverage. Don't execute a line of code on orbit that hasn't been executed on the ground beforehand!

Just my guess.

What if it's been executed in space three times before? Testing won't catch everything.

Exactly. It could be something about the environment in which the thrusters began the flight. It was cooler this morning so maybe an off nominal temp or condensation or who knows what caused the thruster inhibit.

Galactic Penguin SST · « **Reply #184 on:** 03/01/2013 03:23 pm »

Quote from: ugordan on 03/01/2013 03:19 pm

Quote from: wolfpack on 03/01/2013 03:18 pm
No, it's going to be a harsh reminder to be diligent about code coverage. Don't execute a line of code on orbit that hasn't been executed on the ground beforehand!

You're already placing the blame on software as opposed to a hardware issue. What's your rationale?

Quote from: Targeteer on 03/01/2013 03:11 pm

From (NASA TV) update, issue may be related to change of burn schedules due to accelerated docking time.

I don't know why such a conclusion was announced, but it seems more possible of a software problem to me...

mrmandias · « **Reply #185 on:** 03/01/2013 03:24 pm »

Quote from: padrat on 03/01/2013 03:14 pm

Being my first launch I don't really know enough about what's going on to say anything and I prob couldn't even if I did. Sorry guys. Ill just say they are working the problem and making progress. Cross your fingers....

Fingers crossed.

This is the first time I've ever said an actual prayer for a spacecraft, but what the hey.

mmeijeri · « **Reply #186 on:** 03/01/2013 03:25 pm »

Quote from: ugordan on 03/01/2013 03:19 pm

You're already placing the blame on software as opposed to a hardware issue. What's your rationale?

Still a good rule though.

mmeijeri · « **Reply #187 on:** 03/01/2013 03:26 pm »

Quote from: ugordan on 03/01/2013 03:19 pm

You're already placing the blame on software as opposed to a hardware issue. What's your rationale?

Heh, and as one poster here likes to say: if it's not on fire, it's a software problem!

Jason1701 · « **Reply #188 on:** 03/01/2013 03:26 pm »

Elon is gaining twitter followers at about 1 Hz.

Nickolai · « **Reply #189 on:** 03/01/2013 03:27 pm »

Uninhibit the thruster pods HAL.

I can't let you do that ~~Dave~~ Elon

Joel · « **Reply #190 on:** 03/01/2013 03:28 pm »

Quote from: Jason1701 on 03/01/2013 03:26 pm

Elon is gaining twitter followers at about 1 Hz.

That's what I suspected. This is all a PR stunt...

wolfpack · « **Reply #191 on:** 03/01/2013 03:31 pm »

Quote from: ugordan on 03/01/2013 03:19 pm

You're already placing the blame on software as opposed to a hardware issue. What's your rationale?

Like I said, guess. Hardware is simple compared to software. Software tried to stand an Ariane 5 on its head once.

Galactic Penguin SST · « **Reply #192 on:** 03/01/2013 03:33 pm »

From another member who wrongly posted in the updates thread:

"Uninhibit the thruster pods, HAL."

"I'm sorry, ~~Dave~~ Elon. I'm afraid I can't do that."

Robotbeat · « **Reply #193 on:** 03/01/2013 03:34 pm »

Quote from: Nickolai on 03/01/2013 03:27 pm

Uninhibit the thruster pods HAL.

I can't let you do that ~~Dave~~ Elon

yg1968 · « **Reply #194 on:** 03/01/2013 03:36 pm »

Quote from: Galactic Penguin SST on 03/01/2013 03:23 pm

Quote from: ugordan on 03/01/2013 03:19 pm
Quote from: wolfpack on 03/01/2013 03:18 pm
No, it's going to be a harsh reminder to be diligent about code coverage. Don't execute a line of code on orbit that hasn't been executed on the ground beforehand!

You're already placing the blame on software as opposed to a hardware issue. What's your rationale?

Quote from: Targeteer on 03/01/2013 03:11 pm
From (NASA TV) update, issue may be related to change of burn schedules due to accelerated docking time.

I don't know why such a conclusion was announced, but it seems more possible of a software problem to me...

I don't think that's what they actually said.

Jason1701 · « **Reply #195 on:** 03/01/2013 03:41 pm »

Quote from: yg1968 on 03/01/2013 03:36 pm

Quote from: Galactic Penguin SST on 03/01/2013 03:23 pm
Quote from: ugordan on 03/01/2013 03:19 pm
Quote from: wolfpack on 03/01/2013 03:18 pm
No, it's going to be a harsh reminder to be diligent about code coverage. Don't execute a line of code on orbit that hasn't been executed on the ground beforehand!

You're already placing the blame on software as opposed to a hardware issue. What's your rationale?

Quote from: Targeteer on 03/01/2013 03:11 pm
From (NASA TV) update, issue may be related to change of burn schedules due to accelerated docking time.

I don't know why such a conclusion was announced, but it seems more possible of a software problem to me...

I don't think that's what they actually said.

They said the inverse, that the issue may cause a change in the burn schedules. That seems likely, since the first burn was supposed to be 50 minutes from now.

Chris-A · « **Reply #196 on:** 03/01/2013 03:43 pm »

I downloaded the HD/720 livestream feed, good thing I did, and I created a gif of Dragon separation.

Nickolai · « **Reply #197 on:** 03/01/2013 03:47 pm »

Quote from: Chris-A on 03/01/2013 03:43 pm

I downloaded the HD/720 livestream feed, good thing I did, and I created a gif of Dragon separation.

Thanks for that. I love how it looks like it's snowing in space

Anyone know what that is? Maybe ice that had formed on the ground being shaken off?

Elmar Moelzer · « **Reply #198 on:** 03/01/2013 03:50 pm »

Quote from: Nickolai on 03/01/2013 03:47 pm

Thanks for that. I love how it looks like it's snowing in space Anyone know what that is? Maybe ice that had formed on the ground being shaken off?

Thats what I thought too.

Star One · « **Reply #199 on:** 03/01/2013 03:50 pm »

Playing devils advocate here, you could say there is nothing like some flight experience to work the kinks out of the systems.

It will put the manned plans of Space X in a positive position compared to their rivals as they will have been able to work a lot of these out without risking any lives, even allowing for the changes in the manned version of Dragon.