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

Offline Lars-J

  • Senior Member
  • *****
  • Posts: 4028
  • California
  • Liked: 3322
  • Likes Given: 2083
Re: SpaceX Manifest Table Formatting Discussion
« Reply #80 on: 02/25/2018 03:43 AM »
This formatting discussion is interesting and all, but c'mon... This is so .. 1994? We are not limited to 80 chars width, and welcome to the world of HTML and styled tables, everyone!  8)

(And the site's markup language even has table support)
« Last Edit: 02/25/2018 06:38 PM by Lars-J »

Online Semmel

  • Full Member
  • ****
  • Posts: 1353
  • Germany
  • Liked: 1113
  • Likes Given: 3018
Re: SpaceX Manifest Table Formatting Discussion
« Reply #81 on: 02/25/2018 01:37 PM »
This formatting discussion is interesting and all, but c'mon... This is so .. 1994? We are bot limited to 80 chars width, and welcome to the world of HTML and styled tables, everyone!  8)

(And the site's markup language even has table support)

well, you know.. if you go beyond 80 characters, you cant put it on punch cards!


Online gongora

  • Global Moderator
  • Senior Member
  • *****
  • Posts: 3245
  • US
  • Liked: 2628
  • Likes Given: 1576
Re: SpaceX Manifest Table Formatting Discussion
« Reply #82 on: 02/25/2018 02:06 PM »
This formatting discussion is interesting and all, but c'mon... This is so .. 1994? We are bot limited to 80 chars width, and welcome to the world of HTML and styled tables, everyone!  8)

(And the site's markup language even has table support)

We're not limited to a specific width but I'm strongly in favor of keeping it at one row per mission in this table. The forum has limited table support (which we are using), the styling options are very limited.

Offline dglow

  • Full Member
  • ****
  • Posts: 813
  • Liked: 637
  • Likes Given: 1536
Re: SpaceX Manifest Table Formatting Discussion
« Reply #83 on: 04/13/2018 10:11 PM »
One great addition would be the version/block of each F9/FH core. Could that be squeezed into this format?

Perhaps something like this:

       Local        LV  CoreRet- .                             .    Mass   .     Mis-
Est. Date,  Time/UTC.   S/N  Blockurn  Payload(s)                    Orb  (kg)   Site sion
------------------- --- ---------  ---  ----------------------------  ---  -----  -----  ----
2018-01-07*2000/-5F91043.1    4LZumaLEO?C-40(48)
2018-01-31  1625/-5F91032.2    3XGovSat-1 (SES-16)GTO4230C-4049
2018-02-06  1545/-5HRNR*  232LSLFH Demo/Tesla RoadsterESC~1.2kC-39A(50)
2018-02-22  0617/-8F91038.2    3XPAZ & Microsat 2a/2bSSO2.2k+V-4E51
2018-03-06  0033/-5F91044       4XHispasat 1F (30W-6)GTO6092C-4052
2018-03-30  0714/-7F91041.2    4XIridium NEXT (Flight 5)PLR9600V-4E53
2018-04-02  1630/-4F91039.2    4XCRS SpX-14LEO~10kC-4054
------------------- --- ---------  ---  ----------------------------  ---  -----  ----- ----
2018-04-16  1832/-4F91045       4?NASA (TESS)HEO325C-4055
2018-05-04F91046       5SBangabandhu-1GTO3.7kC-39A56
2018-05F9R             ?X?SES-12GTO5300C.
« Last Edit: 04/14/2018 05:25 AM by dglow »

Offline deruch

  • Senior Member
  • *****
  • Posts: 2185
  • California
  • Liked: 1691
  • Likes Given: 3396
Re: SpaceX Manifest Table Formatting Discussion
« Reply #84 on: 04/14/2018 06:25 AM »
One great addition would be the version/block of each F9/FH core. Could that be squeezed into this format?

       Local        LV  CoreRet- .                             .    Mass   .     Mis-
Est. Date,  Time/UTC.   S/N  Blockurn  Payload(s)                    Orb  (kg)   Site sion
------------------- --- ---------  ---  ----------------------------  ---  -----  -----  ----
2018-05-04F91046       5SBangabandhu-1GTO3.7kC-39A56

Yeah, but then for Banghabandu-1 and future missions do we list them as Block 5 or Version 7?
Shouldn't reality posts be in "Advanced concepts"?  --Nomadd

Offline Lars-J

  • Senior Member
  • *****
  • Posts: 4028
  • California
  • Liked: 3322
  • Likes Given: 2083
Re: SpaceX Manifest Table Formatting Discussion
« Reply #85 on: 04/14/2018 06:55 AM »
One great addition would be the version/block of each F9/FH core. Could that be squeezed into this format?

       Local        LV  CoreRet- .                             .    Mass   .     Mis-
Est. Date,  Time/UTC.   S/N  Blockurn  Payload(s)                    Orb  (kg)   Site sion
------------------- --- ---------  ---  ----------------------------  ---  -----  -----  ----
2018-05-04F91046    5SBangabandhu-1GTO3.7kC-39A56

Yeah, but then for Banghabandu-1 and future missions do we list them as Block 5 or Version 7?

Itís all going to be block 5 going forward soon enough, so why bother?

Offline groknull

  • Member
  • Posts: 20
  • U.S. West Coast
  • Liked: 22
  • Likes Given: 89
Re: SpaceX Manifest Table Formatting Discussion
« Reply #86 on: 04/14/2018 06:40 PM »
One great addition would be the version/block of each F9/FH core. Could that be squeezed into this format?

Perhaps something like this:

       Local        LV  CoreRet- .                             .    Mass   .     Mis-
Est. Date,  Time/UTC.   S/N  Blockurn  Payload(s)                    Orb  (kg)   Site sion
------------------- --- ---------  ---  ----------------------------  ---  -----  -----  ----
2018-01-07*2000/-5F91043.1    4LZumaLEO?C-40(48)
2018-01-31  1625/-5F91032.2    3XGovSat-1 (SES-16)GTO4230C-4049
2018-02-06  1545/-5HRNR*  232LSLFH Demo/Tesla RoadsterESC~1.2kC-39A(50)

Strictly speaking, block number is a subtype of the launch vehicle type.
In much the same way that passenger aircraft types are condensed in flight listings (e.g. Boeing 737-300 => B733), LV block number could be appended to the LV column info; F90, F93, F94, H232, H555 etc.:

       Local        LV  CoreRet- .                             .    Mass   .     Mis-
Est. Date,  Time/UTC.   S/Nurn  Payload(s)                    Orb  (kg)   Site sion
------------------- --- ---------  ---  ----------------------------  ---  -----  -----  ----
2018-01-07*2000/-5F941043.1  LZumaLEO?C-40(48)
2018-01-31  1625/-5F931032.2  XGovSat-1 (SES-16)GTO4230C-4049
2018-02-06  1545/-5H232RNR*  LSLFH Demo/Tesla RoadsterESC~1.2kC-39A(50)

That said, block number is not an independent value.  It can be inferred from the core number.  A separate table (core number => block number / version number) could be available to those of us more obsessed with this level of detail.  No changes would be required to the existing manifest table.

Similarly, the core number in the existing manifest table could be a link to detailed information specific to that core number - block number / version number, build date, flight list, upgrades, trivia, final disposition, etc.

Online gongora

  • Global Moderator
  • Senior Member
  • *****
  • Posts: 3245
  • US
  • Liked: 2628
  • Likes Given: 1576
Re: SpaceX Manifest Table Formatting Discussion
« Reply #87 on: 04/14/2018 07:24 PM »
I think a separate table with more detail would be better, maybe in the Launch Log thread  (or just refer to the table in the r/spacex wiki).  You also need F9 Version in addition to Block (it would end up like F9 1.0, F9 1.2.4).

Offline Formica

  • Rocket Boi
  • Member
  • Posts: 67
  • Richmond, CA
  • Liked: 61
  • Likes Given: 425
Re: SpaceX Manifest Table Formatting Discussion
« Reply #88 on: 04/14/2018 07:32 PM »
That said, block number is not an independent value.  It can be inferred from the core number.  A separate table (core number => block number / version number) could be available to those of us more obsessed with this level of detail.  No changes would be required to the existing manifest table.

Similarly, the core number in the existing manifest table could be a link to detailed information specific to that core number - block number / version number, build date, flight list, upgrades, trivia, final disposition, etc.

I tend to agree. The table is dense enough already. I've wanted to see the block numbers in there too, but it would probably be more appropriate to have a separate core tracking thread, or to refer to other community resources such as the r/SpaceX wiki core page. And, as is mentioned, with the advent of block 5, block number may become moot over the course of 2018.
I'm just a space fan, please correct me if I'm wrong!

Offline IanThePineapple

Re: SpaceX Manifest Table Formatting Discussion
« Reply #89 on: 04/14/2018 07:39 PM »
I think a separate table with more detail would be better, maybe in the Launch Log thread  (or just refer to the table in the r/spacex wiki).  You also need F9 Version in addition to Block (it would end up like F9 1.0, F9 1.2.4).

I agree, I think a "Core encyclopedia" chart would be great, similar to the /r/SpaceX one but in the manifest format.

Online gongora

  • Global Moderator
  • Senior Member
  • *****
  • Posts: 3245
  • US
  • Liked: 2628
  • Likes Given: 1576
Re: SpaceX Manifest Table Formatting Discussion
« Reply #90 on: 04/14/2018 07:57 PM »
Someone did start a core reuse tracking thread on the public side (https://forum.nasaspaceflight.com/index.php?topic=45247.0), maybe that could be used, or Cartman could add that info in the Launch Log.


Tags: