Author Topic: SpaceX Falcon 9 v1.1 CRS-3 Splashdown Video Repair Task Thread  (Read 958319 times)

Offline MTom

  • Full Member
  • ***
  • Posts: 378
  • EU / Hungary
  • Liked: 107
  • Likes Given: 435
Re: SpaceX Falcon 9 v1.1 CRS-3 Splashdown Video Repair Task Thread
« Reply #1420 on: 06/06/2014 08:00 PM »
Yes tshirts

And maybe a sponsoring 1 year L2 membership for the contributors?
This would be a 2in1 present - also for the big contribution of this site.
« Last Edit: 06/06/2014 08:01 PM by MTom »

Offline Chris Bergin

Yes tshirts

And maybe a sponsoring 1 year L2 membership for the contributors?
This would be a 2in1 present - also for the big contribution of this site.


I've been gradually going through the main people on here and giving them a L2 membership for their work. A few are already L2 members, so I'll sort out something for them. A few I've yet to sort out, per the list I've just seen.


Offline Chris Bergin

This is the list I've been sent.

arnezami   Primary coordinator& strategist
IainCole   Online editor, YouTube feed
michaelni   ffmpg enhancements
Shanuson   TS header fix, datasteam analysis
Wronkiew   YouTube feed, clock
SwissCheese   MMB
Princess   TS header fix
Quialiss   MMB
mvpel   TS header fix
Saliva_Sweet   MMB
Lourens   MMB, strategy / communications
mhenderson   MMB
Mlindner   
ajmartin   Error stats
theshadow27   error analysis
untribium   MMB
Swatch   
moralec   General commentary
grythumn   MMB

Offline MTom

  • Full Member
  • ***
  • Posts: 378
  • EU / Hungary
  • Liked: 107
  • Likes Given: 435
Re: SpaceX Falcon 9 v1.1 CRS-3 Splashdown Video Repair Task Thread
« Reply #1423 on: 06/06/2014 08:22 PM »
Yes tshirts

And maybe a sponsoring 1 year L2 membership for the contributors?
This would be a 2in1 present - also for the big contribution of this site.


I've been gradually going through the main people on here and giving them a L2 membership for their work. A few are already L2 members, so I'll sort out something for them. A few I've yet to sort out, per the list I've just seen.

Oh, my bad english. I wanted say that NSF should be sponsored so you can give the L2 membership.  ;)
« Last Edit: 06/06/2014 08:30 PM by MTom »

Offline sittingduck

  • Member
  • Posts: 99
  • Liked: 84
  • Likes Given: 121
Re: SpaceX Falcon 9 v1.1 CRS-3 Splashdown Video Repair Task Thread
« Reply #1424 on: 06/06/2014 08:35 PM »
I've been following this thread since page one but it updates so fast that I'm not sure if this has been asked before: I notice in one of the two original videos that SpaceX released there is a very clear shot of the cloud deck while the stage rotates.  The video is also ~8 seconds longer.  What's happened to the clear footage of the clouds?
« Last Edit: 06/06/2014 08:39 PM by sittingduck »

Offline arnezami

  • Full Member
  • **
  • Posts: 284
  • Liked: 262
  • Likes Given: 346
Re: SpaceX Falcon 9 v1.1 CRS-3 Splashdown Video Repair Task Thread
« Reply #1425 on: 06/06/2014 08:40 PM »
This is the list I've been sent.

arnezami   Primary coordinator& strategist
IainCole   Online editor, YouTube feed
michaelni   ffmpg enhancements
Shanuson   TS header fix, datasteam analysis
Wronkiew   YouTube feed, clock
SwissCheese   MMB
Princess   TS header fix
Quialiss   MMB
mvpel   TS header fix
Saliva_Sweet   MMB
Lourens   MMB, strategy / communications
mhenderson   MMB
Mlindner   
ajmartin   Error stats
theshadow27   error analysis
untribium   MMB
Swatch   
moralec   General commentary
grythumn   MMB

Pretty good list. :)

I personally like to see Jakusb (the "dirt-master") on the list too. Because he gave us the list of dirt spots on the camera which allowed others to align blocks in the top part of the frames. But considering having only 15 spots its a good list.

Offline SwissCheese

  • Full Member
  • *
  • Posts: 165
  • Liked: 250
  • Likes Given: 94
Re: SpaceX Falcon 9 v1.1 CRS-3 Splashdown Video Repair Task Thread
« Reply #1426 on: 06/06/2014 08:47 PM »
I feel like I'm going a bit mad.  Could someone who understands the data structures help out a bit here? The relevant MMBs are at the bottom in case the ones in the wiki change, if you need to see what's going on.   

