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

Offline gongora

  • Global Moderator
  • Senior Member
  • *****
  • Posts: 10183
  • US
  • Liked: 13846
  • Likes Given: 5915
SpaceX Manifest Table Formatting Discussion
« on: 06/20/2017 04:11 pm »
It seems that starhawk92 has had other things crop up in his life that are more important than maintaining a launch manifest on an internet forum (hard to believe, but sometimes these things happen).  I'll take over the SpaceX manifest maintenance unless someone else is really eager to do it.

We've been using a fixed width format for the SpaceX manifest, and different people have different opinions on how best to make use of the space in the table.  I have a format that is a little bit different from what starhawk92 has been using, you can see it here:
https://forum.nasaspaceflight.com/index.php?topic=40231.msg1533858#msg1533858

I use one line per mission.  Other information (FH booster serial numbers) goes in the footnotes.

Estimated Local Date and Time:  They usually aren't really NET dates, they're our best guess of when the flight will be.  They could move right, could move left, could go away.  You never really know until it takes off.  This is the date/time at the launch pad (local time).  The number following the time is the UTC offset, so 1200/-4 (local) is 1600 (UTC).  If a flight is scheduled for the second quarter of 2018 I put 2018-Q2, not 2018-04.  If local and UTC date are different I put an asterisk between the date and time.

LV/Mission:  Type of launch vehicle (F9/FH), and the mission numbers from the FCC permits for the launch.  I will probably remove the mission numbers in the future because I can't reliably match them up anymore.

Return: L=Land, S=Sea, X=Expendable.  This keeps the column small and fits FH flights in 3 characters.  (I haven't decided whether to turn the "X" green when it is successfully expended.)

Site: My personal abbreviations, I think they are fairly easy to understand.  C=Canaveral=KSC/CCAFS, V=Vandenberg, B=Boca Chica.

Footnotes: I update the footnote numbers to match the flight numbers.  I haven't really decided whether to use different numbers for FH flights, but am leaning against doing that.

For anyone who hasn't noticed yet, the payload name is a link to the mission discussion thread.  In flights since JCSAT-16 the discussion thread (and also the update thread) has a section at the top with links to other NSF threads and articles for that mission.
« Last Edit: 06/25/2017 08:05 pm by gongora »

Offline ATPTourFan

  • Member
  • Posts: 97
  • Liked: 79
  • Likes Given: 4320
Re: SpaceX Manifest Table Formatting Discussion
« Reply #1 on: 06/20/2017 08:20 pm »
I like all the aspects of your formatting proposal except for the Return column. With 3 characters you can still do something like:

EXP = expendable
LZ1 = LZ1 at CCAFS
JRI = Just Read the Instructions (or whatever 3 characters is best)
OCU = Of course I Still Love You (or whatever 3 characters is best)
LZ? = whatever SpaceX designates the landing pad at SLC-4 in VAFB

Offline Lar

  • Fan boy at large
  • Global Moderator
  • Senior Member
  • *****
  • Posts: 13463
  • Saw Gemini live on TV
  • A large LEGO storage facility ... in Michigan
  • Liked: 11864
  • Likes Given: 11086
Re: SpaceX Manifest Table Formatting Discussion
« Reply #2 on: 06/21/2017 01:21 am »
Why is the core number column called "reuse" ?? Otherwise I think this is awesome!

A: because it didn't get changed yet.
« Last Edit: 06/21/2017 02:44 am by Lar »
"I think it would be great to be born on Earth and to die on Mars. Just hopefully not at the point of impact." -Elon Musk
"We're a little bit like the dog who caught the bus" - Musk after CRS-8 S1 successfully landed on ASDS OCISLY

Offline rockets4life97

  • Full Member
  • ****
  • Posts: 798
  • Liked: 538
  • Likes Given: 365
Re: SpaceX Manifest Table Formatting Discussion
« Reply #3 on: 06/21/2017 07:53 am »
Hmmm... Gongora's new version wraps onto two lines on my browser. Not sure why.

Offline gongora

  • Global Moderator
  • Senior Member
  • *****
  • Posts: 10183
  • US
  • Liked: 13846
  • Likes Given: 5915
Re: SpaceX Manifest Table Formatting Discussion
« Reply #4 on: 06/21/2017 05:28 pm »
I've switched the table in the top post to new format.  I've been told it's still a few characters too wide to show up as a single line on some browsers.  If the width is a big problem I could scrunch it down a little more but I like having two spaces between most of the columns so it is easier to read.

I removed the FCC mission numbers from my table, which meant I could no longer spell out FHeavy, and I wanted more visual distinction between F9 and FH, so I ended up just putting "H" for the Falcon Heavy launch vehicle.

(The old table format is backed up in Reply #20 if anyone wants to refer back to it.  I'll only be maintaining the table in the top post.)
« Last Edit: 06/21/2017 05:44 pm by gongora »

Offline Lar

  • Fan boy at large
  • Global Moderator
  • Senior Member
  • *****
  • Posts: 13463
  • Saw Gemini live on TV
  • A large LEGO storage facility ... in Michigan
  • Liked: 11864
  • Likes Given: 11086
Re: SpaceX Manifest Table Formatting Discussion
« Reply #5 on: 06/21/2017 05:46 pm »
I think the subscript tag migthe be helpful to get more characters on?

[ sub ] and [/ sub ]  (minus the spaces)

MY HACKS ARE DESCRIBED IN ALL CAPS...  FROM HERE IS A COPY OF THE HEADER POST... WITH HACKS
++++++++

Discussion of the manifest, and updates. The best guess at the current manifest is in this post. 
This table is now being maintained by gongora

TEXT WITHOUT SUB:
Prior thread 3 : https://forum.nasaspaceflight.com/index.php?topic=40049.0
SAME TEXT WITH SUB:

Prior thread 3 : https://forum.nasaspaceflight.com/index.php?topic=40049.0


TEST PREFACE WITH SUB

Site: C=Canaveral (UTC-4 EDT,UTC-5 EST)
         SLC-40: Damaged by vehicle explosion (no launches until around August 2017)
         LC-39A: Active for F9, will need further work for FH and Commercial Crew
       V=Vandenberg (UTC-7 PDT,UTC-8 PST)
         SLC-4E: Active for F9
       B=Boca Chica (UTC-5 CDT,UTC-6 CST)
         Site preparation work underway

Daylight saving time starts second Sunday in March, ends first Sunday in November,
time changes at 2:00 a.m. local time
Launch Windows, if known, are in the footnotes.


CHUNK OF TABLE WITHOUT SUB FOR COMPARISION


       LOCAL        LV  Core   Ret-                                    MASS         No-
EST. DATE  TIME/UTC     S/N    urn  PAYLOAD(S)                    ORB  (kg)   Site  tes
---------- -------- --- ------ ---  ----------------------------  ---  -----  ----- ---
2015-12-22          F9  1019   L    ORBCOMM OG2 Launch 2          LEO  1892   C-40   20
2016-01-17 1042/-8  F9         S    Jason-3                       LEO  553    V-4E   21
2016-03-04 1835/-5  F9         S    SES-9                         GTO  5271   C-40   22
2016-04-08 1643/-4  F9  1021   S    CRS-8                         LEO  ~9k    C-40   23
2016-05-06 0121/-4  F9  1022   S    JCSAT-14                      GTO  4696   C-40   24
2016-05-27 1740/-4  F9  1023   S    Thaicom 8                     GTO  3025   C-40   25


TABLE AND POSTSCRIPT ITEMS WITH SUB



       LOCAL        LV  Core   Ret-                                    MASS         No-
EST. DATE  TIME/UTC     S/N    urn  PAYLOAD(S)                    ORB  (kg)   Site  tes
---------- -------- --- ------ ---  ----------------------------  ---  -----  ----- ---
2015-12-22          F9  1019   L    ORBCOMM OG2 Launch 2          LEO  1892   C-40   20
2016-01-17 1042/-8  F9         S    Jason-3                       LEO  553    V-4E   21
2016-03-04 1835/-5  F9         S    SES-9                         GTO  5271   C-40   22
2016-04-08 1643/-4  F9  1021   S    CRS-8                         LEO  ~9k    C-40   23
2016-05-06 0121/-4  F9  1022   S    JCSAT-14                      GTO  4696   C-40   24
2016-05-27 1740/-4  F9  1023   S    Thaicom 8                     GTO  3025   C-40   25
2016-06-15 1029/-4  F9         S    Eutelsat 117W B & ABS-2A      GTO  4200   C-40   26
2016-07-18 0045/-4  F9         L    CRS-9                         LEO  ~9k    C-40   27
2016-08-14 0126/-4  F9         S    JCSAT-16                      GTO  ~4600  C-40   28
2016-09-01 0907/-4  F9         N/A  AMOS-6(destroyed in pad test) GTO  5500   C-40   29
2017-01-14 0954/-8  F9  1029   S    Iridium NEXT (Flight 1)       PLR  9600   V-4E   30
2017-02-19 0939/-5  F9  1031   L    CRS 10                        LEO  ~9k    C-39A  31
2017-03-16 0200/-4  F9  1030   X    Echostar 23                   GTO  ~5500  C-39A  32
2017-03-30 1827/-4  F9  1021.2 S    SES-10                        GTO  5282   C-39A  33
2017-05-01 0715/-4  F9  1032   L    NROL-76                       LEO  ?      C-39A  34
2017-05-15 1921/-4  F9  1034   X    Inmarsat 5 F4                 GTO  6086   C-39A  35
2017-06-03 1707/-4  F9  1035   L    CRS 11                        LEO  ~9k    C-39A  36
---------------------------------------------------------------------------------------
2017-06-23 1410/-4  F9  1029.2 S    BulgariaSat-1                 GTO  3669   C-39A  37
2017-06-25 1325/-7  F9  1036   S    Iridium NEXT (Flight 2)       PLR  9600   V-4E   38
2017-07-xx 1935/-4  F9         X    Intelsat 35e                  GTO  ~6k    C-39A  39
2017-07-late        F9         ?    SES-11/Echostar 105           GTO  5400   C-39A  40
2017-08-01          F9         L    CRS 12                        LEO  ~9k    C
2017-08             F9         L    Air Force X-37B OTV-5         LEO  5400   C
2017-08             F9         ?    FORMOSAT-5                    SSO  ~525   V-4E   41
2017-08-24          F9         S    Iridium NEXT (Flight 3)       PLR  9600   V-4E       
2017-Q3             F9         S    Koreasat-5A                   GTO  3500   C
2017-10             F9         S    GovSat-1 (SES-16)             GTO  4000   C
2017                 H         LL?  Falcon Heavy Demo Flight                  C-39A  50
2017-10             F9         S    Iridium NEXT (Flight 4)       PLR  9600   V-4E
2017-10             F9         ?    SAOCOM 1A                     SSO  3000   V-4E
2017-11             F9         L    CRS 13                        LEO  ~9k    C
2017-Q4             F9         S    SES-14 (NASA GOLD payload)    GTO  4200   C
2017-12             F9         S    Iridium NEXT (Flight 5)       PLR  9600   V-4E
2017                 H         LL?  STP-2 (US Air Force)          MEO  ~8k?   C-39A
2017-Q4             F9              Hispasat 1F                   GTO  ~5k    C      60
2017-12             F9              Bangabandhu                   GTO  ~3500  C      61
2017                F9              Paz & co-passenger            SSO  1400   V-4E   62
2018                F9              Spaceflight SSO-A (575km)     SSO         V-4E   70
2018                F9         S    Es'hail 2                     GTO  ~3k    C
2018                F9         ?    PSN-6 and co-passenger        GTO  5000   C
2018-02             F9         L    CRS 14                        LEO  ~9k    C
2018-02             F9              Iridium NEXT (Flight 6)       PLR  9600   V-4E
2018-03             F9         ?    CCtCap DM1                    LEO         C-39A
2018-03-20          F9              NASA (TESS)                   HEO  325    C
2018-04             F9         L    CRS 15                        LEO  ~9k    C
2018-04             F9              Iridium NEXT (Flight 7)       PLR  9600   V-4E
2018-H1             F9              CCiCap In-Flight Abort Test   SUB         C-39A
2018-H1             F9              Telstar 18 Vantage/Apstar-5C  GTO  >5400  C
2018-H1             F9              Telstar 19 Vantage            GTO  >5400  C
2018-05             F9              USAF GPS III A-2              MEO  3880   C
2018-06             F9              Telkom 4                      GTO         C      68
2018                F9              CCtCap DM2 (Crew)             LEO         C-39A
2018-mid            F9              Iridium NEXT 8/GRACE-FO       SSO  ~6000  V     
2018                 H              Arabsat 6A                    GTO  ~6k    C/B
2018-08             F9         L    CRS 16                        LEO  ~9k    C
2018-Q3             F9              RADARSAT Constellation        SSO  1400   V-4E
2018                F9              OHB SARah 1                   SSO  ~2200  V-4E
2018-10             F9         L    CRS 17                        LEO  ~9k    C
2018-Q4             F9              Spaceflight SSO-B (500km)     SSO         V-4E   70
2018-Q4             F9              GiSat-1                       GTO  ~6k    C/B
2018-H2             F9              Spaceflight GTO-1(200x36k/km) GTO         C      70
2018-H2             F9              Spaceflight GTO-2(200x60k/km) GTO         C      70
2018-12             F9         L    CRS 18                        LEO  ~9k    C
2018-end             H         ???  SpaceX Crewed Circumlunar     TLI  ~10k?  C-39A  99
2018                F9              SAOCOM 1B                     SSO  3000   V-4E
2019                F9              CRS 19-20                     LEO         C
2019-02             F9              USAF GPS IIIA-3               MEO  3880   C
2019                F9              OHB SARah 2/3                 SSO  ~3600  V-4E
2019-H2             F9              Spaceflight SSO-C (500km SSO) SSO         V-4E   70
2020                F               Inmarsat 6 F1                 GTO         C/B    65
2020                 H              Red Dragon (Mars Surface)     TMI  ~11k   C/B
2020-H1             F9              Spaceflight GTO-C(200x36k/km) GTO         C/B    70
2020-H1             F9              Spaceflight SSO-D (500km SSO) SSO         V-4E   70
2020-2021            H              ViaSat 3-Americas or 3-EMEA   GTO  6400   C/B    69
2021-04             F9              SWOT                          LEO  2000   V-4E
TBD (NET 2022)       H              ViaSat 3-Asia (maybe)         GTO  6400   C/B    69
TBD                 F               Inmarsat                      GTO         C/B
TBD (2019-2024)     F9              Commercial Crew (6 flights)   LEO         C-39A
TBD (2019-2024)     F9              CRS-2 (6+ flights)            LEO         C
TBD                 F               EutelSat

Return: L=Land,S=Sea,X=Expendable,N/A=Not Applicable
Launch Vehicle: F9=Falcon 9, H=Falcon Heavy, F=Falcon 9 or Heavy
Colors: Successful / Unsuccessful / Mars!!!! / Footnotes

L2 SpaceX CRS External Cargo
L2 Level SpaceX Falcon 9 Stage Watch
SpaceX Launch Log (past launches)
Wikipedia Falcon Launches
Viewing flights from Vandenberg
Upcoming SpaceX Talks

NOTES:
[20] Orbcomm OG2 Launch 2 [FCC F9-21]
[21] Jason-3 [FCC F9-19]
[22] SES-9 [FCC F9-22]
[23] CRS-8 [FCC 23] Discussion / Updates
[24] JCSAT-14 [FCC F9-24] Discussion / Updates / L2 Coverage / Pre-Launch Article /
 Post-Launch Article
[25] Thaicom-8 [FCC F9-25] Discussion / Updates / L2 Coverage / Post-Launch Article
[26] Eutelsat 117 West B & ABS-2A [FCC F9-26] Discussion / Updates / L2 Coverage /
 Pre-Launch Article / Post-Launch Article
[27] CRS-9 [FCC 27] Discussion / Updates / L2 Coverage /
 Return Updates / Static Fire Article / Launch Article
[28] JCSat-16 [FCC F9-28] Discussion
[29] Amos-6 [FCC F9-29] Discussion
[30] Iridium NEXT Flight 1 [FCC F9-30] Discussion
[31] CRS-10 [FCC 32] Discussion
[32] EchoStar 23 [FCC F9-31] Discussion
[33] SES-10 [FCC F9-33] Discussion
[34] NROL-76 [FCC 1363] Discussion
[35] Inmarsat 5 F4 [FCC F9-34] Discussion
[36] CRS-11 Discussion

[37] Bulgariasat-1 Discussion Launch Window 14:10 – 16:10 (Eastern)
[38] Iridium Next (Flight 2) [FCC 1338] Discussion
[39] Intelsat 35e [FCC 1372] Discussion Launch Window 19:35-20:35 (Eastern)
[40] SES 11/Echostar 105 Discussion
[41] FORMOSAT-5 Discussion
[50] FH Demo - Serial Numbers: Center:1033  Side1:1023.2  Side2: 1025.2
[60] Hispasat 1f also called Hispasat 30W-6
[61] Bangabandhu News Article / Satellite Order Press Release / Gunter's Site
[62] Paz (Hisdesat) post in manifest thread / article in DW
[65] Inmarsat 6 F1 SpaceNews mention / Airbus contract / Gunter / Space Intel mention
[68] Telkom 4 links Gunter
[69] Viasat 3 : one of first two Viasat 3 birds in mid-2019 or early-2020.
  Also third Viasat 3 if it gets built?
  ViaSatellite 2/10/16 SpaceNews 2/10/2016 Gunter
[70] Spaceflight Industries : Upcoming Spaceflight Ind. schedule
[99] SpaceX announcement


END TEXT WITH SUB

[xx] Europasat/HellasSat 3 moved to different launch vehicle
[xx] ABS-8 Satellite build cancelled
[xx] SHERPA cancelled from FORMOSAT-5 flight

Competitions for future payloads:
STP-3
Air Force First 6 EELV

L2 notes on manifest:
https://forum.nasaspaceflight.com/index.php?topic=42937.msg1679127#msg1679127
https://forum.nasaspaceflight.com/index.php?topic=42839.msg1683254#msg1683254

Last 10 Edits:
Jun 17  Changed table format, now being maintained by gongora
Jun 06  edit/gongora: Slipped Bulgariasat 2 days.  Added X-37B in August 2017
Jun 05  edit/gongora: Marked CRS-11 successful.  Removed speculative Mars mission dates.
Jun 02  edit/gongora: Removed Eutelsat Quantum
May 25  edit/gongora: Moved Iridium Flight 2 to June 25 (1325 PDT).  Moved Intelsat 35e to July 1.
May 24  edit/gongora: Moved Koreasat-5A to August (educated guess), CCiCap In-Flight Abort to 2018
         removed estimated launch month from FH Demo and STP-2
May 23  edit/gongora: Moved Eutelsat Quantum to 2019
May 21  edit/gongora: Added Telkom 4, June 2018
May 20  edit/gongora: Moved CCtCap DM-1 to March 2018
May 17  edit/gongora: Moved PSN-6 to 2018
May 14  edit/gongora: updated masses (Telstar, Es'hail-2, Hispasat, GiSat) and core numbers for multiple missions 

All comments and updates are welcomed!  Thank you to all contributors!
« Last Edit: 06/21/2017 05:53 pm by Lar »
"I think it would be great to be born on Earth and to die on Mars. Just hopefully not at the point of impact." -Elon Musk
"We're a little bit like the dog who caught the bus" - Musk after CRS-8 S1 successfully landed on ASDS OCISLY

Offline envy887

  • Senior Member
  • *****
  • Posts: 8142
  • Liked: 6799
  • Likes Given: 2963
Re: SpaceX Manifest Table Formatting Discussion
« Reply #6 on: 06/21/2017 08:10 pm »
[ pre ] TEXT HERE [ /pre ] Also gives monospace formatting in a smaller font:

 TEXT HERE 


You can also boldface:


 TEXT HERE 

« Last Edit: 06/22/2017 03:33 pm by envy887 »

Offline rosbif73

  • Veteran
  • Full Member
  • **
  • Posts: 225
  • Liked: 22
  • Likes Given: 37
Re: SpaceX Manifest Table Formatting Discussion
« Reply #7 on: 06/22/2017 11:35 am »
If the width is a big problem I could scrunch it down a little more but I like having two spaces between most of the columns so it is easier to read.

It occurs to me that if you abbreviate the launch site as K for Kennedy (LC39A), C for Canaveral (LC40), V for Vandenberg and B for Boca Chica, you could save three extra characters in width :-)

Offline gongora

  • Global Moderator
  • Senior Member
  • *****
  • Posts: 10183
  • US
  • Liked: 13846
  • Likes Given: 5915
Re: SpaceX Manifest Table Formatting Discussion
« Reply #8 on: 06/22/2017 02:59 pm »
If the width is a big problem I could scrunch it down a little more but I like having two spaces between most of the columns so it is easier to read.

It occurs to me that if you abbreviate the launch site as K for Kennedy (LC39A), C for Canaveral (LC40), V for Vandenberg and B for Boca Chica, you could save three extra characters in width :-)

It doesn't save much because future flights would be listed like K/C, C/B, K/C/B.  Unless you add E for launching East from somewhere.

Offline rockets4life97

  • Full Member
  • ****
  • Posts: 798
  • Liked: 538
  • Likes Given: 365
Re: SpaceX Manifest Table Formatting Discussion
« Reply #9 on: 06/22/2017 03:02 pm »
If the width is a big problem I could scrunch it down a little more but I like having two spaces between most of the columns so it is easier to read.

It occurs to me that if you abbreviate the launch site as K for Kennedy (LC39A), C for Canaveral (LC40), V for Vandenberg and B for Boca Chica, you could save three extra characters in width :-)

It doesn't save much because future flights would be listed like K/C, C/B, K/C/B.  Unless you add E for launching East from somewhere.

Or just make an educated guess and adjust the launch pad when new info is available.

Offline Comga

  • Senior Member
  • *****
  • Posts: 6460
  • Liked: 4567
  • Likes Given: 5105
Re: SpaceX Manifest Table Formatting Discussion
« Reply #10 on: 06/23/2017 02:11 am »
It's still 16 characters too wide for my phone
Wrapping makes it very difficult for me to read
What kind of wastrels would dump a perfectly good booster in the ocean after just one use?

Offline ClayJar

  • Full Member
  • ****
  • Posts: 563
  • Baton Rouge, LA, USA
  • Liked: 1280
  • Likes Given: 126
Re: SpaceX Manifest Table Formatting Discussion
« Reply #11 on: 06/23/2017 12:49 pm »
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)



Discussion of the manifest, and updates. The best guess at the current manifest is in this post. 
This table is now being maintained by gongora

Prior thread 3 : https://forum.nasaspaceflight.com/index.php?topic=40049.0

Site: C=Canaveral (UTC-4 EDT,UTC-5 EST)
         SLC-40: Damaged by vehicle explosion (no launches until around August 2017)
         LC-39A: Active for F9, will need further work for FH and Commercial Crew
      V=Vandenberg (UTC-7 PDT,UTC-8 PST)
         SLC-4E: Active for F9
      B=Boca Chica (UTC-5 CDT,UTC-6 CST)
         Site preparation work underway


Daylight saving time starts second Sunday in March, ends first Sunday in November, time changes at 2:00 a.m. local time
Launch Windows, if known, are in the footnotes.

.LOCALLVCoreRet-..MASS.No-
EST. DATETIME/UTC.S/NurnPAYLOAD(S)ORB(kg)Sitetes
------------------------------------------------------
2015-12-22.F91019LORBCOMM OG2 Launch 2LEO1892C-4020
2016-01-171042/-8F9.SJason-3LEO553V-4E21
2016-03-041835/-5F9.SSES-9GTO5271C-4022
2016-04-081643/-4F91021SCRS-8LEO~9kC-4023
2016-05-060121/-4F91022SJCSAT-14GTO4696C-4024
2016-05-271740/-4F91023SThaicom 8GTO3025C-4025
2016-06-151029/-4F9.SEutelsat 117W B & ABS-2AGTO4200C-4026
2016-07-180045/-4F9.LCRS-9LEO~9kC-4027
2016-08-140126/-4F9.SJCSAT-16GTO~4600C-4028
2016-09-010907/-4F9.N/AAMOS-6(destroyed in pad test)GTO5500C-4029
2017-01-140954/-8F91029SIridium NEXT (Flight 1)PLR9600V-4E30
2017-02-190939/-5F91031LCRS 10LEO~9kC-39A31
2017-03-160200/-4F91030XEchostar 23GTO~5500C-39A32
2017-03-301827/-4F91021.2SSES-10GTO5282C-39A33
2017-05-010715/-4F91032LNROL-76LEO?C-39A34
2017-05-151921/-4F91034XInmarsat 5 F4GTO6086C-39A35
2017-06-031707/-4F91035LCRS 11LEO~9kC-39A36
------------------------------------------------------
2017-06-231410/-4F91029.2SBulgariaSat-1GTO3669C-39A37
2017-06-251325/-7F91036SIridium NEXT (Flight 2)PLR9600V-4E38
2017-07-xx1935/-4F9.XIntelsat 35eGTO~6kC-39A39
2017-07-late.F9.?SES-11/Echostar 105GTO5400C-39A40
2017-08-01.F9.LCRS 12LEO~9kC.
2017-08-17.F9.LAir Force X-37B OTV-5LEO5400C.
2017-08.F9.?FORMOSAT-5SSO~525V-4E41
2017-08-24.F9.SIridium NEXT (Flight 3)PLR9600V-4E.
2017-Q3.F9.SKoreasat-5AGTO3500C.
2017-10.F9.SGovSat-1 (SES-16)GTO4000C.
2017-10.F9.SIridium NEXT (Flight 4)PLR9600V-4E.
2017-10.F9.?SAOCOM 1ASSO3000V-4E.
2017.H.LLSFalcon Heavy Demo Flight.C-39A.50
2017-11.F9.LCRS 13LEO~9kC.
2017-Q4.F9.SSES-14 (NASA GOLD payload)GTO4200C.
2017-12.F9.SIridium NEXT (Flight 5)PLR9600V-4E.
2017-Q4.F9..Hispasat 1FGTO~5kC60
2017-12.F9..BangabandhuGTO~3500C61
2017.F9..Paz & co-passengerSSO1400V-4E62
2018.F9..Spaceflight SSO-A (575km)SSO.V-4E70
2018.F9.SEs'hail 2GTO~3kC.
2018.F9.?PSN-6 and co-passengerGTO5000C.
2018-02.F9.LCRS 14LEO~9kC.
2018-02.F9..Iridium NEXT (Flight 6)PLR9600V-4E.
2018-H1.H.LLSArabsat 6AGTO~6kC-39A.
2018-03.F9.?CCtCap DM1LEO.C-39A.
2018-03-20.F9..NASA (TESS)HEO325C.
2018-04.F9.LCRS 15LEO~9kC.
2018-04.F9..Iridium NEXT (Flight 7)PLR9600V-4E.
2018-H1.F9..CCiCap In-Flight Abort TestSUBC-39A.
2018-H1.F9..Telstar 18 Vantage/Apstar-5CGTO>5400C.
2018-H1.F9..Telstar 19 VantageGTO>5400C.
2018-H1.H.LLSSTP-2 (US Air Force)MEO~8k?C-39A.
2018-05.F9..USAF GPS III A-2MEO3880C.
2018-06.F9..Telkom 4GTO.C68
2018.F9..CCtCap DM2 (Crew)LEO.C-39A.
2018-mid.F9..Iridium NEXT 8/GRACE-FOSSO~6000V.
2018-08.F9.LCRS 16LEO~9kC.
2018-Q3.F9..RADARSAT ConstellationSSO1400V-4E.
2018.F9..OHB SARah 1SSO~2200V-4E.
2018-10.F9.LCRS 17LEO~9kC.
2018-Q4.F9..Spaceflight SSO-B (500km)SSO.V-4E70
2018-Q4.F9..GiSat-1GTO~6kC/B.
2018-H2.F9..Spaceflight GTO-1(200x36k/km)GTO.C70
2018-H2.F9..Spaceflight GTO-2(200x60k/km)GTO.C70
2018-12.F9.LCRS 18LEO~9kC.
2018.F9..SAOCOM 1BSSO3000V-4E.
2018-2019.H.??SpaceX Crewed CircumlunarTLI~10k?C-39A99
2019.F9..CRS 19-20LEO.C.
2019-02.F9..USAF GPS IIIA-3MEO3880C.
2019.F9..OHB SARah 2/3SSO~3600V-4E.
2019-H2.F9..Spaceflight SSO-C (500km SSO)SSO.V-4E70
2020.F..Inmarsat 6 F1GTO.C/B65
2020.H..Red Dragon (Mars Surface)TMI~11kC/B
2020-H1.F9..Spaceflight GTO-C(200x36k/km)GTO.C/B70
2020-H1.F9..Spaceflight SSO-D (500km SSO)SSO.V-4E70
2020-2021.H..ViaSat 3-Americas or 3-EMEAGTO6400C/B69
2021-04.F9..SWOTLEO2000V-4E.
TBD (NET 2022).H..ViaSat 3-Asia (maybe)GTO6400C/B69
TBD.F..InmarsatGTO.C/B.
TBD (2019-2024).F9..Commercial Crew (6 flights)LEO.C-39A.
TBD (2019-2024).F9..CRS-2 (6+ flights)LEO.C.
TBD.F..EutelSat

Return: L=Land,S=Sea,X=Expendable,N/A=Not Applicable
Launch Vehicle: F9=Falcon 9, H=Falcon Heavy, F=Falcon 9 or Heavy
Colors: Successful / Unsuccessful / Mars!!!! / Footnotes

L2 SpaceX CRS External Cargo
L2 Level SpaceX Falcon 9 Stage Watch
SpaceX Launch Log (past launches)
Wikipedia Falcon Launches
Viewing flights from Vandenberg
Upcoming SpaceX Talks

NOTES:
[20] Orbcomm OG2 Launch 2 [FCC F9-21]
[21] Jason-3 [FCC F9-19]
[22] SES-9 [FCC F9-22]
[23] CRS-8 [FCC 23] Discussion / Updates
[24] JCSAT-14 [FCC F9-24] Discussion / Updates / L2 Coverage / Pre-Launch Article / Post-Launch Article
[25] Thaicom-8 [FCC F9-25] Discussion / Updates / L2 Coverage / Post-Launch Article
[26] Eutelsat 117 West B & ABS-2A [FCC F9-26] Discussion / Updates / L2 Coverage / Pre-Launch Article / Post-Launch Article
[27] CRS-9 [FCC 27] Discussion / Updates / L2 Coverage / Return Updates / Static Fire Article / Launch Article
[28] JCSat-16 [FCC F9-28] Discussion
[29] Amos-6 [FCC F9-29] Discussion
[30] Iridium NEXT Flight 1 [FCC F9-30] Discussion
[31] CRS-10 [FCC 32] Discussion
[32] EchoStar 23 [FCC F9-31] Discussion
[33] SES-10 [FCC F9-33] Discussion
[34] NROL-76 [FCC 1363] Discussion
[35] Inmarsat 5 F4 [FCC F9-34] Discussion
[36] CRS-11 Discussion

[37] Bulgariasat-1 Discussion Launch Window 14:10 – 16:10 (Eastern)
[38] Iridium Next (Flight 2) [FCC 1338] Discussion
[39] Intelsat 35e [FCC 1372] Discussion Launch Window 19:35-20:35 (Eastern)
[40] SES 11/Echostar 105 Discussion
[41] FORMOSAT-5 Discussion
[50] FH Demo - Serial Numbers: Center:1033  Side1:1023.2  Side2: 1025.2
[60] Hispasat 1f also called Hispasat 30W-6
[61] Bangabandhu News Article / Satellite Order Press Release / Gunter's Site
[62] Paz (Hisdesat) post in manifest thread / article in DW
[65] Inmarsat 6 F1 SpaceNews mention / Airbus contract / Gunter / Space Intel mention
[68] Telkom 4 links Gunter
[69] Viasat 3 : one of first two Viasat 3 birds in mid-2019 or early-2020.  Also third Viasat 3 if it gets built?
  ViaSatellite 2/10/16 SpaceNews 2/10/2016 Gunter
[70] Spaceflight Industries : Upcoming Spaceflight Ind. schedule
[99] SpaceX announcement

[xx] Europasat/HellasSat 3 moved to different launch vehicle
[xx] ABS-8 Satellite build cancelled
[xx] SHERPA cancelled from FORMOSAT-5 flight

Competitions for future payloads:
STP-3
Air Force First 6 EELV

L2 notes on manifest:
https://forum.nasaspaceflight.com/index.php?topic=42937.msg1679127#msg1679127
https://forum.nasaspaceflight.com/index.php?topic=42839.msg1683254#msg1683254

Last 10 Edits:
Jun 22  Moved Arabsat 6A before STP-2, both early/H1 2018
Jun 17  OTV-5 August 17.  Changed table format, now being maintained by gongora.
Jun 06  edit/gongora: Slipped Bulgariasat 2 days.  Added X-37B in August 2017
Jun 05  edit/gongora: Marked CRS-11 successful.  Removed speculative Mars mission dates.
Jun 02  edit/gongora: Removed Eutelsat Quantum
May 25  edit/gongora: Moved Iridium Flight 2 to June 25 (1325 PDT).  Moved Intelsat 35e to July 1.
May 24  edit/gongora: Moved Koreasat-5A to August (educated guess), CCiCap In-Flight Abort to 2018
         removed estimated launch month from FH Demo and STP-2
May 23  edit/gongora: Moved Eutelsat Quantum to 2019
May 21  edit/gongora: Added Telkom 4, June 2018
May 20  edit/gongora: Moved CCtCap DM-1 to March 2018
May 17  edit/gongora: Moved PSN-6 to 2018

All comments and updates are welcomed!  Thank you to all contributors!

Offline ClayJar

  • Full Member
  • ****
  • Posts: 563
  • Baton Rouge, LA, USA
  • Liked: 1280
  • Likes Given: 126
Re: SpaceX Manifest Table Formatting Discussion
« Reply #12 on: 06/23/2017 01:09 pm »
Okay, looks like it didn't break the forums when I look at the post on Chrome on my desktop.  On my phone, in portrait, the table is cut off on the right (and you can't scroll horizontally).  In landscape, it is quite compressed (lots of line breaking within the columns), but it fits.  (Screenshots attached.)  Of course, in Chrome on my phone, if I hit the menu dots and "Request desktop site..." to get the "full" site instead of the "mobile" site, the [table] form renders as nicely as it does on my desktop.

I now leave the rest of you to discuss the merits of one or the other format, [table] or fixed-width text.  Unsurprisingly, I think I prefer the [table]-based format, but perhaps there are easy improvements to it, too.

Offline mme

  • Full Member
  • ****
  • Posts: 1510
  • Santa Barbara, CA, USA, Earth, Solar System, Milky Way Galaxy, Virgo Supercluster
  • Liked: 2034
  • Likes Given: 5381
Re: SpaceX Manifest Table Formatting Discussion
« Reply #13 on: 06/23/2017 08:37 pm »
...
I now leave the rest of you to discuss the merits of one or the other format, [table] or fixed-width text.  Unsurprisingly, I think I prefer the [table]-based format, but perhaps there are easy improvements to it, too.
I much prefer the use of the table. But not scrolling on the phone may be an issue for some (seems like an SMF bug.) For me it's worth it because it renders well at different zoom levels and window sizes. (I have old eyes that get tired at night.)
Space is not Highlander.  There can, and will, be more than one.

Offline Comga

  • Senior Member
  • *****
  • Posts: 6460
  • Liked: 4567
  • Likes Given: 5105
Re: SpaceX Manifest Table Formatting Discussion
« Reply #14 on: 06/24/2017 12:35 pm »
That works great on my phone
(I use the 'full' option)
But now Bulgariasat is on the wrong side of the line and in the wrong color. Keep up!  Keep up! 😉
What kind of wastrels would dump a perfectly good booster in the ocean after just one use?

Online CraigLieb

  • Full Member
  • ****
  • Posts: 1193
  • Dallas Fort Worth
  • Liked: 1349
  • Likes Given: 2394
Re: SpaceX Manifest Table Formatting Discussion
« Reply #15 on: 06/24/2017 06:01 pm »
Love seeing the table on my phone I use chrome and view full site.
On the ground floor of the National Space Foundation... Colonize Mars!

Offline mnelson

  • Member
  • Posts: 46
  • Salt Lake City, Utah
  • Liked: 80
  • Likes Given: 199
Re: SpaceX Manifest Table Formatting Discussion
« Reply #16 on: 06/24/2017 06:30 pm »
I'm not sure how to say this as respectfully as possible: bleck! It is now much less readable for me. On my laptop (Chrome on a MacBook) I have plenty of screen width and it only uses a very little of the space. The font is very small and blocky. When I enlarge the page the font is large and blocky.

I very much appreciate all the great work on maintaining this list. I'm trying to provide feedback on the new format. Please, please, don't take this as a lack of gratitude for the diligent and consistent effort!

Offline beancounter

  • Full Member
  • ****
  • Posts: 1249
  • Perth, Western Australia
  • Liked: 106
  • Likes Given: 172
Re: SpaceX Manifest Table Formatting Discussion
« Reply #17 on: 06/25/2017 01:02 pm »
I'm not sure how to say this as respectfully as possible: bleck! It is now much less readable for me. On my laptop (Chrome on a MacBook) I have plenty of screen width and it only uses a very little of the space. The font is very small and blocky. When I enlarge the page the font is large and blocky.

I very much appreciate all the great work on maintaining this list. I'm trying to provide feedback on the new format. Please, please, don't take this as a lack of gratitude for the diligent and consistent effort!

Fine on an iPad or iPad mini.
Beancounter from DownUnder

Offline Star One

  • Senior Member
  • *****
  • Posts: 13982
  • UK
  • Liked: 3968
  • Likes Given: 220
Re: SpaceX Manifest Table Formatting Discussion
« Reply #18 on: 06/25/2017 10:11 pm »
I can tell you one thing it looks terrible on Tapatalk on my iPhone 6S+. The text looks far too big and even somewhat hard to look at when colours are used.
« Last Edit: 06/25/2017 10:13 pm by Star One »

Offline yokem55

  • Full Member
  • ****
  • Posts: 653
  • Oregon (Ore-uh-gun dammit)
  • Liked: 468
  • Likes Given: 13
Re: SpaceX Manifest Table Formatting Discussion
« Reply #19 on: 06/25/2017 10:24 pm »
I can tell you one thing it looks terrible on Tapatalk on my iPhone 6S+. The text looks far too big and even somewhat hard to look at when colours are used.
The manifest has never worked in Tapatalk. Previously I had to load up the non mobile web view to make sense of it. Now the mobile view just works.

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: 693
  • Liked: 450
  • Likes Given: 106
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

  • Senior Member
  • *****
  • Posts: 2484
  • Raleigh NC
  • Liked: 3628
  • Likes Given: 1950
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

  • Full Member
  • ****
  • Posts: 495
  • Denver, Colorado
  • Liked: 716
  • Likes Given: 1878
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

  • Full Member
  • *
  • Posts: 141
  • Idaho, USA
  • Liked: 291
  • Likes Given: 1176
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

Offline Comga

  • Senior Member
  • *****
  • Posts: 6460
  • Liked: 4567
  • Likes Given: 5105
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?

Offline gongora

  • Global Moderator
  • Senior Member
  • *****
  • Posts: 10183
  • US
  • Liked: 13846
  • Likes Given: 5915
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.

Offline Formica

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: 32
  • Liked: 4
  • Likes Given: 90
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 »

Offline gongora

  • Global Moderator
  • Senior Member
  • *****
  • Posts: 10183
  • US
  • Liked: 13846
  • Likes Given: 5915
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

  • Full Member
  • *
  • Posts: 127
  • London, UK
  • Liked: 122
  • Likes Given: 2297
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!

Offline gongora

  • Global Moderator
  • Senior Member
  • *****
  • Posts: 10183
  • US
  • Liked: 13846
  • Likes Given: 5915
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

  • Senior Member
  • *****
  • Posts: 2422
  • California
  • Liked: 2006
  • Likes Given: 5634
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

Offline gongora

  • Global Moderator
  • Senior Member
  • *****
  • Posts: 10183
  • US
  • Liked: 13846
  • Likes Given: 5915
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?).

Offline DreamyPickle

  • Full Member
  • ****
  • Posts: 955
  • Home
  • Liked: 921
  • Likes Given: 205
Re: SpaceX Manifest Table Formatting Discussion
« Reply #35 on: 10/19/2017 01:08 pm »
It would be interesting to add a marker in the table for flights where the customer agreed on a reused booster but the ID is not yet known. Instead of a dot in the core S/N column you could have the words "new" and "reuse" when this information is available.

The obvious application would be the next Iridium flights.
« Last Edit: 10/19/2017 03:54 pm by DreamyPickle »

Offline deruch

  • Senior Member
  • *****
  • Posts: 2422
  • California
  • Liked: 2006
  • Likes Given: 5634
Re: SpaceX Manifest Table Formatting Discussion
« Reply #36 on: 10/19/2017 01:22 pm »
I just noticed that the past missions list doesn't have any of the F1 launches or the pad abort. 
Shouldn't reality posts be in "Advanced concepts"?  --Nomadd

Offline swervin

  • Full Member
  • *
  • Posts: 168
  • Viper Driver
  • GA
  • Liked: 44
  • Likes Given: 10
Re: SpaceX Manifest Table Formatting Discussion
« Reply #37 on: 10/19/2017 02:06 pm »
Is there an actual master file of all SpX launches (F1, F9, pad abort)? Heck, throw in the Texas reusability 'launches' as well! Would be a cool timeline to see in one consolidated file!

Also, does anyone have an accurate accounting of which LVs were v0, v1.1, FT, Blk 3, Blk 4, etc?

Thanks!
« Last Edit: 10/19/2017 02:07 pm by swervin »

Offline gongora

  • Global Moderator
  • Senior Member
  • *****
  • Posts: 10183
  • US
  • Liked: 13846
  • Likes Given: 5915
Re: SpaceX Manifest Table Formatting Discussion
« Reply #38 on: 10/19/2017 02:56 pm »
I just noticed that the past missions list doesn't have any of the F1 launches or the pad abort.

I don't think the pad abort belongs on that list.  (I'm not sure the in-flight abort will really belong on that list.)

Offline envy887

  • Senior Member
  • *****
  • Posts: 8142
  • Liked: 6799
  • Likes Given: 2963
Re: SpaceX Manifest Table Formatting Discussion
« Reply #39 on: 10/19/2017 02:57 pm »
I'd be interested in a SpaceX suborbital launches list. Not sure it belongs in this thread though.

Offline Lar

  • Fan boy at large
  • Global Moderator
  • Senior Member
  • *****
  • Posts: 13463
  • Saw Gemini live on TV
  • A large LEGO storage facility ... in Michigan
  • Liked: 11864
  • Likes Given: 11086
Re: SpaceX Manifest Table Formatting Discussion
« Reply #40 on: 10/19/2017 03:32 pm »
Is there an actual master file of all SpX launches (F1, F9, pad abort)? Heck, throw in the Texas reusability 'launches' as well! Would be a cool timeline to see in one consolidated file!

Also, does anyone have an accurate accounting of which LVs were v0, v1.1, FT, Blk 3, Blk 4, etc?

Thanks!

I believe Wikipedia's list is believed to be correct
https://en.wikipedia.org/wiki/List_of_Falcon_9_and_Falcon_Heavy_launches maybe?
But it does not include any F1 launches.

This manifest is better in my view (and might even be a source for that one, NSF has a high reputation for accuracy)
"I think it would be great to be born on Earth and to die on Mars. Just hopefully not at the point of impact." -Elon Musk
"We're a little bit like the dog who caught the bus" - Musk after CRS-8 S1 successfully landed on ASDS OCISLY

Offline gongora

  • Global Moderator
  • Senior Member
  • *****
  • Posts: 10183
  • US
  • Liked: 13846
  • Likes Given: 5915
Re: SpaceX Manifest Table Formatting Discussion
« Reply #41 on: 10/19/2017 03:43 pm »
At some point every manifest compiler looks at the other manifests just to make sure nothing is missing.  (I rarely get around to comparing our manifest against Wikipedia but one time they did find a new mission before we did.)

When I went back to compile the list of past launches I was cross-referencing between Wikipedia, Ed Kyle's site, and Jonathan McDowell's site.  Wikipedia was the quickest and easiest to read but double-checking the launch times and payload masses on the other sites was worth it.

Offline deruch

  • Senior Member
  • *****
  • Posts: 2422
  • California
  • Liked: 2006
  • Likes Given: 5634
Re: SpaceX Manifest Table Formatting Discussion
« Reply #42 on: 10/19/2017 04:30 pm »
I just noticed that the past missions list doesn't have any of the F1 launches or the pad abort.

I don't think the pad abort belongs on that list.  (I'm not sure the in-flight abort will really belong on that list.)
Both abort missions will be launched from active SpaceX pads and therefore are/were taking an available launch slot.  If we are looking at how SpaceX is serving their manifest, IMO they are relevant.  Additionally, both need launch licenses from the FAA.  (I wouldn't include Grasshopper hops for those reasons.)
Shouldn't reality posts be in "Advanced concepts"?  --Nomadd

Offline Paul451

  • Senior Member
  • *****
  • Posts: 3552
  • Australia
  • Liked: 2514
  • Likes Given: 2177
Re: SpaceX Manifest Table Formatting Discussion
« Reply #43 on: 10/30/2017 11:56 am »
Would it be possible to add a link for the Update threads for each launch, in addition to the Discussion thread links.

It would be handy to have them somewhere convenient in chronological order, instead of whenever-someone-last-posted order.

Perhaps the Update link could be in the date-time stamp. (Seems like a logical association, for some reason.)

Eg,

       Local        LV  Core   Ret- .                             .    Mass   .     Mis-
Est. Date,  Time/UTC.   S/N    urn  Payload(s)                    Orb  (kg)   Site sion
------------------- --- ------ ---  ----------------------------  ---  -----  -----  ----
2017-08-24  1151/-7F91038SFORMOSAT-5SSO475V-4E41
2017-09-07  1000/-4F91040LAir Force X-37B OTV-5LEO5400C-39A42
2017-10-09  0537/-7F91041SIridium NEXT (Flight 3)PLR9600V-4E43
2017-10-11  1853/-4F91031.2SSES-11/Echostar 105GTO5200C-39A44
------------------- --- ------ ---  ----------------------------  ---  -----  ----- ----
2017-10-30  1534/-4F91042SKoreasat-5AGTO3500C-39A45
2017-11-15*2000/-5F91043LNorthrop Grumman-ZumaLEO?C-39A46
2017-12-04  1452/-5F9.LCRS 13LEO~10kC-40.
.
.
.

Offline gongora

  • Global Moderator
  • Senior Member
  • *****
  • Posts: 10183
  • US
  • Liked: 13846
  • Likes Given: 5915
Re: SpaceX Manifest Table Formatting Discussion
« Reply #44 on: 10/30/2017 01:58 pm »
The update threads are linked in the first post of the discussion threads (at least for recent missions.)

Offline Lar

  • Fan boy at large
  • Global Moderator
  • Senior Member
  • *****
  • Posts: 13463
  • Saw Gemini live on TV
  • A large LEGO storage facility ... in Michigan
  • Liked: 11864
  • Likes Given: 11086
Re: SpaceX Manifest Table Formatting Discussion
« Reply #45 on: 10/30/2017 07:33 pm »
having both links here saves a lot of clicking (well maybe not a lot, LOL)... we'll double your pay if you do it!
"I think it would be great to be born on Earth and to die on Mars. Just hopefully not at the point of impact." -Elon Musk
"We're a little bit like the dog who caught the bus" - Musk after CRS-8 S1 successfully landed on ASDS OCISLY

Offline gongora

  • Global Moderator
  • Senior Member
  • *****
  • Posts: 10183
  • US
  • Liked: 13846
  • Likes Given: 5915
Re: SpaceX Manifest Table Formatting Discussion
« Reply #46 on: 10/30/2017 07:38 pm »
It doesn't save that much clicking.  Editing the table is already kind of a pain since switching to use the table tags (hit Quote on the manifest post to see what it looks like), adding another URL on every line will just make it worse.
« Last Edit: 10/30/2017 07:40 pm by gongora »

Offline Lar

  • Fan boy at large
  • Global Moderator
  • Senior Member
  • *****
  • Posts: 13463
  • Saw Gemini live on TV
  • A large LEGO storage facility ... in Michigan
  • Liked: 11864
  • Likes Given: 11086
Re: SpaceX Manifest Table Formatting Discussion
« Reply #47 on: 10/30/2017 07:41 pm »
Have you considered generating the whole thing in Excel?  That's what I often do for data driven tables. The hard part is how to handle missing data, you have to have every element IF()ed

I have some sample spreadsheets that generate html around here somewhere.... if that suggestion doesn't make much sense.
« Last Edit: 10/30/2017 07:42 pm by Lar »
"I think it would be great to be born on Earth and to die on Mars. Just hopefully not at the point of impact." -Elon Musk
"We're a little bit like the dog who caught the bus" - Musk after CRS-8 S1 successfully landed on ASDS OCISLY

Offline AncientU

  • Senior Member
  • *****
  • Posts: 6257
  • Liked: 4164
  • Likes Given: 6078
Re: SpaceX Manifest Table Formatting Discussion
« Reply #48 on: 01/31/2018 11:43 pm »
Love how you deemed the GovSat expended core 'unsuccessful'.  ;D

https://forum.nasaspaceflight.com/index.php?topic=43418.msg1702572#msg1702572

« Last Edit: 01/31/2018 11:45 pm by AncientU »
"If we shared everything [we are working on] people would think we are insane!"
-- SpaceX friend of mlindner

Offline Zed_Noir

  • Senior Member
  • *****
  • Posts: 5469
  • Canada
  • Liked: 1801
  • Likes Given: 1296
Re: SpaceX Manifest Table Formatting Discussion
« Reply #49 on: 02/01/2018 02:40 am »
Love how you deemed the GovSat expended core 'unsuccessful'.  ;D

https://forum.nasaspaceflight.com/index.php?topic=43418.msg1702572#msg1702572

Nah, @Gongora just mis-color the X from green to orange in the return column. With X signifying a landing on water instead of being expended with the color to indicate the fate of the core.  ;D

@Gongora should take my table legend revision suggestion. Otherwise he will have to come up a way of classifying the fate of the core from the GovSat-1 flight.  :P



Online CraigLieb

  • Full Member
  • ****
  • Posts: 1193
  • Dallas Fort Worth
  • Liked: 1349
  • Likes Given: 2394
Re: SpaceX Manifest Table Formatting Discussion
« Reply #50 on: 02/01/2018 02:59 am »
Love how you deemed the GovSat expended core 'unsuccessful'.  ;D

https://forum.nasaspaceflight.com/index.php?topic=43418.msg1702572#msg1702572

Nah, @Gongora just mis-color the X from green to orange in the return column. With X signifying a landing on water instead of being expended with the color to indicate the fate of the core.  ;D

@Gongora should take my table legend revision suggestion. Otherwise he will have to come up a way of classifying the fate of the core from the GovSat-1 flight.  :P

 options
W for wet
S for Sea Or C (if we want a sounds like)
D for in the drink
Or  U for Unbelievable or unexpected
On the ground floor of the National Space Foundation... Colonize Mars!

Offline gongora

  • Global Moderator
  • Senior Member
  • *****
  • Posts: 10183
  • US
  • Liked: 13846
  • Likes Given: 5915
Re: SpaceX Manifest Table Formatting Discussion
« Reply #51 on: 02/01/2018 03:03 am »
I was always unsure of whether to make the "X" green before because I thought it was redundant.  Now I guess I need to go back and color them in.

Offline Lar

  • Fan boy at large
  • Global Moderator
  • Senior Member
  • *****
  • Posts: 13463
  • Saw Gemini live on TV
  • A large LEGO storage facility ... in Michigan
  • Liked: 11864
  • Likes Given: 11086
Re: SpaceX Manifest Table Formatting Discussion
« Reply #52 on: 02/01/2018 03:51 am »
so green X is going to be a successfully expended stage (it was destroyed) and red X is going to be a failed expended stage (it was recovered completely and thus it was a completely failed destruction) and yellow X is partial failure to expend (some of it was recovered) ???
« Last Edit: 02/01/2018 03:51 am by Lar »
"I think it would be great to be born on Earth and to die on Mars. Just hopefully not at the point of impact." -Elon Musk
"We're a little bit like the dog who caught the bus" - Musk after CRS-8 S1 successfully landed on ASDS OCISLY

Online Semmel

  • Senior Member
  • *****
  • Posts: 2178
  • Germany
  • Liked: 2433
  • Likes Given: 11916
Re: SpaceX Manifest Table Formatting Discussion
« Reply #53 on: 02/01/2018 11:42 am »
so green X is going to be a successfully expended stage (it was destroyed) and red X is going to be a failed expended stage (it was recovered completely and thus it was a completely failed destruction) and yellow X is partial failure to expend (some of it was recovered) ???

Well, since red is reserved for Mars, a red cross would mean a successful (it was destroyed) expending of the stage on Mars. Didnt know the first stage can get THAT far..

Offline meberbs

  • Senior Member
  • *****
  • Posts: 3096
  • Liked: 3379
  • Likes Given: 777
Re: SpaceX Manifest Table Formatting Discussion
« Reply #54 on: 02/01/2018 03:08 pm »
I was always unsure of whether to make the "X" green before because I thought it was redundant.  Now I guess I need to go back and color them in.
I have liked the black X's since it makes it easy to see them as separate from landings, however I fully approve of the yellow X to highlight this absurd situation, and that does by extension imply the other X's should be green. (Or maybe make them blue, though that adds something to the legend.)

Offline ValmirGP

Re: SpaceX Manifest Table Formatting Discussion
« Reply #55 on: 02/01/2018 03:16 pm »

I have liked the black X's since it makes it easy to see them as separate from landings, however I fully approve of the yellow X to highlight this absurd situation, and that does by extension imply the other X's should be green. (Or maybe make them blue, though that adds something to the legend.)

If it is to highlight it's absurd situation, I would stick with my suggestion on the launch party and put a  :o  in place of the X

Offline mme

  • Full Member
  • ****
  • Posts: 1510
  • Santa Barbara, CA, USA, Earth, Solar System, Milky Way Galaxy, Virgo Supercluster
  • Liked: 2034
  • Likes Given: 5381
Re: SpaceX Manifest Table Formatting Discussion
« Reply #56 on: 02/01/2018 04:53 pm »

I have liked the black X's since it makes it easy to see them as separate from landings, however I fully approve of the yellow X to highlight this absurd situation, and that does by extension imply the other X's should be green. (Or maybe make them blue, though that adds something to the legend.)

If it is to highlight it's absurd situation, I would stick with my suggestion on the launch party and put a  :o  in place of the X
I agree though I was just thinking an asterisk (*), exclamation (!) or a footnote [1].  This is likely a really rare occurrence.  Of course I would have bet money this would never happen so what the heck so I know?
Space is not Highlander.  There can, and will, be more than one.

Offline oldAtlas_Eguy

  • Senior Member
  • *****
  • Posts: 5303
  • Florida
  • Liked: 5003
  • Likes Given: 1437
Re: SpaceX Manifest Table Formatting Discussion
« Reply #57 on: 02/01/2018 06:40 pm »
An O (Ocean) for a stage that does all the burns but does not land on a solid object (ASDS) or land. The X should be for no attempt (no recovery burns) at recovery. A green O would be a successful landing in the ocean without a breakup. A green X is a successful expenditure of the stage but actually that is not really a either/or type of thing. Expenditure will always be successful if the vehicle stages OK.

Offline Paul451

  • Senior Member
  • *****
  • Posts: 3552
  • Australia
  • Liked: 2514
  • Likes Given: 2177
Re: SpaceX Manifest Table Formatting Discussion
« Reply #58 on: 02/01/2018 08:37 pm »
O the problems we have.

Offline rockets4life97

  • Full Member
  • ****
  • Posts: 798
  • Liked: 538
  • Likes Given: 365
Re: SpaceX Manifest Table Formatting Discussion
« Reply #59 on: 02/04/2018 11:12 am »
Shouldn't Zuma be green? The launch was successful from SpaceX's perspective. The loss of payload occurred after SpaceX's portion of the mission was over.

Offline toruonu

Re: SpaceX Manifest Table Formatting Discussion
« Reply #60 on: 02/04/2018 11:19 am »
Shouldn't Zuma be green? The launch was successful from SpaceX's perspective. The loss of payload occurred after SpaceX's portion of the mission was over.
Which loss of payload? There has been no confirmed loss of payload.

Offline Lar

  • Fan boy at large
  • Global Moderator
  • Senior Member
  • *****
  • Posts: 13463
  • Saw Gemini live on TV
  • A large LEGO storage facility ... in Michigan
  • Liked: 11864
  • Likes Given: 11086
Re: SpaceX Manifest Table Formatting Discussion
« Reply #61 on: 02/04/2018 02:37 pm »
Shouldn't Zuma be green? The launch was successful from SpaceX's perspective. The loss of payload occurred after SpaceX's portion of the mission was over.
Which loss of payload? There has been no confirmed loss of payload.

Alleged loss of alleged payload. Better?
"I think it would be great to be born on Earth and to die on Mars. Just hopefully not at the point of impact." -Elon Musk
"We're a little bit like the dog who caught the bus" - Musk after CRS-8 S1 successfully landed on ASDS OCISLY

Offline Norm38

  • Full Member
  • ****
  • Posts: 1696
  • Liked: 1272
  • Likes Given: 2316
Re: SpaceX Manifest Table Formatting Discussion
« Reply #62 on: 02/07/2018 03:03 pm »
How can an expendable return (Govsat) be unsuccessful?  ???
« Last Edit: 02/07/2018 03:03 pm by Norm38 »

Offline the_other_Doug

  • Senior Member
  • *****
  • Posts: 3010
  • Minneapolis, MN
  • Liked: 2191
  • Likes Given: 4620
Re: SpaceX Manifest Table Formatting Discussion
« Reply #63 on: 02/07/2018 03:27 pm »
How can an expendable return (Govsat) be unsuccessful?  ???

Because they tried to expend the booster, and failed... :D
-Doug  (With my shield, not yet upon it)

Offline OccasionalTraveller

  • Member
  • Posts: 36
  • Liked: 18
  • Likes Given: 0
Re: SpaceX Manifest Table Formatting Discussion
« Reply #64 on: 02/07/2018 03:37 pm »
How can an expendable return (Govsat) be unsuccessful?  ???
They were testing a landing burn without having anything to actually land on. It didn't sink and appeared to have remained intact. Or at least it didn't sink straight away. There's a speculative recovery thread on Reddit: https://www.reddit.com/r/spacex/comments/7uw4ly/b01322_the_falcon_that_could_recovery_thread/

By contrast, the FH Centre Core is reported to have broken up on impact with the ocean, after missing the drone ship, due to two engines not igniting for the landing burn (Elon Musk in the post-launch press conference).

Sent from my Swift 2 Plus using Tapatalk


Offline cscott

  • Senior Member
  • *****
  • Posts: 3471
  • Liked: 2867
  • Likes Given: 726
Re: SpaceX Manifest Table Formatting Discussion
« Reply #65 on: 02/07/2018 06:52 pm »
How can an expendable return (Govsat) be unsuccessful?  ???

Because they tried to expend the booster, and failed... :D
I think the responders failed to notice the smiley face at the end of the_other_Doug's post.

Offline gongora

  • Global Moderator
  • Senior Member
  • *****
  • Posts: 10183
  • US
  • Liked: 13846
  • Likes Given: 5915
Re: SpaceX Manifest Table Formatting Discussion
« Reply #66 on: 02/08/2018 02:28 am »
Pursuant to that, it's too early to put any notional StarLink launches on, no? Or is it?

In general I'm trying to avoid putting stuff that's still notional (although I will keep a single Mars entry on there since that is the goal.)  Once SpaceX does some successful satellite testing, gets their constellation licensed, and announces a real time frame for deployment I'll start adding Starlink to the manifest.

Offline meekGee

  • Senior Member
  • *****
  • Posts: 14152
  • N. California
  • Liked: 14030
  • Likes Given: 1391
Re: SpaceX Manifest Table Formatting Discussion
« Reply #67 on: 02/12/2018 02:39 am »
On the leading post, for GovSat, you marked a yellow "X" as the landing disposition - an "unsuccessful expendable" - meaning they failed to expend it since it wouldn't sink?

If on purpose, that's awesome.
ABCD - Always Be Counting Down

Offline Lar

  • Fan boy at large
  • Global Moderator
  • Senior Member
  • *****
  • Posts: 13463
  • Saw Gemini live on TV
  • A large LEGO storage facility ... in Michigan
  • Liked: 11864
  • Likes Given: 11086
Re: SpaceX Manifest Table Formatting Discussion
« Reply #68 on: 02/12/2018 04:26 am »
On the leading post, for GovSat, you marked a yellow "X" as the landing disposition - an "unsuccessful expendable" - meaning they failed to expend it since it wouldn't sink?

If on purpose, that's awesome.
You're a little behind. But now we have to decide what to do to denote that the booster they didn't intend to recover ended up having to be destroyed... blinking yellow X ???  :)
"I think it would be great to be born on Earth and to die on Mars. Just hopefully not at the point of impact." -Elon Musk
"We're a little bit like the dog who caught the bus" - Musk after CRS-8 S1 successfully landed on ASDS OCISLY

Offline meekGee

  • Senior Member
  • *****
  • Posts: 14152
  • N. California
  • Liked: 14030
  • Likes Given: 1391
Re: SpaceX Manifest Table Formatting Discussion
« Reply #69 on: 02/12/2018 08:06 am »
On the leading post, for GovSat, you marked a yellow "X" as the landing disposition - an "unsuccessful expendable" - meaning they failed to expend it since it wouldn't sink?

If on purpose, that's awesome.
You're a little behind. But now we have to decide what to do to denote that the booster they didn't intend to recover ended up having to be destroyed... blinking yellow X ???  :)
Glad to see things are fully under control even when I'm away. (Eye roll)

My late vote: The yellow X should shine in perpetuity. That stage fought till the bitter end, and it took a effin jet fighter crack demolition team act of god to take it out..

To 1032!
« Last Edit: 02/12/2018 02:56 pm by meekGee »
ABCD - Always Be Counting Down

Offline vanoord

  • Full Member
  • ****
  • Posts: 693
  • Liked: 450
  • Likes Given: 106
Re: SpaceX Manifest Table Formatting Discussion
« Reply #70 on: 02/12/2018 10:31 am »
Nope. SpaceX have denied that they had to ask the USAF for assistance.

It either broke up and sank of its own accord; or it was persuaded to do so by outside influence - possibly (but not necessarily) including some form of impact from undisclosed material delivered from a safe distance via means unknown.

Ultimately, it was subject to a soft-landing in water and was expended - as such it probably qualifies as a successful 'Expendable' mission, albeit it lingered for several days.

Offline dsobin

  • Member
  • Posts: 49
  • New Jersey, USA
  • Liked: 15
  • Likes Given: 793
Re: SpaceX Manifest Table Formatting Discussion
« Reply #71 on: 02/19/2018 06:24 pm »
I notice the FH Demo "Return" column shows LSL, while STP-2 is shown as LLS.

If the positions denote left-booster, center core, right-booster, I think STP-2 should be LSL.

Or, if the positions denote left-booster, right-booster, center core, then FH Demo should be changed to LLS.

Whichever is preferred, I think the table should show this consistently.
IMHO, left-center-right is the way to go.

A related issue was discussed in the main Manifest thread, but I didn't see a definitive answer, and the current Table is still inconsistent with respect to past and future launches:
Agree about the abbreviation order, it should be consistent, and side/center/side is better than center/side/side or side/side/center

Offline Lar

  • Fan boy at large
  • Global Moderator
  • Senior Member
  • *****
  • Posts: 13463
  • Saw Gemini live on TV
  • A large LEGO storage facility ... in Michigan
  • Liked: 11864
  • Likes Given: 11086
Re: SpaceX Manifest Table Formatting Discussion
« Reply #72 on: 02/24/2018 05:42 pm »
So[1] should the chart be extended/expanded with a new column to track fairings? They are recovered bits and it is good to collect the data. So far we have some not very clear recovery attempts starting not sure how far back, and then one fairly well publicised one that had a partial success for one half and a fail for the other half[2]

Or is that better tracked on a different (and thus harder to correlate) chart?

1 - because the chart isn't wide enough, and because we don't have anything else to talk about...
2 - yes, the halves need to be tracked separately
"I think it would be great to be born on Earth and to die on Mars. Just hopefully not at the point of impact." -Elon Musk
"We're a little bit like the dog who caught the bus" - Musk after CRS-8 S1 successfully landed on ASDS OCISLY

Online FutureSpaceTourist

  • Global Moderator
  • Senior Member
  • *****
  • Posts: 47936
  • UK
    • Plan 28
  • Liked: 81287
  • Likes Given: 36800
Re: SpaceX Manifest Table Formatting Discussion
« Reply #73 on: 02/24/2018 05:58 pm »
So[1] should the chart be extended/expanded with a new column to track fairings?

I’d be very happy to see fairing recovery data added, as this has the big advantage of having all the data accessible in one place. I really appreciate and like this thread for that reason.

As the return colum is already 3 characters wide, F9 fairing info can be added without any increase in width. Of course that doesn’t work for FH, so either two additional characters are needed or some sort of code/notes would have to be used to avoid increasing the width. Personally I’m ok with either approach.

Offline gongora

  • Global Moderator
  • Senior Member
  • *****
  • Posts: 10183
  • US
  • Liked: 13846
  • Likes Given: 5915
Re: SpaceX Manifest Table Formatting Discussion
« Reply #74 on: 02/24/2018 06:52 pm »
Let's see, we could get a list of 256 colors, use 2 bits for each core and 1 bit for each fairing, and I can just have one character to give the recovery status.

Offline AC in NC

  • Senior Member
  • *****
  • Posts: 2484
  • Raleigh NC
  • Liked: 3628
  • Likes Given: 1950
Re: SpaceX Manifest Table Formatting Discussion
« Reply #75 on: 02/24/2018 08:28 pm »
Do it all together by dropping the extraneous "/" in the Time/UTC and the "-" in the Site and add two characters on the outside of Return for Fairing Halves.  Underscores in the Return column of the example below are aren't necessary but help maintain good clean alignment.

       Local        LV  Core    Ret-  .                             .    Mass   .     Mis-
Est. Date,  Time-UTC.   S/N    urn   Payload(s)                    Orb  (kg)   Site sion
------------------ --- ------ -----  ----------------------------  ---  -----  -----  ----
2018-01-07*2000-5F91043__L__ZumaLEO?C40(48)
2018-01-31  1625-5F91032.2__X__GovSat-1 (SES-16)GTO4230C4049
2018-02-06  1545-5HRNR*_LSL_FH Demo/Tesla RoadsterESC~1.2kC39A(50)
2018-02-22  0617-8F91038.2F_X_fPAZ & Microsat 2a/2bSSO2.2k+V4E51
------------------- --- ------ -----  ----------------------------  ---  -----  ----- ----
2018-02-xx  0035-5F91044__S__Hispasat 1F (30W-6)GTO6092C4052
« Last Edit: 02/24/2018 11:02 pm by AC in NC »

Offline Comga

  • Senior Member
  • *****
  • Posts: 6460
  • Liked: 4567
  • Likes Given: 5105
Re: SpaceX Manifest Table Formatting Discussion
« Reply #76 on: 02/25/2018 12:04 am »
If each of the five components: core, left boooster, right booster, left fairing half, right fairing half, has three potential states: expended, failed recovery, successful recovery, there are 243 combinations. That is less than the 256 ASCII characters, so each outcome can be denoted, albeit cryptically, with a single character.
Now if we add in the characters of the Klingon alphabet.....
Let’s not get carried away here.
What kind of wastrels would dump a perfectly good booster in the ocean after just one use?

Offline launchwatcher

  • Full Member
  • ****
  • Posts: 755
  • Liked: 724
  • Likes Given: 985
Re: SpaceX Manifest Table Formatting Discussion
« Reply #77 on: 02/25/2018 12:40 am »
If each of the five components: core, left boooster, right booster, left fairing half, right fairing half, has three potential states: expended, failed recovery, successful recovery, there are 243 combinations. That is less than the 256 ASCII characters, so each outcome can be denoted, albeit cryptically, with a single character.
Now if we add in the characters of the Klingon alphabet.....
Let’s not get carried away here.
ASCII is a 7-bit code (meaning only 128 distinct codepoints), but it devotes a little over a quarter of its code space to non-printing control characters; only 94 ASCII characters actually make a mark on the page/screen.

you're looking for unicode, which is sufficiently extensible that, if the standards body let you, you could define a set of combining characters that render into the desired rocket configuration.   Unfortunately, the complexity is such that some vendors would get it wrong and certain vehicle configurations would end up crashing your browser....


Offline Comga

  • Senior Member
  • *****
  • Posts: 6460
  • Liked: 4567
  • Likes Given: 5105
Re: SpaceX Manifest Table Formatting Discussion
« Reply #78 on: 02/25/2018 12:59 am »
So you are saying we could use ASCII if we use 2 or 3 colors.
I am afraid that you are not kidding, launchwatcher
I was
“Things should be kept as simple as possible, but no simpler.”
« Last Edit: 02/25/2018 01:02 am by Comga »
What kind of wastrels would dump a perfectly good booster in the ocean after just one use?

Offline launchwatcher

  • Full Member
  • ****
  • Posts: 755
  • Liked: 724
  • Likes Given: 985
Re: SpaceX Manifest Table Formatting Discussion
« Reply #79 on: 02/25/2018 03:39 am »
So you are saying we could use ASCII if we use 2 or 3 colors.
I am afraid that you are not kidding, launchwatcher
I was
“Things should be kept as simple as possible, but no simpler.”
Indeed.

I was, um, paying tribute to a recently fixed bug in several apple products described in some depth here: https://manishearth.github.io/blog/2018/02/15/picking-apart-the-crashing-ios-string/

When you set out to be able to render text in any of world's written languages, it's hard to keep things simple.

Offline Lars-J

  • Senior Member
  • *****
  • Posts: 6809
  • California
  • Liked: 8485
  • Likes Given: 5384
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

  • Senior Member
  • *****
  • Posts: 2178
  • Germany
  • Liked: 2433
  • Likes Given: 11916
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!


Offline gongora

  • Global Moderator
  • Senior Member
  • *****
  • Posts: 10183
  • US
  • Liked: 13846
  • Likes Given: 5915
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

  • Senior Member
  • *****
  • Posts: 2067
  • Liked: 2295
  • Likes Given: 4430
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: 2422
  • California
  • Liked: 2006
  • Likes Given: 5634
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: 6809
  • California
  • Liked: 8485
  • Likes Given: 5384
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

  • Full Member
  • **
  • Posts: 227
  • U.S. West Coast
  • Liked: 431
  • Likes Given: 1013
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.

Offline gongora

  • Global Moderator
  • Senior Member
  • *****
  • Posts: 10183
  • US
  • Liked: 13846
  • Likes Given: 5915
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

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.

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.

Offline gongora

  • Global Moderator
  • Senior Member
  • *****
  • Posts: 10183
  • US
  • Liked: 13846
  • Likes Given: 5915
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.


Offline IntoTheVoid

  • Full Member
  • ****
  • Posts: 422
  • USA
  • Liked: 420
  • Likes Given: 134
Re: SpaceX Manifest Table Formatting Discussion
« Reply #91 on: 12/16/2018 03:50 pm »
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)

Offline gongora

  • Global Moderator
  • Senior Member
  • *****
  • Posts: 10183
  • US
  • Liked: 13846
  • Likes Given: 5915
Re: SpaceX Manifest Table Formatting Discussion
« Reply #92 on: 12/16/2018 04:00 pm »
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)

I kinda like the way new cores stand out if you don't put a suffix on them, now that so many of the flights are reused cores.

Offline GregTheGrumpy

Re: SpaceX Manifest Table Formatting Discussion
« Reply #93 on: 04/23/2019 06:49 pm »
... do we still consider the FH center core to be a successful landing?

I'd say yes, the landing was a success pending more information.  If the leg failed due to damage during the landing then that could be considered failed because it contributed directly to the loss of the booster.  Otherwise, a big bumpy sea doesn't negate the success of the landing.  If one allots a certain percentage of loss in "handling" then this might even qualify as a success in the overall scheme of things.

Offline tleski

  • Full Member
  • ****
  • Posts: 477
  • Washington, DC
  • Liked: 367
  • Likes Given: 757
Re: SpaceX Manifest Table Formatting Discussion
« Reply #94 on: 04/23/2019 06:51 pm »
Looks 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.

Offline intelati

Re: SpaceX Manifest Table Formatting Discussion
« Reply #95 on: 04/23/2019 07:49 pm »
Looks 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.

Yes.
Starships are meant to fly

Offline Hauerg

  • Full Member
  • ****
  • Posts: 901
  • Berndorf, Austria
  • Liked: 520
  • Likes Given: 2574
Re: SpaceX Manifest Table Formatting Discussion
« Reply #96 on: 04/23/2019 08:24 pm »
Looks 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.
Landing.
It would also have been a successful „recovery“ if the transport of a booster from LZ to the shed would hafe failed/crashed.

Offline Lar

  • Fan boy at large
  • Global Moderator
  • Senior Member
  • *****
  • Posts: 13463
  • Saw Gemini live on TV
  • A large LEGO storage facility ... in Michigan
  • Liked: 11864
  • Likes Given: 11086
Re: SpaceX Manifest Table Formatting Discussion
« Reply #97 on: 04/23/2019 09:42 pm »
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?
"I think it would be great to be born on Earth and to die on Mars. Just hopefully not at the point of impact." -Elon Musk
"We're a little bit like the dog who caught the bus" - Musk after CRS-8 S1 successfully landed on ASDS OCISLY

Offline GregTheGrumpy

Re: SpaceX Manifest Table Formatting Discussion
« Reply #98 on: 04/23/2019 09:46 pm »
I'd go with asterisk (*) as there are just so many things that could happen.  Detail in a notes field for anything so marked?

Offline Stefan.Christoff.19

  • Member
  • Posts: 60
  • RI USA
  • Liked: 75
  • Likes Given: 78
Re: SpaceX Manifest Table Formatting Discussion
« Reply #99 on: 04/24/2019 05:42 pm »
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?

I hear you on tracking the loss, but it becomes a completely different question/purpose than the Manifest table. Manifest is forward looking and while some history is helpful the lack of real estate makes it tough to squeeze all of these tail end cases.
When I created the core schedule thread, I wanted to know what's available for the next flight in order to make speculations on core to flight assignment. I wanted it to compliment the Manifest. That thread is probably not a good historical thread either despite showing which cores are not available due to being expended or lost.
The core wiki Reddit page is really good at core history, but maybe we need one here too.
« Last Edit: 04/24/2019 05:47 pm by Stefan.Christoff.19 »

Offline gongora

  • Global Moderator
  • Senior Member
  • *****
  • Posts: 10183
  • US
  • Liked: 13846
  • Likes Given: 5915
Re: SpaceX Manifest Table Formatting Discussion
« Reply #100 on: 04/30/2019 04:22 pm »
I'm not really opposed to making a change for "booster landed and then fell over" (why is this making me think of a castle built in a swamp? ), but it's not the highest priority information I want to track in the table.  Using an asterisk would make the field one or more characters wider when it's an FH launch.  I'm thinking about just making it blue (the footnote color) instead of green or orange, then putting something in the footnotes.

Offline pb2000

  • Full Member
  • ****
  • Posts: 671
  • Calgary, AB
  • Liked: 759
  • Likes Given: 237
Launches attended: Worldview-4 (Atlas V 401), Iridium NEXT Flight 1 (Falcon 9 FT), PAZ+Starlink (Falcon 9 FT), Arabsat-6A (Falcon Heavy)
Pilgrimaged to: Boca Chica (09/19 & 01/22)

Offline pb2000

  • Full Member
  • ****
  • Posts: 671
  • Calgary, AB
  • Liked: 759
  • Likes Given: 237
Re: SpaceX Manifest Table Formatting Discussion
« Reply #102 on: 02/18/2020 03:22 pm »
Minor nitpick: The H2 and H3 notes should probably be moved to the 'previous missions' post.

Quote
(H2) Arabsat 6A - Serial Numbers:  Side1:1052.1  Center:1055.1  Side2: 1053.1.  Center booster landed on ASDS and then fell over while being towed back to port.
(H3) STP-2 - Serial Numbers:  Side1:1052.2  Center:1057.1  Side2: 1053.2
Launches attended: Worldview-4 (Atlas V 401), Iridium NEXT Flight 1 (Falcon 9 FT), PAZ+Starlink (Falcon 9 FT), Arabsat-6A (Falcon Heavy)
Pilgrimaged to: Boca Chica (09/19 & 01/22)

Offline DreamyPickle

  • Full Member
  • ****
  • Posts: 955
  • Home
  • Liked: 921
  • Likes Given: 205
Re: SpaceX Manifest Table Formatting Discussion
« Reply #103 on: 02/01/2021 08:46 pm »
It would be very cool to add a special marker for crewed missions. We're now at three crewed missions outside the main NASA commercial crew program and there's no obvious way to distinguish them.

Maybe an unicode symbol 🧑‍🚀👩‍🚀

Offline niwax

  • Full Member
  • ****
  • Posts: 1422
  • Germany
    • SpaceX Booster List
  • Liked: 2033
  • Likes Given: 166
Re: SpaceX Manifest Table Formatting Discussion
« Reply #104 on: 02/01/2021 09:33 pm »
It would be very cool to add a special marker for crewed missions. We're now at three crewed missions outside the main NASA commercial crew program and there's no obvious way to distinguish them.

Maybe an unicode symbol 🧑‍🚀👩‍🚀

At this point it might be worth it to have a list for crew missions only.
Which booster has the most soot? SpaceX booster launch history! (discussion)

Offline Paul451

  • Senior Member
  • *****
  • Posts: 3552
  • Australia
  • Liked: 2514
  • Likes Given: 2177
Re: SpaceX Manifest Table Formatting Discussion
« Reply #105 on: 02/01/2021 11:46 pm »
Weirdly, that unicode symbol doesn't display in either Chrome and a Chromium-based browser, but in the notification in my offline email program (Tbird), it did display.

Unicode emojis seem to be highly variable in their implementation and should probably be avoided.

[edit: It also didn't quote for me, even though it showed the blank-square alt.display in the edit window.]
« Last Edit: 02/01/2021 11:48 pm by Paul451 »

Offline panjabi

  • Member
  • Posts: 77
  • Texas
  • Liked: 117
  • Likes Given: 202
Re: SpaceX Manifest Table Formatting Discussion
« Reply #106 on: 05/14/2022 12:41 am »
Hello All,

Can we put a red strikethrough like this 1051-12  on the "Core S/N" column when the core is
either retired or damaged or lost?

That will help show the active cores without adding any new columns. It is also consistent with the other used of red in the manifest, in showing a departure from the "norm".

Thank you!
« Last Edit: 05/14/2022 12:46 am by panjabi »

Offline M.E.T.

  • Senior Member
  • *****
  • Posts: 2306
  • Liked: 2901
  • Likes Given: 505
Re: SpaceX Manifest Table Formatting Discussion
« Reply #107 on: 05/18/2022 02:01 am »
Would it be possible to add an index number in the first column of the manifest, showing the number of the launch for the calendar year?

E.G. Launch # 1,2,3…19,20 etc?

Pretty much each time I check the manifest I start squinting and recounting the number of currently completed launches for 2022. Even more relevant now that they are launching so frequently.

Offline panjabi

  • Member
  • Posts: 77
  • Texas
  • Liked: 117
  • Likes Given: 202
Re: SpaceX Manifest Table Formatting Discussion
« Reply #108 on: 05/22/2022 05:57 am »
Hello All,

Can we put a red strikethrough like this 1051-12  on the "Core S/N" column when the core is
either retired or damaged or lost?

That will help show the active cores without adding any new columns. It is also consistent with the other used of red in the manifest, in showing a departure from the "norm".

Thank you!

In the same vein, please consider adding a green color to those (rare) instances when it is a new booster. Makes them easier to spot than looking for a  missing number

1073-1


Thank you!
« Last Edit: 05/22/2022 05:57 am by panjabi »

Offline Comga

  • Senior Member
  • *****
  • Posts: 6460
  • Liked: 4567
  • Likes Given: 5105
Re: SpaceX Manifest Table Formatting Discussion
« Reply #109 on: 06/03/2022 10:54 pm »
There are now several announced launch series with indeterminate dates, like Crew-8 thru -14, Polaris 2& 3, OneWeb, and more.
Could there be some compact notation, like “6xF9” to indicate the extent of the backlog and the fluidity of the scheduling? 
What kind of wastrels would dump a perfectly good booster in the ocean after just one use?

Offline gongora

  • Global Moderator
  • Senior Member
  • *****
  • Posts: 10183
  • US
  • Liked: 13846
  • Likes Given: 5915
Re: SpaceX Manifest Table Formatting Discussion
« Reply #110 on: 06/03/2022 11:27 pm »
There are now several announced launch series with indeterminate dates, like Crew-8 thru -14, Polaris 2& 3, OneWeb, and more.
Could there be some compact notation, like “6xF9” to indicate the extent of the backlog and the fluidity of the scheduling?

What about the current list doesn't suffice?

Offline Comga

  • Senior Member
  • *****
  • Posts: 6460
  • Liked: 4567
  • Likes Given: 5105
Re: SpaceX Manifest Table Formatting Discussion
« Reply #111 on: 06/03/2022 11:44 pm »
There are now several announced launch series with indeterminate dates, like Crew-8 thru -14, Polaris 2& 3, OneWeb, and more.
Could there be some compact notation, like “6xF9” to indicate the extent of the backlog and the fluidity of the scheduling?

What about the current list doesn't suffice?
Polaris is the weakest of my examples
A single second line is no big deal and works fine.
Putting in unique lines for each of the new Crew launches, whose years are uncertain, would be a mess.
It could be argued that the same applies to the bunch of Starlink launches in the next calendar quarter. Multiple lines saying about the same thing seems to just stretch out the list.
It’s your choice, of course.
It is a great page I view quite regularly.
What kind of wastrels would dump a perfectly good booster in the ocean after just one use?

Offline gongora

  • Global Moderator
  • Senior Member
  • *****
  • Posts: 10183
  • US
  • Liked: 13846
  • Likes Given: 5915
Re: SpaceX Manifest Table Formatting Discussion
« Reply #112 on: 12/30/2022 07:10 pm »
Is this too wide?  It adds a column for counting the launches in the year, which has been asked for in the past and I agree could be useful now that we have to count through 60+ launches in a year.  (I realize others may not see value in the COSPAR ID but I find it useful and want to keep it).

I'm thinking about dropping the green color for successful landings/missions, it really doesn't add much.



       Local        LV  Core   Ret- .                             .    Mass   .     Mis-CO-#
Est. Date,  Time/UTC.   S/N    urn  Payload(s)                    Orb  (kg)   Site sionSPARYR
------------------- .--- ------ .---  ------------------------  --- .-----  -----  ------.----.---
2022-06-17  1209/-4F91060-13SStarlink 4-19LEO~16kC-39AF9-158-0621
2022-06-18  0719/-7F91071-3LSARah 1SSO~4kVF9-159-0632
2022-06-19  0030/-4F91061-9SUSA 328-331/GlobalstarLEO.C-40F9-160-0643
2022-09-04*2209/-4F91052-7SStarlink 4-20/Varuna (R)LEO~16kC-40F9-174-10710
2022-09-10*2120/-4F91058-14SStarlink 4-2/BW3 (R)LEO~16kC-39AF9-175-11199
2022-11-01  0941/-4HNNNLXLUSSF-44GEO.C-39A(H4)-144100
2022-11-02*2325/-4F91067-7SHotbird 13GGTO4500C-40F9-184-146101
------------------- --- ------ ---  ------------------------  ---  -----  ----- -----------
2023-01-02 0955/-5F9..SpaceX Transporter-6SSO.C ...
2023-01-08 (NET)F9.LOneweb F16PLR.C...
2023-01-10H.SXSUSSF-67..C-39A(H6)..
2023-01-18F91077.2SGPS III-6MEO4400C...
2023F9.SAmazonas NexusGTO4500C...

Offline AC in NC

  • Senior Member
  • *****
  • Posts: 2484
  • Raleigh NC
  • Liked: 3628
  • Likes Given: 1950
Re: SpaceX Manifest Table Formatting Discussion
« Reply #113 on: 12/31/2022 06:49 pm »
I'm thinking about dropping the green color for successful landings/missions, it really doesn't add much.
Makes sense.  Color for exceptions

Offline Comga

  • Senior Member
  • *****
  • Posts: 6460
  • Liked: 4567
  • Likes Given: 5105
Re: SpaceX Manifest Table Formatting Discussion
« Reply #114 on: 12/31/2022 07:01 pm »
For me it only wraps if the booster use number is two digits, but that’s becoming pretty frequent. Can you scavenge one more character space for it?

If the green text goes, it must be that success is now normalized.  That in itself is something.

Thanks again for maintaining this list.
What kind of wastrels would dump a perfectly good booster in the ocean after just one use?

Online FutureSpaceTourist

  • Global Moderator
  • Senior Member
  • *****
  • Posts: 47936
  • UK
    • Plan 28
  • Liked: 81287
  • Likes Given: 36800
Re: SpaceX Manifest Table Formatting Discussion
« Reply #115 on: 12/31/2022 08:21 pm »
Can you scavenge one more character space for it?

The - prefixing every COSPAR number seems superfluous?

Offline Paul451

  • Senior Member
  • *****
  • Posts: 3552
  • Australia
  • Liked: 2514
  • Likes Given: 2177
Re: SpaceX Manifest Table Formatting Discussion
« Reply #116 on: 01/01/2023 04:03 pm »
Can you scavenge one more character space for it?
The - prefixing every COSPAR number seems superfluous?

Could also drop the "-" from the site. (Maybe even the "C-" entirely, lets you drop to 3 chars. I think Vandy only needs 3 chars (eg, V4E), ditto BC (BC1/BC2 eventually.))

Also, there's already F9 in the LV column, so is it needed in the mission number? It never used to be there in the old format.



That said, if width is becoming an issue, perhaps switch to two-lines per flight? Put time under date, return under LV, mass under orbit? Perhaps COSPAR under mission? Keep the rest on a single line. Overall, would save about 15 to 20 chars width; and I think the grouping I've suggested is natural (date+time, LV+Return, Orbit+mass.) COSPAR with mission is a bit of a stretch.

[Edit: Actually having the full COSPAR ("COSPAR ID 2022-146") under Payload name might be a more natural match.]

4-5 of those saved chars could then go back into spacing out the columns a bit more for readability. The first and last few are getting a bit smooshed together.



[Edit2: Can I suggest adding different colours to the vehicles (at least, for the non-F9 launches) to make FH and S pop a bit more. Maybe also colour for the F9 launches of Dragon crew.]
« Last Edit: 01/02/2023 06:56 am by Paul451 »

Offline Kiwi53

  • Full Member
  • *
  • Posts: 145
  • New Zealand
  • Liked: 152
  • Likes Given: 212
Re: SpaceX Manifest Table Formatting Discussion
« Reply #117 on: 01/01/2023 08:08 pm »

[Edit2: Can I suggest adding different colours to the vehicles (at least, for the non-F9 launches) to make FH and S pop a bit more. Maybe also colour for the F9 launches of Dragon crew.]

If you're going to use colour, please be aware that a significant proportion1 of your audience will have a red/green colour vision deficiency (i.e. "colour blind"), so you should avoid using red and green to mean different things


1 Between roughly 8% and 12% of the male Caucasian (European) population2 has a red/green colour vision deficiency. I somehow suspect that the audience here is rather highly biased towards that demographic.

2 I am not aware of the statistics for other racial/ethnic groupings

Offline UKobserver

  • Member
  • Posts: 33
  • Liked: 79
  • Likes Given: 25
Re: SpaceX Manifest Table Formatting Discussion
« Reply #118 on: 01/02/2023 02:45 am »
I find it much harder to quickly assimilate the data when one launch is split into two lines.

I was going to suggest deleting the LV column entirely, as that info is duplicated in the mission column (where it is arguably needed more), and is also implied from the data in the return column (1 letter = F9, 3 letters = heavy).

The mission column is currently empty prior to launch (except for a few Heavy hyperlinks); how about putting the F9/H/S prefix there from the start and then simply adding the mission number once launched?

Offline Paul451

  • Senior Member
  • *****
  • Posts: 3552
  • Australia
  • Liked: 2514
  • Likes Given: 2177
Re: SpaceX Manifest Table Formatting Discussion
« Reply #119 on: 01/02/2023 05:29 am »
[Edit2: Can I suggest adding different colours to the vehicles (at least, for the non-F9 launches) to make FH and S pop a bit more. Maybe also colour for the F9 launches of Dragon crew.]
If you're going to use colour, please be aware that a significant proportion1 of your audience will have a red/green colour vision deficiency (i.e. "colour blind"), so you should avoid using red and green to mean different things

I don't mean to replace the LV column with colour somewhere else. I mean to colour the labels "F9" "H" "S" differently. The info is still there in the text, the colour would be just a convenience to make it easier to quickly spot non-F9 launches.

Note that the launch vehicles are currently all black. So even worse case, colour-blind readers are no worse off.

Offline Herb Schaltegger

Re: SpaceX Manifest Table Formatting Discussion
« Reply #120 on: 01/02/2023 02:07 pm »
If we’re bumping up this old thread, how ‘bout adding a simple line counter to track overall numbers of launches. When SpaceX was launching 10 - 12 times a year or less, it wasn’t hard to keep track. But as the years add up and launches/year get into the dozens, it’s really hard to manually count lines.

Alternately, allow whomever is maintaining the manifest to attach an updated .csv file or something to the first post in the thread so those of us interested in stats can do the counting ourselves.
« Last Edit: 01/02/2023 02:08 pm by Herb Schaltegger »
Ad astra per aspirin ...

Offline Comga

  • Senior Member
  • *****
  • Posts: 6460
  • Liked: 4567
  • Likes Given: 5105
Re: SpaceX Manifest Table Formatting Discussion
« Reply #121 on: 01/02/2023 06:03 pm »
If we’re bumping up this old thread, how ‘bout adding a simple line counter to track overall numbers of launches. When SpaceX was launching 10 - 12 times a year or less, it wasn’t hard to keep track. But as the years add up and launches/year get into the dozens, it’s really hard to manually count lines.

Alternately, allow whomever is maintaining the manifest to attach an updated .csv file or something to the first post in the thread so those of us interested in stats can do the counting ourselves..

"whomever"!?!
This is mantained by our esteemed gongora, to whom much appreciation is due.
Whomever, indeed

If we are still scrounging columns, I agree that the mission number column doesn't need the "F9-".
If it just has the number, it can be assumed that it's a Falcon 9.
For Heavy flights, "H-#" fits for the next three flights but "H##" would be adequate for the next 90.
Superheavy.Starship launches can do the same with an "S"
Or just cut two columns and use "H-##" and "S-##"

I also agree that keeping each flight on one line is much to be preferred.

Herb's idea of a counter for the yeat-to-date launch count might be nice, but we can't ask to add to gongora's task, which gets more time consuming as SpaceX's pace accelerates.
« Last Edit: 01/02/2023 06:03 pm by Comga »
What kind of wastrels would dump a perfectly good booster in the ocean after just one use?

Offline Herb Schaltegger

Re: SpaceX Manifest Table Formatting Discussion
« Reply #122 on: 01/02/2023 06:26 pm »
If we’re bumping up this old thread, how ‘bout adding a simple line counter to track overall numbers of launches. When SpaceX was launching 10 - 12 times a year or less, it wasn’t hard to keep track. But as the years add up and launches/year get into the dozens, it’s really hard to manually count lines.

Alternately, allow whomever is maintaining the manifest to attach an updated .csv file or something to the first post in the thread so those of us interested in stats can do the counting ourselves..

"whomever"!?!
This is mantained by our esteemed gongora, to whom much appreciation is due.
Whomever, indeed


Don't get your knickers in a twist - just because a forum moderator/staffer posts the updates doesn't automatically imply that they are the same person actually tracking the data. I am and have been a member of many forums where an admin or moderator simply posts or maintains data collated by others.
Ad astra per aspirin ...

Offline meekGee

  • Senior Member
  • *****
  • Posts: 14152
  • N. California
  • Liked: 14030
  • Likes Given: 1391
Re: SpaceX Manifest Table Formatting Discussion
« Reply #123 on: 01/02/2023 07:26 pm »
When I was a young one  all the text was green and nobody complained :)

Please keep the color scheme (while also keeping the letters - color blind people can still get the info, but color coding is nice)

Dropping the"-" is a good idea. 

ABCD - Always Be Counting Down

Offline gongora

  • Global Moderator
  • Senior Member
  • *****
  • Posts: 10183
  • US
  • Liked: 13846
  • Likes Given: 5915
Re: SpaceX Manifest Table Formatting Discussion
« Reply #124 on: 01/03/2023 08:24 pm »
Ugh, I can't fit the past flights in a single post anymore (too many characters).  Definitely not adding colors to any more columns, that's like 20 characters per column per line.

Offline meekGee

  • Senior Member
  • *****
  • Posts: 14152
  • N. California
  • Liked: 14030
  • Likes Given: 1391
Re: SpaceX Manifest Table Formatting Discussion
« Reply #125 on: 01/03/2023 09:34 pm »
Ugh, I can't fit the past flights in a single post anymore (too many characters).  Definitely not adding colors to any more columns, that's like 20 characters per column per line.
You can do launch numbers in hex!
ABCD - Always Be Counting Down

Offline shark0302

  • Member
  • Posts: 20
  • Liked: 11
  • Likes Given: 0
Re: SpaceX Manifest Table Formatting Discussion
« Reply #126 on: 01/03/2023 09:41 pm »
Ugh, I can't fit the past flights in a single post anymore (too many characters).  Definitely not adding colors to any more columns, that's like 20 characters per column per line.
Dumb question can you use the vertical pipe "|" instead of dash to compact the line's?
« Last Edit: 01/04/2023 11:17 am by zubenelgenubi »

Offline Herb Schaltegger

Re: SpaceX Manifest Table Formatting Discussion
« Reply #127 on: 01/03/2023 11:22 pm »
Ugh, I can't fit the past flights in a single post anymore (too many characters).  Definitely not adding colors to any more columns, that's like 20 characters per column per line.

Can you attach a .csv with each update so stats-counters can do our counting and data massaging offline?
« Last Edit: 01/03/2023 11:23 pm by Herb Schaltegger »
Ad astra per aspirin ...

Offline gongora

  • Global Moderator
  • Senior Member
  • *****
  • Posts: 10183
  • US
  • Liked: 13846
  • Likes Given: 5915
Re: SpaceX Manifest Table Formatting Discussion
« Reply #128 on: 01/03/2023 11:37 pm »
That would require me to make a csv file, which probably wouldn't be a bad idea eventually.

If you're mostly wanting to do stats on past launches, I'd suggest looking at Jonathan's site:
https://planet4589.org/space/gcat/data/launch/Falcon9.html

Offline Paul451

  • Senior Member
  • *****
  • Posts: 3552
  • Australia
  • Liked: 2514
  • Likes Given: 2177
Re: SpaceX Manifest Table Formatting Discussion
« Reply #129 on: 01/05/2023 03:06 pm »
Gongora,
Out of curiosity, how do you generate the table?

Offline gongora

  • Global Moderator
  • Senior Member
  • *****
  • Posts: 10183
  • US
  • Liked: 13846
  • Likes Given: 5915
Re: SpaceX Manifest Table Formatting Discussion
« Reply #130 on: 01/05/2023 04:41 pm »
Currently it's not generated from a data file, it's just manually edited.

Offline Paul451

  • Senior Member
  • *****
  • Posts: 3552
  • Australia
  • Liked: 2514
  • Likes Given: 2177
Re: SpaceX Manifest Table Formatting Discussion
« Reply #131 on: 01/05/2023 08:13 pm »
Currently it's not generated from a data file, it's just manually edited.

[stares in silent horror]

Offline AC in NC

  • Senior Member
  • *****
  • Posts: 2484
  • Raleigh NC
  • Liked: 3628
  • Likes Given: 1950
Re: SpaceX Manifest Table Formatting Discussion
« Reply #132 on: 01/06/2023 02:09 am »
Currently it's not generated from a data file, it's just manually edited.
Dang Dude!!!  I've got the skeleton of a XLSX,CSV somewhere (if you want them) from when I was maintaining the Elon Tweet Index of Links and Quotes.  I can't imagine manually editing that table.

Fair warning though.  It took some hoop-jumping to make it work right.  I was able to use the XLSX to keep the formatting in very thin columns, with the content in regular width columns.  Exported the whole thing to CSV with Pipe Characters instead of commas, and used notepad to covert the Pipes to spaces which just left the formatting.

Offline gongora

  • Global Moderator
  • Senior Member
  • *****
  • Posts: 10183
  • US
  • Liked: 13846
  • Likes Given: 5915
Re: SpaceX Manifest Table Formatting Discussion
« Reply #133 on: 01/06/2023 01:14 pm »
If I generate if from a data file then I'd probably still want to be able to output BBCode, and it will need formatting information for individual columns.  Maybe I'll play around with writing something in the next couple months.

Offline crandles57

  • Full Member
  • ****
  • Posts: 609
  • Sychdyn
  • Liked: 430
  • Likes Given: 136
Re: SpaceX Manifest Table Formatting Discussion
« Reply #134 on: 01/07/2023 11:03 pm »
If wikipedia table is usually more up to date, perhaps an app to take wikipedia table info and convert it into both a csv file and the bbcode needed would be useful?

https://en.wikipedia.org/wiki/List_of_Falcon_9_and_Falcon_Heavy_launches#Future_launches

Offline gongora

  • Global Moderator
  • Senior Member
  • *****
  • Posts: 10183
  • US
  • Liked: 13846
  • Likes Given: 5915
Re: SpaceX Manifest Table Formatting Discussion
« Reply #135 on: 01/07/2023 11:47 pm »
No

Offline meekGee

  • Senior Member
  • *****
  • Posts: 14152
  • N. California
  • Liked: 14030
  • Likes Given: 1391
Re: SpaceX Manifest Table Formatting Discussion
« Reply #136 on: 01/08/2023 01:14 pm »
Currently it's not generated from a data file, it's just manually edited.

[stares in silent horror]
Come on, it's not that bad... I always assumed it's just that.

It's not like he's editing it on his phone...

How much harder is it to edit a text file than a spreadsheet?

ABCD - Always Be Counting Down

Offline Paul451

  • Senior Member
  • *****
  • Posts: 3552
  • Australia
  • Liked: 2514
  • Likes Given: 2177
Re: SpaceX Manifest Table Formatting Discussion
« Reply #137 on: 01/09/2023 10:08 pm »
How much harder is it to edit a text file than a spreadsheet?

Have you tried doing complex tables in BBCode?

Offline meekGee

  • Senior Member
  • *****
  • Posts: 14152
  • N. California
  • Liked: 14030
  • Likes Given: 1391
Re: SpaceX Manifest Table Formatting Discussion
« Reply #138 on: 01/10/2023 06:43 am »
How much harder is it to edit a text file than a spreadsheet?

Have you tried doing complex tables in BBCode?
Copy the last line, tweak the words...
Not ideal but I can see it.
ABCD - Always Be Counting Down

Offline Herb Schaltegger

Re: SpaceX Manifest Table Formatting Discussion
« Reply #139 on: 01/10/2023 11:53 am »
Let me just point out that this is a solved problem. Search Google or your favorite search engine for “Excel convert table to BBCODE” and you get a bunch of hits from people who have stared down this problem, solved it, and shared the results.
Ad astra per aspirin ...

Offline gongora

  • Global Moderator
  • Senior Member
  • *****
  • Posts: 10183
  • US
  • Liked: 13846
  • Likes Given: 5915
Re: SpaceX Manifest Table Formatting Discussion
« Reply #140 on: 01/10/2023 06:08 pm »
A simple conversion of Excel to BBCode probably doesn't help me at all unless I changed the functionality of the table

Offline Herb Schaltegger

Re: SpaceX Manifest Table Formatting Discussion
« Reply #141 on: 01/10/2023 06:36 pm »
A simple conversion of Excel to BBCode probably doesn't help me at all unless I changed the functionality of the table

I mean, you stated above (unless I misunderstand) that you’re basically just keeping a text document now.

If you converted to a true tabular format in something like Excel or a comparable spreadsheet application, you could manipulate, arrange, sort, and parse the data at will from inside the spreadsheet, then export whatever data, in whatever order or format you like, infinitely.

If there are readily-available tools to convert that output (whether it be natively inside Excel, or from CSV or tab-delimited files or whatever), why would you not want to take advantage of that flexibility?
Ad astra per aspirin ...

Offline gongora

  • Global Moderator
  • Senior Member
  • *****
  • Posts: 10183
  • US
  • Liked: 13846
  • Likes Given: 5915
Re: SpaceX Manifest Table Formatting Discussion
« Reply #142 on: 01/10/2023 06:58 pm »
The conversion needs to include formatting information, not just data.  Otherwise I'm better off maintaining my current routine.

Offline Comga

  • Senior Member
  • *****
  • Posts: 6460
  • Liked: 4567
  • Likes Given: 5105
Re: SpaceX Manifest Table Formatting Discussion
« Reply #143 on: 01/10/2023 07:55 pm »
The conversion needs to include formatting information, not just data.  Otherwise I'm better off maintaining my current routine.

Sure, but that’s easy
The formatting can be in hidden columns that print the hypertext coding, and ate copied down en mass with a drag.
For instance, you could augment the (table column stop, table column start) before and after the mission name with the green color that was extra work to add
After a launch, you cut the row with the dashes, and insert it under the launched mission.
Then you just drag-copy the format with the green color start and stop.
Piece of cake
Quick as a wink
And that’s just off-the-cuff
YMMBB (Your mileage may be better)

I keep my own manifest and history in a spreadsheet that has been evolving for almost  19 years.  A real database might be better, but it works well for me.

“To a man with a hammer,
Every problem looks like a nail.
I have Excel!”
What kind of wastrels would dump a perfectly good booster in the ocean after just one use?

Offline Paul451

  • Senior Member
  • *****
  • Posts: 3552
  • Australia
  • Liked: 2514
  • Likes Given: 2177
Re: SpaceX Manifest Table Formatting Discussion
« Reply #144 on: 01/11/2023 02:32 am »
The conversion needs to include formatting information, not just data.  Otherwise I'm better off maintaining my current routine.
Sure, but that’s easy
The formatting can be in hidden columns that print the hypertext coding, and ate copied down en mass with a drag.
For instance, you could augment the (table column stop, table column start) before and after the mission name with the green color that was extra work to add
After a launch, you cut the row with the dashes, and insert it under the launched mission.
Then you just drag-copy the format with the green color start and stop.

I was goofing around with an Excel s/sheet (pedantically, a Libreoffice s/sheet saved as .xls) and figured the most user friendly way of doing it is to be as dumb as possible.

No macros/scripts. Use multiple sheets. First sheet is just data (but with extra columns for the colour/urls for their associated cell.) The second sheet turns that into markdown format for each single TD cell, but with as many extra columns as needed to first explode then stepwise concatenate the cell markdown. Third sheet concats the completed cells in each row into a single line of text. Fourth concats all rows into a single copyable line for the whole table.

The idea being that if you need to change anything about the format, not just the data, everything is exploded into pieces that can hopefully be manipulated fairly easy, without having to worry too much about the upstream or downstream layout/formulae. And if you do break something, it'll generally just be a borked cell ref.

I might play around with it some more on the weekend.

Even if it isn't useful to Gongora, I hate creating BBCode tables directly, so doing it in Excel once will be a useful exercise in deciding whether a particular future table will be quicker to do manually or to hack out a spreadsheet.

“To a man with a hammer,
Every problem looks like a nail.
I have Excel!”



[edit: A more interesting puzzle would be turning someone else's BBCode markdown table as a single line into a spreadsheet and getting it to break it apart into Excel/etc formatted cells. Lots of lookups chained together, I suspect, if I want to avoid scripts.]
« Last Edit: 01/11/2023 02:39 am by Paul451 »

Offline Comga

  • Senior Member
  • *****
  • Posts: 6460
  • Liked: 4567
  • Likes Given: 5105
Re: SpaceX Manifest Table Formatting Discussion
« Reply #145 on: 07/18/2023 03:25 pm »
Can the column width for booster number be expanded by a single character?
At present it wraps for boosters on their tenth or greater flights, because there are two digits after the dash for a total of seven (“10XX-1X”)
That started only recently but is now frequent.
It’s hard to keep up with SpaceX!
What kind of wastrels would dump a perfectly good booster in the ocean after just one use?

Tags:
 

Advertisement NovaTech
Advertisement Northrop Grumman
Advertisement
Advertisement Margaritaville Beach Resort South Padre Island
Advertisement Brady Kenniston
Advertisement NextSpaceflight
Advertisement Nathan Barker Photography
1