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! (And the site's markup language even has table support)
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
Quote from: dglow on 04/13/2018 10:11 pmOne 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-39A56Yeah, but then for Banghabandu-1 and future missions do we list them as Block 5 or Version 7?
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-40492018-02-06 1545/-5HRNR* 232LSLFH 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.
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).
Minor nit...Some reflown cores did not get their 1st flights upgraded to XXXX.1 status. (mostly the block 5 team; 1045.1 vs 1046)
... do we still consider the FH center core to be a successful landing?
Looks like CRS-17 is now ASDS; also, do we still consider the FH center core to be a successful landing?
Quote from: pb2000 on 04/23/2019 06:30 pmLooks like CRS-17 is now ASDS; also, do we still consider the FH center core to be a successful landing?I would say the landing was successful but recovery was not. The question is what do we want to keep track of.
It's important to track booster loss from all causes, in my view. Until it actually launches again, it's not truly recovered. (ok I kid but yeah, if we can lose them at sea, it's a trackable thing)Adding a whole new column for an edge case seems problematic. New code letter? Asterisk?