Part 13, frame 242.  Used to be: 
12:12:-3,19:20:43995,43:29:-3

SwissCheese pulled out a bit more data from it, but for simplicity's sake lets say the new 242 is:
12:12:-3,19:20:43995

Just removing the null block at the end of the frame.

This causes absolutely no changes to frame 243 or 244.

Then we get to 245.  With the old frame 242, it did not play* without the mmb 43:29:-3 applied to it.
With the new 242, it doesn't play unless you get rid of that 43:29:-3.

So we have old version with two frames ending with 43:29:-3, and the new version that is identical except to remove those two commands

The old version, all the frames play out normally. 
The new version, 247, 249, 250, 252, 253 and 254 all fail to play. 

This is problematic, and extremely confusing.  I've noticed an occasional frame that wouldn't display before, but this is the first time I've seen half a sequence go bad because of changes frames earlier in the set.  Something very weird is going on here!  Help! 



*By 'not play' I mean that when the editor hits it, the whole frame blurs very slightly and none of the changes in the p frame are applied. 


'old'
FRAME0:0:0:-1, 29:11:56945, 0:12:58604:0:48:0:0:0:0, 17:12:60055:0:0:-10:5:0:0, 18:12:60234:0:0:5:-5:0:0, 0:13:63030:50:0:0:0:0:0, 18:13:64546:15:0:0:-5:0:0, 19:13:64773:-2:1:0:0:0:0:1, 23:13:65229:0:5:10:0:0:0, 26:13:65548:9:0:0:0:0:0, 29:13:65871:15:0:0:0:0:0, 2:14:67729:0:0:-5:0:0:0, 11:14:68538:0:0:0:0:0:-5, 18:14:69331:0:0:0:20:0:0, 28:15:75458:20:0:0:0:0:0, 28:16:81012:0:0:0:-40:0:0, 31:18:90278:30:0:0:0:0:0, 7:29:-1, 8:29:139153=FRAME1:12:12:-3, 19:20:43995, 43:29:-3=FRAME4:43:29:-3=FRAME5:29:5:-3, 43:9:47279, 24:13:-3, 32:14:77707, 21:22:109507, 1:23:111455=FRAME6:28:10:-3, 42:11:55212, 16:14:66147, 43:29:-3=FRAME7:33:5:25539, 6:7:-3, 4:21:92786, 8:28:116815=FRAME8:9:23:-3=FRAME9:7:5:6416, 41:5:-3, 0:12:13030, 43:29:-3=FRAME10:27:14:-3, 43:15:35848=FRAME11:30:1:3471, 35:11:-3, 38:11:23458, 19:15:-3, 39:19:38646, 10:21:-3, 11:21:40210, 43:29:-3=FRAME12:32:0:3533, 24:4:-3, 25:4:-3, 31:4:21824, 34:8:-3, 2:9:41767, 40:9:-3, 43:11:46658, 32:14:79617, 0:15:-3, 16:15:72454, 33:16:-3, 39:16:79667, 6:17:-3, 24:17:82941, 36:19:92064, 5:23:-3=FRAME13:29:1:-3, 0:12:179561, 39:17:-3=FRAME14:32:0:-3, 23:3:79913, 18:5:-3, 11:7:144389, 28:9:-3, 41:11:179414, 40:17:-3=FRAME15:35:1:-3, 33:8:15768, 11:16:-3, 36:16:31633, 27:17:-3, 0:18:33492, 32:19:35931, 43:29:-3=FRAME16:12:29:-3=FRAME17:19:3:-3=FRAME18:37:2:13241, 3:4:18430, 27:9:-3, 41:21:97555, 6:28:116909, 43:29:-3=FRAME19:39:23:-3, 43:23:39539, 13:29:-3



'new' 
FRAME0:0:0:-1, 29:11:56945, 0:12:58604:0:48:0:0:0:0, 17:12:60055:0:0:-10:5:0:0, 18:12:60234:0:0:5:-5:0:0, 0:13:63030:50:0:0:0:0:0, 18:13:64546:15:0:0:-5:0:0, 19:13:64773:-2:1:0:0:0:0:1, 23:13:65229:0:5:10:0:0:0, 26:13:65548:9:0:0:0:0:0, 29:13:65871:15:0:0:0:0:0, 2:14:67729:0:0:-5:0:0:0, 11:14:68538:0:0:0:0:0:-5, 18:14:69331:0:0:0:20:0:0, 28:15:75458:20:0:0:0:0:0, 28:16:81012:0:0:0:-40:0:0, 31:18:90278:30:0:0:0:0:0, 7:29:-1, 8:29:139153=FRAME1:12:12:-3, 19:20:43995=FRAME5:29:5:-3, 43:9:47279, 24:13:-3, 32:14:77707, 21:22:109507, 1:23:111455=FRAME6:28:10:-3, 42:11:55212, 16:14:66147, 43:29:-3=FRAME7:33:5:25539, 6:7:-3, 4:21:92786, 8:28:116815=FRAME8:9:23:-3=FRAME9:7:5:6416, 41:5:-3, 0:12:13030, 43:29:-3=FRAME10:27:14:-3, 43:15:35848=FRAME11:30:1:3471, 35:11:-3, 38:11:23458, 19:15:-3, 39:19:38646, 10:21:-3, 11:21:40210, 43:29:-3=FRAME12:32:0:3533, 24:4:-3, 25:4:-3, 31:4:21824, 34:8:-3, 2:9:41767, 40:9:-3, 43:11:46658, 32:14:79617, 0:15:-3, 16:15:72454, 33:16:-3, 39:16:79667, 6:17:-3, 24:17:82941, 36:19:92064, 5:23:-3=FRAME13:29:1:-3, 0:12:179561, 39:17:-3=FRAME14:32:0:-3, 23:3:79913, 18:5:-3, 11:7:144389, 28:9:-3, 41:11:179414, 40:17:-3=FRAME15:35:1:-3, 33:8:15768, 11:16:-3, 36:16:31633, 27:17:-3, 0:18:33492, 32:19:35931, 43:29:-3=FRAME16:12:29:-3=FRAME17:19:3:-3=FRAME18:37:2:13241, 3:4:18430, 27:9:-3, 41:21:97555, 6:28:116909, 43:29:-3=FRAME19:39:23:-3, 43:23:39539, 13:29:-3

You need to look at the log, at the end of the frame: for some reason, sometimes when the end of the frame is not reached at position 43:29 the frame is not used. If this is the case, the log also writes the number of bits remaining (positive or negative) to the end of frame position. Sometimes you can simply put 43:29:-3 to solve this, but in other cases the exact position is needed. The problem is that it is quite difficult to read the log in the online editor (that's the only remaining thing I do in my local build).

In another news, my laptop "drank" a cup of tea on thursday; after a 24 hour drying it seems to have survived. Had some keyboard issues first but now everything seems OK  ;D

Offline Quialiss

  • Member
  • Posts: 75
  • Liked: 82
  • Likes Given: 29
Re: SpaceX Falcon 9 v1.1 CRS-3 Splashdown Video Repair Task Thread
« Reply #1427 on: 06/06/2014 08:48 PM »
I've been following this thread since page one but it updates so fast that I'm not sure if this has been asked before: I notice in one of the two original videos that SpaceX released there is a very clear shot of the cloud deck while the stage rotates.  The video is also ~8 seconds longer.  What's happened to the clear footage of the clouds?

IIRC, it was mentioned by a member of SpaceX that they only gave out the raw ts for the part they most wanted recovered.  What we have starts just a few seconds before the stage leaves the clouds, to a few seconds after the stage touched down on the water, so it's cropped on both ends.

Watching the raw video again is interesting.  There are a handful of undamaged p frames in parts 13-14, I recognize them in the raw video, long before the tipping motion. 

Offline lgjy98d

  • Member
  • Posts: 10
  • Liked: 6
  • Likes Given: 0
Re: SpaceX Falcon 9 v1.1 CRS-3 Splashdown Video Repair Task Thread
« Reply #1428 on: 06/06/2014 09:16 PM »
There has been an effort to let people suggest improvements (in case there are doubts, it one is too shy to replace someones work with own variant). This is why we have suggest form in Online editor now. When the form is processed the moderators are emailed about the suggestion. See the sample notification e-mail attached.

We intend to improve the notification logic to notify only frame contributors not all moderators. Thus ones who contributed to frame will be notified only. You are welcome to register as contributors and frame moderators at: https://docs.google.com/forms/d/1HoijPXQJsR8nHkS54UqMJkoNA7h24tF6DCIaeN_PhAE

Huge cudos to JohnKiel for his spxi.php script that enables these suggestion previews in notification emails and video frames in Google Spreadsheets.

Offline moralec

Hahahha thanks for the "General commentary" title Chris hahahha! ;)

Offline Chris Bergin

Hahahha thanks for the "General commentary" title Chris hahahha! ;)

Not my list! ;D All I did was copy and paste it into the thread :)
« Last Edit: 06/06/2014 09:43 PM by Chris Bergin »

Offline moralec

Hahahha thanks for the "General commentary" title Chris hahahha! ;)

Not my list! ;D All I did was copy and paste it into the thread :)

Haha I found it hilarious. I'm gonna make a business card with that. 

Offline catdlr

  • Member
  • Senior Member
  • *****
  • Posts: 5504
  • Viewed launches since the Redstones
  • Marina del Rey, California, USA
  • Liked: 2120
  • Likes Given: 1482
Re: SpaceX Falcon 9 v1.1 CRS-3 Splashdown Video Repair Task Thread
« Reply #1432 on: 06/06/2014 10:26 PM »
Hahahha thanks for the "General commentary" title Chris hahahha! ;)

Not my list! ;D All I did was copy and paste it into the thread :)

Haha I found it hilarious. I'm gonna make a business card with that. 

and this would be your updated title on NSF...  ;)
« Last Edit: 06/06/2014 10:27 PM by catdlr »
Tony De La Rosa

Offline moralec

Hahahha thanks for the "General commentary" title Chris hahahha! ;)

Not my list! ;D All I did was copy and paste it into the thread :)

Haha I found it hilarious. I'm gonna make a business card with that. 

and this would be your updated title on NSF...  ;)


OMG! Hahahaha

Offline deruch

  • Senior Member
  • *****
  • Posts: 2305
  • California
  • Liked: 1840
  • Likes Given: 3993
Re: SpaceX Falcon 9 v1.1 CRS-3 Splashdown Video Repair Task Thread
« Reply #1434 on: 06/06/2014 11:10 PM »
Hahahha thanks for the "General commentary" title Chris hahahha! ;)

Not my list! ;D All I did was copy and paste it into the thread :)

Haha I found it hilarious. I'm gonna make a business card with that.

"General Commentary" is a job description.  But, on business cards, you're supposed to list your job title.  Commentary General, (Res.) is a job title.  :)
Shouldn't reality posts be in "Advanced concepts"?  --Nomadd

Offline deruch

  • Senior Member
  • *****
  • Posts: 2305
  • California
  • Liked: 1840
  • Likes Given: 3993
Re: SpaceX Falcon 9 v1.1 CRS-3 Splashdown Video Repair Task Thread
« Reply #1435 on: 06/06/2014 11:24 PM »
This is the list I've been sent.

arnezami   Primary coordinator& strategist
IainCole   Online editor, YouTube feed
michaelni   ffmpg enhancements
Shanuson   TS header fix, datasteam analysis
Wronkiew   YouTube feed, clock
SwissCheese   MMB
Princess   TS header fix
Quialiss   MMB
mvpel   TS header fix
Saliva_Sweet   MMB
Lourens   MMB, strategy / communications
mhenderson   MMB
Mlindner   
ajmartin   Error stats
theshadow27   error analysis
untribium   MMB
Swatch   
moralec   General commentary
grythumn   MMB

That looks like a pretty good list.  I recently went back through the thread to write up something that acknowledged each of the people that contributed to the TS repair, which I then planned to upload to the wiki.  There were only 3 people that made what I thought were considerable contributions that didn't make the quoted list.  Jared (aka reddit user /u/sharebrained, I don't know if he's a NSF member) for the original coerced.ts, @Adaptation for .ts alignment and search tool, and @gospacex for packet fixing tools and analysis/meta-analysis.  With a list limited to 15 people there will, based solely on the size of this project, be deserving people left off.  I don't feel qualified to assert that one of these three is worthy of bumping someone off Chris' list.  Plus I think it got a very good mix of people involved with the various sub-parts of the project, and I wouldn't bump any of the TS superstars that made the list.   But if the list were expanded at all, these three deserve consideration to be the first added. 

edited for clarity
« Last Edit: 06/06/2014 11:33 PM by deruch »
Shouldn't reality posts be in "Advanced concepts"?  --Nomadd

Offline Shanuson

  • Full Member
  • **
  • Posts: 292
  • Liked: 197
  • Likes Given: 595
Re: SpaceX Falcon 9 v1.1 CRS-3 Splashdown Video Repair Task Thread
« Reply #1436 on: 06/06/2014 11:57 PM »
<snip>

You need to look at the log, at the end of the frame: for some reason, sometimes when the end of the frame is not reached at position 43:29 the frame is not used. If this is the case, the log also writes the number of bits remaining (positive or negative) to the end of frame position. Sometimes you can simply put 43:29:-3 to solve this, but in other cases the exact position is needed. The problem is that it is quite difficult to read the log in the online editor (that's the only remaining thing I do in my local build).
<snip>

It could be that this is one if the effects of a wrong AF length of the last packet. I think more and more that we should have fixed that before releasing/adding the "final" ts file.

Well as long as there is a way to work around that problem, it's OK I think.

Cheers,
Shanuson

Offline lgjy98d

  • Member
  • Posts: 10
  • Liked: 6
  • Likes Given: 0
Re: SpaceX Falcon 9 v1.1 CRS-3 Splashdown Video Repair Task Thread
« Reply #1437 on: 06/07/2014 12:08 AM »
Apparently the Wikispaces API doesn't allow file uploads.  >:(

The auto-generated MMBs are uploaded here, in case you need to track down a bug:

http://adama.nocdirect.com/~wronkiew/spx_crs3/mmbs/

IainCole, can you change the youtube uploader to grab http://adama.nocdirect.com/~wronkiew/spx_crs3/landing_clockfix_3hr.mp4 ? I can then move the trigger to the 3hr script.

Alternatively you can just grab the CSV from https://docs.google.com/spreadsheets/d/1xEtLQy3tvjv3cyz_wMQssuSFwHYVbMQ5-FdSz-uCsKA/export?gid=0&format=csv - this CSV is being autopublished by Google with something like 10 minute delay of the actual edit of the any of the parts' spreadseets.

Offline cmobile

  • Member
  • Posts: 2
  • Liked: 6
  • Likes Given: 0
Re: SpaceX Falcon 9 v1.1 CRS-3 Splashdown Video Repair Task Thread
« Reply #1438 on: 06/07/2014 12:28 AM »
This is the list I've been sent.

arnezami   Primary coordinator& strategist
IainCole   Online editor, YouTube feed
michaelni   ffmpg enhancements
Shanuson   TS header fix, datasteam analysis
Wronkiew   YouTube feed, clock
SwissCheese   MMB
Princess   TS header fix
Quialiss   MMB
mvpel   TS header fix
Saliva_Sweet   MMB
Lourens   MMB, strategy / communications
mhenderson   MMB
Mlindner   
ajmartin   Error stats
theshadow27   error analysis
untribium   MMB
Swatch   
moralec   General commentary
grythumn   MMB

That looks like a pretty good list.  I recently went back through the thread to write up something that acknowledged each of the people that contributed to the TS repair, which I then planned to upload to the wiki.  There were only 3 people that made what I thought were considerable contributions that didn't make the quoted list.  Jared (aka reddit user /u/sharebrained, I don't know if he's a NSF member) for the original coerced.ts, @Adaptation for .ts alignment and search tool, and @gospacex for packet fixing tools and analysis/meta-analysis.  With a list limited to 15 people there will, based solely on the size of this project, be deserving people left off.  I don't feel qualified to assert that one of these three is worthy of bumping someone off Chris' list.  Plus I think it got a very good mix of people involved with the various sub-parts of the project, and I wouldn't bump any of the TS superstars that made the list.   But if the list were expanded at all, these three deserve consideration to be the first added. 

edited for clarity

Just submit everyone who made a significant contribution even if it's more than 15.  I doubt they're going to begrudge a few T-shirts.

Offline Untribium

  • Member
  • Posts: 32
  • Switzerland
  • Liked: 32
  • Likes Given: 78
Re: SpaceX Falcon 9 v1.1 CRS-3 Splashdown Video Repair Task Thread
« Reply #1439 on: 06/07/2014 01:22 AM »
-snip-
Just submit everyone who made a significant contribution even if it's more than 15.  I doubt they're going to begrudge a few T-shirts.

Yeah I agree, mostly because I'm #16 on the list ;D No but seriously, it was (and is) a group effort, so it would be kinda sad if we had to make a cut somewhere...

Back to the actual job :) I haven't been able to spend much time recently, that may change :) I really want go through a single i-frame and try to give meaning to every single bit using the specification and the VLC codes. May not be feasible, we'll see :))
Also, I saw someone fixed the dc stuff for i-frame 4 (61). Quialiss, I suspect that was you :) Great work, row 10 was driving nuts :)) There's also one more change that morningdew76 suggested a long time ago, but somehow it wasn't  picked up by anybody...I put it back in, still works nicely, but with all the changes that have happened to the wiki (love the google spreadsheets!), I'm not quite sure what needs to be updated manually and what is done automatically. I'm thinking Wiki frames part 4 and the spreadsheet, is that correct?

Anybody in the Florida area want to get together for the OrbComm launch? I am working a temporary / long term assignment in Miami and considering driving to KSC for the OrbComm OG2 launch next Thursday (backup launch date is Friday).

I'd love that, but unfortunately I'm not exactly in the area :'( ;)

Tags: