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

Offline gongora

  • Global Moderator
  • Senior Member
  • *****
  • Posts: 3650
  • US
  • Liked: 2980
  • Likes Given: 1790
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: 52
  • Liked: 29
  • Likes Given: 569
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: 10440
  • Saw Gemini live on TV
  • A large LEGO storage facility ... in Michigan
  • Liked: 7291
  • Likes Given: 5091
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: 551
  • Liked: 253
  • Likes Given: 226
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: 3650
  • US
  • Liked: 2980
  • Likes Given: 1790
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: 10440
  • Saw Gemini live on TV
  • A large LEGO storage facility ... in Michigan
  • Liked: 7291
  • Likes Given: 5091
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: 4464
  • Liked: 2404
  • Likes Given: 1358
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: 215
  • Liked: 17
  • Likes Given: 30
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: 3650
  • US
  • Liked: 2980
  • Likes Given: 1790
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: 551
  • Liked: 253
  • Likes Given: 226
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: 4281
  • Liked: 1523
  • Likes Given: 1258
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: 401
  • Baton Rouge, LA, USA
  • Liked: 854
  • Likes Given: 74
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: 401
  • Baton Rouge, LA, USA
  • Liked: 854
  • Likes Given: 74
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: 1262
  • Santa Barbara, CA, USA, Earth, Solar System, Milky Way Galaxy, Virgo Supercluster
  • Liked: 1573
  • Likes Given: 4200
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: 4281
  • Liked: 1523
  • Likes Given: 1258
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?

Offline CraigLieb

  • Full Member
  • ****
  • Posts: 859
  • Dallas Fort Worth
  • Liked: 779
  • Likes Given: 974
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.
Colonize Mars!

Offline mnelson

  • Member
  • Posts: 44
  • Salt Lake City, Utah
  • Liked: 68
  • Likes Given: 156
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: 1251
  • Perth, Western Australia
  • Liked: 105
  • Likes Given: 167
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: 9558
  • UK
  • Liked: 1759
  • Likes Given: 183
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: 545
  • Oregon (Ore-uh-gun dammit)
  • Liked: 310
  • Likes Given: 12
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

Online vanoord

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

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

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

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

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

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

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

Offline AC in NC

  • Full Member
  • ***
  • Posts: 362
  • Raleigh NC
  • Liked: 286
  • Likes Given: 336
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: 142
  • Denver, Colorado
  • Liked: 154
  • Likes Given: 294
Re: SpaceX Manifest Table Formatting Discussion
« Reply #23 on: 06/26/2017 05:21 PM »
Regarding the 3 characters vs 1 character for return: I think it would be good to stick with a single character per core. Need to be able to track landings of all 3 FH cores individually.

Offline toren

  • Member
  • Posts: 42
  • Idaho, USA
  • Liked: 54
  • Likes Given: 273
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: 4281
  • Liked: 1523
  • Likes Given: 1258
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: 3650
  • US
  • Liked: 2980
  • Likes Given: 1790
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

  • Rocket Boi
  • Member
  • Posts: 67
  • Richmond, CA
  • Liked: 61
  • Likes Given: 432
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
I'm just a space fan, please correct me if I'm wrong!

Offline smh

  • Member
  • Posts: 24
  • Liked: 4
  • Likes Given: 23
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: 3650
  • US
  • Liked: 2980
  • Likes Given: 1790
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: 107
  • London, UK
  • Liked: 89
  • Likes Given: 665
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: 3650
  • US
  • Liked: 2980
  • Likes Given: 1790
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: 2281
  • California
  • Liked: 1791
  • Likes Given: 3905
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: 3650
  • US
  • Liked: 2980
  • Likes Given: 1790
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: 188
  • Home
  • Liked: 79
  • Likes Given: 18
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: 2281
  • California
  • Liked: 1791
  • Likes Given: 3905
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: 165
  • Viper Driver
  • GA
  • Liked: 43
  • Likes Given: 9
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: 3650
  • US
  • Liked: 2980
  • Likes Given: 1790
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: 4464
  • Liked: 2404
  • Likes Given: 1358
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: 10440
  • Saw Gemini live on TV
  • A large LEGO storage facility ... in Michigan
  • Liked: 7291
  • Likes Given: 5091
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: 3650
  • US
  • Liked: 2980
  • Likes Given: 1790
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: 2281
  • California
  • Liked: 1791
  • Likes Given: 3905
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

  • Full Member
  • ****
  • Posts: 1444
  • Australia
  • Liked: 717
  • Likes Given: 586
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: 3650
  • US
  • Liked: 2980
  • Likes Given: 1790
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: 10440
  • Saw Gemini live on TV
  • A large LEGO storage facility ... in Michigan
  • Liked: 7291
  • Likes Given: 5091
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: 3650
  • US
  • Liked: 2980
  • Likes Given: 1790
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: 10440
  • Saw Gemini live on TV
  • A large LEGO storage facility ... in Michigan
  • Liked: 7291
  • Likes Given: 5091
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: 6217
  • Liked: 4008
  • Likes Given: 5545
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: 2448
  • Canada
  • Liked: 359
  • Likes Given: 570
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



Offline CraigLieb

  • Full Member
  • ****
  • Posts: 859
  • Dallas Fort Worth
  • Liked: 779
  • Likes Given: 974
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
Colonize Mars!

Offline gongora

  • Global Moderator
  • Senior Member
  • *****
  • Posts: 3650
  • US
  • Liked: 2980
  • Likes Given: 1790
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: 10440
  • Saw Gemini live on TV
  • A large LEGO storage facility ... in Michigan
  • Liked: 7291
  • Likes Given: 5091
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

  • Full Member
  • ****
  • Posts: 1427
  • Germany
  • Liked: 1233
  • Likes Given: 3340
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

  • Full Member
  • ****
  • Posts: 1757
  • Liked: 1568
  • Likes Given: 382
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: 1262
  • Santa Barbara, CA, USA, Earth, Solar System, Milky Way Galaxy, Virgo Supercluster
  • Liked: 1573
  • Likes Given: 4200
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: 3452
  • Florida
  • Liked: 1852
  • Likes Given: 223
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

  • Full Member
  • ****
  • Posts: 1444
  • Australia
  • Liked: 717
  • Likes Given: 586
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: 551
  • Liked: 253
  • Likes Given: 226
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: 10440
  • Saw Gemini live on TV
  • A large LEGO storage facility ... in Michigan
  • Liked: 7291
  • Likes Given: 5091
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: 1125
  • Liked: 493
  • Likes Given: 706
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: 2726
  • Minneapolis, MN
  • Liked: 1784
  • Likes Given: 3387
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: 14
  • Liked: 6
  • 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: 2949
  • Liked: 2053
  • Likes Given: 664
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: 3650
  • US
  • Liked: 2980
  • Likes Given: 1790
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: 8470
  • N. California
  • Liked: 4663
  • Likes Given: 884
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: 10440
  • Saw Gemini live on TV
  • A large LEGO storage facility ... in Michigan
  • Liked: 7291
  • Likes Given: 5091
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: 8470
  • N. California
  • Liked: 4663
  • Likes Given: 884
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

Online vanoord

  • Full Member
  • ****
  • Posts: 604
  • Liked: 356
  • Likes Given: 67
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: 717
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: 10440
  • Saw Gemini live on TV
  • A large LEGO storage facility ... in Michigan
  • Liked: 7291
  • Likes Given: 5091
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

Offline FutureSpaceTourist

  • Senior Member
  • *****
  • Posts: 6435
  • UK
    • Plan 28
  • Liked: 6083
  • Likes Given: 1782
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: 3650
  • US
  • Liked: 2980
  • Likes Given: 1790
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

  • Full Member
  • ***
  • Posts: 362
  • Raleigh NC
  • Liked: 286
  • Likes Given: 336
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: 4281
  • Liked: 1523
  • Likes Given: 1258
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?

Online launchwatcher

  • Full Member
  • ***
  • Posts: 366
  • Liked: 252
  • Likes Given: 343
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: 4281
  • Liked: 1523
  • Likes Given: 1258
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?

Online launchwatcher

  • Full Member
  • ***
  • Posts: 366
  • Liked: 252
  • Likes Given: 343
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: 4144
  • California
  • Liked: 3539
  • Likes Given: 2187
Re: SpaceX Manifest Table Formatting Discussion
« Reply #80 on: 02/25/2018 03:43 AM »
This formatting discussion is interesting and all, but c'mon... This is so .. 1994? We are not limited to 80 chars width, and welcome to the world of HTML and styled tables, everyone!  8)

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

Online Semmel

  • Full Member
  • ****
  • Posts: 1427
  • Germany
  • Liked: 1233
  • Likes Given: 3340
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: 3650
  • US
  • Liked: 2980
  • Likes Given: 1790
Re: SpaceX Manifest Table Formatting Discussion
« Reply #82 on: 02/25/2018 02:06 PM »
This formatting discussion is interesting and all, but c'mon... This is so .. 1994? We are bot limited to 80 chars width, and welcome to the world of HTML and styled tables, everyone!  8)

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

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

Offline dglow

  • Full Member
  • ****
  • Posts: 826
  • Liked: 652
  • Likes Given: 1602
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: 2281
  • California
  • Liked: 1791
  • Likes Given: 3905
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: 4144
  • California
  • Liked: 3539
  • Likes Given: 2187
Re: SpaceX Manifest Table Formatting Discussion
« Reply #85 on: 04/14/2018 06:55 AM »
One great addition would be the version/block of each F9/FH core. Could that be squeezed into this format?

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

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

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

Offline groknull

  • Member
  • Posts: 29
  • U.S. West Coast
  • Liked: 38
  • Likes Given: 105
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: 3650
  • US
  • Liked: 2980
  • Likes Given: 1790
Re: SpaceX Manifest Table Formatting Discussion
« Reply #87 on: 04/14/2018 07:24 PM »
I think a separate table with more detail would be better, maybe in the Launch Log thread  (or just refer to the table in the r/spacex wiki).  You also need F9 Version in addition to Block (it would end up like F9 1.0, F9 1.2.4).

Offline Formica

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

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

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

Offline IanThePineapple

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

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

Offline gongora

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


Tags: