Quote from: IainCole on 06/06/2014 07:13 pmYes tshirtsAnd maybe a sponsoring 1 year L2 membership for the contributors?This would be a 2in1 present - also for the big contribution of this site.
Yes tshirts
Quote from: MTom on 06/06/2014 08:00 pmQuote from: IainCole on 06/06/2014 07:13 pmYes tshirtsAnd 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.
This is the list I've been sent.arnezami Primary coordinator& strategistIainCole Online editor, YouTube feedmichaelni ffmpg enhancementsShanuson TS header fix, datasteam analysisWronkiew YouTube feed, clockSwissCheese MMBPrincess TS header fixQuialiss MMBmvpel TS header fixSaliva_Sweet MMBLourens MMB, strategy / communicationsmhenderson MMBMlindner ajmartin Error statstheshadow27 error analysisuntribium MMBSwatch moralec General commentarygrythumn MMB
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:43995Just 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 commandsThe 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
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?
Hahahha thanks for the "General commentary" title Chris hahahha!
Quote from: moralec on 06/06/2014 09:20 pmHahahha thanks for the "General commentary" title Chris hahahha! Not my list! All I did was copy and paste it into the thread
Quote from: Chris Bergin on 06/06/2014 09:42 pmQuote from: moralec on 06/06/2014 09:20 pmHahahha thanks for the "General commentary" title Chris hahahha! Not my list! 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.
Quote from: moralec on 06/06/2014 10:20 pmQuote from: Chris Bergin on 06/06/2014 09:42 pmQuote from: moralec on 06/06/2014 09:20 pmHahahha thanks for the "General commentary" title Chris hahahha! Not my list! 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...
Quote from: Quialiss on 06/06/2014 04:42 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>
<snip>
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.
Quote from: Chris Bergin on 06/06/2014 08:07 pmThis is the list I've been sent.arnezami Primary coordinator& strategistIainCole Online editor, YouTube feedmichaelni ffmpg enhancementsShanuson TS header fix, datasteam analysisWronkiew YouTube feed, clockSwissCheese MMBPrincess TS header fixQuialiss MMBmvpel TS header fixSaliva_Sweet MMBLourens MMB, strategy / communicationsmhenderson MMBMlindner ajmartin Error statstheshadow27 error analysisuntribium MMBSwatch moralec General commentarygrythumn MMBThat 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
-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.
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 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?