Author Topic: SpaceX Manifest Table Formatting Discussion  (Read 5702 times)

Offline Jet Black

Re: SpaceX Manifest Table Formatting Discussion
« Reply #20 on: 06/26/2017 08:28 AM »
If you're still wrapping lines on some browsers, you could save a couple of characters by getting rid of the 20-- on each year. I appreciate this means the table will need revisiting in 83 years
For a successful technology, reality must take precedence over public relations, for Nature cannot be fooled. -- Richard Feynman

Offline vanoord

  • Full Member
  • ****
  • Posts: 447
  • Liked: 271
  • Likes Given: 30
Re: SpaceX Manifest Table Formatting Discussion
« Reply #21 on: 06/26/2017 10:06 AM »
Since the manifest table is a table and all, I wondered how it would render on screens large and small if the manifest table were actually posted as a [table].  So, I reworked it (including learning things like [td][hr][/td] won't even preview and plain [hr] between rows actually renders but splits the table into multiple tables, breaking the column alignment).

This is a copy of the current first post, coded as a table.  (I put just the LV column in bold, as I thought as a rendered table it needed something to help visually break up/anchor the line.)  Obviously reposted unquoted for "test as you post" fidelity.  Since the preview is not the same width as a post in thread, and since I can't see what it looks like on my phone without it being posted, here goes nothing.

Any comments, questions, or rapid mod edits/deletion if rendering this post messes up the thread display?  (Hey, it looked great in preview. ;D)

Looks a lot cleaner and easier to read than the font in the original table - which I think was down to the 'tt' tag?

Admittedly I'm using it on a big screen, but I don't think you're ever going to find a definitive way of presenting that sort of info in a mobile-friendly way.

(We have the same problem with our company website and we've taken the decision not to bother trying to make tables mobile-friendly).

One *very* minor comment would be to use 'FH' for the launch vehicle rather than 'H', per SpaceX usage.
« Last Edit: 06/26/2017 10:08 AM by vanoord »

Offline AC in NC

  • Full Member
  • *
  • Posts: 164
  • Raleigh NC
  • Liked: 124
  • Likes Given: 126
Re: SpaceX Manifest Table Formatting Discussion
« Reply #22 on: 06/26/2017 01:55 PM »
Thoughts:

1)  I find myself really wanting to see K-39A instead of C-39A.  Tiny thing but a nod to the history.
2)  Love monospace everywhere except prose bodies.  Makes the text alignment after Edit History dates read more comfortably.
3)  Agree with utilizing the 3 characters available for Return

Otherwise, overall format change has been outstanding.
« Last Edit: 06/26/2017 04:35 PM by AC in NC »

Offline flyright

  • Member
  • Posts: 82
  • Denver, Colorado
  • Liked: 84
  • Likes Given: 111
Re: SpaceX Manifest Table Formatting Discussion
« Reply #23 on: 06/26/2017 05:21 PM »
Regarding the 3 characters vs 1 character for return: I think it would be good to stick with a single character per core. Need to be able to track landings of all 3 FH cores individually.

Offline toren

  • Member
  • Posts: 24
  • Idaho, USA
  • Liked: 29
  • Likes Given: 114
Re: SpaceX Manifest Table Formatting Discussion
« Reply #24 on: 06/26/2017 06:59 PM »
A minor nitpick:  It would be nice to have the original flight of a later re-used core updated so that the reuse was evident, e.g., 1029.1

Online Comga

  • Senior Member
  • *****
  • Posts: 3884
  • Liked: 1211
  • Likes Given: 1037
Re: SpaceX Manifest Table Formatting Discussion
« Reply #25 on: 06/30/2017 09:44 PM »
Another nit to pick:
The list of past launches is growing.  The old policy was to trim past launches after a year on the list.
However, this is such a nice display I would like to see it retained.
How about putting it at the bottom of the list?
Maybe in reverse order, with most recent on top?
It would be a shame to lose such a nice, compact record. 
(I was just noticing that the last landing failure was over a year ago and they have landed all of the last nine attempts, and 12 of the last 13 if you go back an additional 10 weeks.)


2017-06-25  1325/-7 F9 1036    S Iridium NEXT (Flight 2) PLR 9600 V-4E 38
2017-06-23  1510/-4 F9 1029.2  S BulgariaSat-1             GTO 3669 C-39A 37
2017-06-03  1707/-4 F9 1035    L CRS 11                    LEO ~9k C-39A 36
2017-05-15  1921/-4 F9 1034    X Inmarsat 5 F4             GTO 6086 C-39A 35
2017-05-01  0715/-4 F9 1032    L NROL-76                  LEO ? C-39A 34
2017-03-30  1827/-4 F9 1021.2  S SES-10                   GTO 5282 C-39A 33
2017-03-16  0200/-4 F9 1030    X Echostar 23                GTO ~5500 C-39A 32
2017-02-19  0939/-5 F9 1031    L CRS 10                       LEO ~9k C-39A 31
2017-01-14  0954/-8 F9 1029    S Iridium NEXT (Flight 1) PLR 9600 V-4E 30
2016-09-01  0907/-4 F9      N/A AMOS-6(destroyed in pad test) GTO 5500 C-40 29
2016-08-14  0126/-4 F9         S JCSAT-16                        GTO ~4600 C-40 28
2016-07-18  0045/-4 F9         L CRS-9                             LEO ~9k C-40 27
2016-06-15  1029/-4 F9         S Eutelsat 117W B & ABS-2A GTO 4200 C-40 26
2016-05-27  1740/-4 F9 1023    S Thaicom 8                    GTO 3025 C-40 25
2016-05-06  0121/-4 F9 1022    S JCSAT-14                     GTO 4696 C-40 24
2016-04-08  1643/-4 F9 1021    S CRS-8                       LEO ~9k C-40 23
2016-03-04  1835/-5 F9         S SES-9                        GTO 5271 C-40 22
2016-01-17  1042/-8 F9         S Jason-3                  LEO 553 V-4E 21
2015-12-22          F9 1019    L ORBCOMM OG2 Launch 2   LEO 1892 C-40 20
What kind of wastrels would dump a perfectly good booster in the ocean after just one use?

Online gongora

  • Global Moderator
  • Full Member
  • *****
  • Posts: 1776
  • US
  • Liked: 1204
  • Likes Given: 916
Re: SpaceX Manifest Table Formatting Discussion
« Reply #26 on: 06/30/2017 10:19 PM »
The list of past launches is growing.  The old policy was to trim past launches after a year on the list.
However, this is such a nice display I would like to see it retained.
How about putting it at the bottom of the list?

I was thinking about doing that.  I use that list to find the mission threads, so I hate to remove the old ones.

Online Formica

  • Member
  • Posts: 27
  • Liked: 22
  • Likes Given: 181
Re: SpaceX Manifest Table Formatting Discussion
« Reply #27 on: 06/30/2017 11:16 PM »
Thank you for doing this gongora! The manifest is now well laid out and readable on my Android tablet, using Firefox, with the desktop site. I really appreciate the effort.

I would also vote to keep the past launches in the list. Now that it's so well formatted, it really makes an excellent and convenient reference. And it's just such a fun thing to see that list of green grow as the steamroller gets going  :D

Offline smh

  • Member
  • Posts: 19
  • Liked: 3
  • Likes Given: 3
Re: SpaceX Manifest Table Formatting Discussion
« Reply #28 on: 07/01/2017 06:36 PM »
I use that list to find the mission threads, so I hate to remove the old ones.
Maybe even add older missions?

Offline Digitalchromakey

  • Member
  • Posts: 23
  • Phuket
  • Liked: 5
  • Likes Given: 2
Re: SpaceX Manifest Table Formatting Discussion
« Reply #29 on: 07/01/2017 07:20 PM »
Revised format is fine and easy to read W10/Edge on a Laptop with a 14 inch, 1080 HD Display.

Only quibble would be to see the Heavy core numbers in the main table - three rows?

Generally well thought out revisions - thank you.

« Last Edit: 07/01/2017 07:23 PM by Digitalchromakey »

Online gongora

  • Global Moderator
  • Full Member
  • *****
  • Posts: 1776
  • US
  • Liked: 1204
  • Likes Given: 916
Re: SpaceX Manifest Table Formatting Discussion
« Reply #30 on: 07/01/2017 07:28 PM »
Only quibble would be to see the Heavy core numbers in the main table - three rows?

I'll be leaving that information in the footnotes.  I just don't see enough value in adding table rows for that small bit of information.  I know some will disagree with me on that, but I'm sticking with one line per mission.

Offline SLC

  • Member
  • Posts: 83
  • London, UK
  • Liked: 51
  • Likes Given: 414
Re: SpaceX Manifest Table Formatting Discussion
« Reply #31 on: 07/03/2017 09:02 PM »
A minor nitpick:  It would be nice to have the original flight of a later re-used core updated so that the reuse was evident, e.g., 1029.1
I'd vote for this as well.  Apart from that, it's perfect!

Online gongora

  • Global Moderator
  • Full Member
  • *****
  • Posts: 1776
  • US
  • Liked: 1204
  • Likes Given: 916
Re: SpaceX Manifest Table Formatting Discussion
« Reply #32 on: 07/03/2017 09:52 PM »
A minor nitpick:  It would be nice to have the original flight of a later re-used core updated so that the reuse was evident, e.g., 1029.1
I'd vote for this as well.  Apart from that, it's perfect!

I'll look at that next time I mess with the table.

Offline deruch

  • Full Member
  • ****
  • Posts: 1435
  • California
  • Liked: 1110
  • Likes Given: 1508
Re: SpaceX Manifest Table Formatting Discussion
« Reply #33 on: 10/11/2017 07:04 AM »
In the "previous missions" list (second post of the manifest thread), how would you feel about putting in some sort of break between calendar years?  Not too sure how best to do it, but I've demonstrated it with an added dash.  Can't seem to get the table to just recognize an empty row.  Would look like:

       Local        LV  Core   Ret- .                             .    Mass   .     Mis-
Est. Date,  Time/UTC.   S/N    urn  Payload(s)                    Orb  (kg)   Site sion
------------------- --- ------ ---  ----------------------------  ---  -----  -----  ----
2010-06-04  1445/-4F9..Dragon Qual UnitLEO~6kC-401
2010-12-08  1043/-5F9..Dragon C1LEO~8kC-402
-
2012-05-22  0344/-4F9..Dragon C2LEO~8kC-403
2012-10-07*2035/-4F9..CRS-1LEO~8kC-404
-
2013-03-01  1010/-5F9..CRS-2LEO~9kC-405
2013-09-29  0900/-7F9..CassiopePLR500V-4E6
2013-12-03  1741/-5F9..SES-8GTO3183C-407
-
2014-01-06  1706/-5F9..Thaicom 6GTO3016C-408
2014-04-18  1525/-4F9..CRS-3LEO~10kC-409
2014-07-14  1115/-4F9..Orbcomm OG2 Flight 1LEO1-2kC-4010
2014-08-05  0400/-4F9..Asiasat 8GTO4535C-4011
2014-09-07  0100/-4F9..Asiasat 6GTO4428C-4012
2014-09-21  0152/-4F9..CRS-4LEO~10kC-4013
-
2015-01-10  0447/-5F9.SCRS-5LEO~10kC-4014
2015-02-11  1803/-5F9..DSCOVREEO570C-4015
2015-03-01*2250/-5F9..Eutelsat 115WB/ABS 3AGTO4159C-4016
2015-04-14  1610/-4F9.SCRS-6LEO~10kC-4017
2015-04-27  1903/-4F9..TürkmenÄlem 52E/MonacoSATGTO4707C-4018
2015-06-28  1021/-4F9.N/ACRS-7 (failed)LEO~10kC-4019
2015-12-21  2029/-5F91019LORBCOMM OG2 Launch 2LEO1892C-4020
-
2016-01-17  1042/-8F9.SJason-3LEO553V-4E21
2016-03-04  1835/-5F9.SSES-9GTO5271C-4022
2016-04-08  1643/-4F91021.1SCRS-8LEO~10kC-4023
2016-05-06  0121/-4F91022SJCSAT-14GTO4696C-4024
2016-05-27  1740/-4F91023.1SThaicom 8GTO3025C-4025
2016-06-15  1029/-4F9.SEutelsat 117W B & ABS-2AGTO4200C-4026
2016-07-18  0045/-4F9.LCRS-9LEO~10kC-4027
2016-08-14  0126/-4F9.SJCSAT-16GTO~4600C-4028
2016-09-01  0907/-4F9.N/AAMOS-6(destroyed in pad test)GTO5500C-4029
Shouldn't reality posts be in "Advanced concepts"?  --Nomadd

Online gongora

  • Global Moderator
  • Full Member
  • *****
  • Posts: 1776
  • US
  • Liked: 1204
  • Likes Given: 916
Re: SpaceX Manifest Table Formatting Discussion
« Reply #34 on: 10/12/2017 04:49 PM »
In the "previous missions" list (second post of the manifest thread), how would you feel about putting in some sort of break between calendar years?  Not too sure how best to do it, but I've demonstrated it with an added dash.  Can't seem to get the table to just recognize an empty row.  Would look like: ...

This seems ok.  The table parser discards completely empty fields (was that some coder's idea of a joke?).

Tags: