threelonmusketeers

joined 1 year ago
MODERATOR OF
[–] [email protected] 0 points 7 hours ago

I wish they said with the efficiency of this process is. Seems cool.

[–] [email protected] 3 points 7 hours ago (1 children)

it probably brings you to an instance that isn't yours so you have to figure out a way to open the link from your own instance

Lemmy Universal Link Switcher

This is a pretty much a solved problem, the solution just needs to be promoted more, perhaps even on the join-lemmy page.

[–] [email protected] 1 points 7 hours ago

I sometimes wish voting (or downvoting) could be limited to subscribers the subscribers of a community. Do you think this could help reduce cases like this?

[–] [email protected] 4 points 17 hours ago

To add on to that, Thunder have implemented all these search features in the app.

[–] [email protected] 5 points 18 hours ago (1 children)

The only spelling error I spotted is right at the end where you said Mask and not Musk

Pretty sure "Alone Mask" is intentional. It seems to be common to misspell his name on purpose. I've seen "Elmo Husk", "Leon Skum", etc.

[–] [email protected] 0 points 19 hours ago (2 children)

a massive asteroid smashed into the earth

Asteroid, or proto-planet?

[–] [email protected] 3 points 19 hours ago

Starbase activities (2024-09-06):

  • No Sep 5th cryo delivery tally.
  • Sep 5th addendum: Compilation timelapses of chopstick tests, including a full launch rehearsal from BQD retraction to chopsticks catch. (ViX, NSF 1, NSF 2) When the chopsticks are at the top of the tower, their momentum causes a noticeable amount of tower sway. (Anderson)
  • Build site: Overnight, S31 moves to Massey's. (LabPadre, ViX, Starship Gazer photo, Starship Gazer video, NSF, NSF video, Beyer, Gisler, Doherty)
  • Pad A: Chopsticks testing continues. Chopsticks close, landing rails rise, landing rails lower.
  • Pad B: The CC8800-1 crane is laid down. (ViX, Hammer)
  • Massey's: Crews were spotted at Test Tank 16. (Hammer)
[–] [email protected] 0 points 1 day ago

Even with a long timeline, it seems a bit early for asteroid mining. Until in-space manufacturing gets going, it would likely be profitable for only a few platinum-group elements, and even then I'm not sure.

[–] [email protected] 1 points 1 day ago (1 children)

Good choice. They're federated with LemmyWorld, correct? Just not the piracy community?

[–] [email protected] 0 points 1 day ago (1 children)
[–] [email protected] 5 points 1 day ago

Starbase activities (2024-09-05):

 

Original static webpage version: https://what-if.xkcd.com/115/

10
NROL-113 Launch Thread! (sh.itjust.works)
submitted 2 days ago* (last edited 1 day ago) by [email protected] to c/[email protected]
 

| Scheduled for (UTC) | 2024-09-06, 03:20 | |


|


| | Scheduled for (local) | 2024-09-05, 20:20 (PDT) | | Launch site | SLC-4E, Vandenberg SFB, California, USA | | Booster | B1063-20 | | Landing | Of Course I Still Love You | | Payload | NROL-113 | | Customer | National Reconnaissance Office | | Mission success criteria | Successful delivery of payload to LEO |

Webcasts

| Stream | Link | |


|


| | Space Affairs | https://www.youtube.com/watch?v=IEHplxmatco | Spaceflight Now | https://www.youtube.com/watch?v=NGUkhL4FCIQ | NASASpaceflight | | The Launch Pad | https://www.youtube.com/watch?v=I-QXLkgPp48 | SpaceX | https://x.com/SpaceX/status/1831892881591689372 | The Space Devs |

Stats

Sourced from NextSpaceflight and r/SpaceX:

☑️ 17th consecutive successful Falcon 9 launch (if successful)

☑️ 29th launch from SLC-4E this year

☑️ 5 days, 18:32:00 turnaround for this pad

☑️ 56 day turnaround for B1063

☑️ 101st landing on OCISLY

☑️ 346th Falcon Family Booster landing, 357th Falcon recovery attempt

☑️ 86th Falcon 9 mission this year, 372nd Falcon 9 mission overall

☑️ 87th SpaceX mission of 2024, 387th mission overall (excluding Starship flights)

☑️ 89th SpaceX launch this year, 400th SpaceX launch overall (including Starship flights)

Mission info

Third batch of satellites for a reconnaissance satellite constellation built by SpaceX and Northrop Grumman for the National Reconnaissance Office to provide imaging and other reconnaissance capabilities.

9
submitted 3 days ago* (last edited 1 day ago) by [email protected] to c/[email protected]
 

Starlink Group 8-11 launch out of SLC-40 in Florida currently scheduled for 2024-09-05 15:33 UTC, or 2024-09-05 11:33 local time (EDT). Booster 1077-15 to land on Just Read the Instructions.

Webcasts:

 

The turnaround time between [Starlink 9-5] and the previous flight, Starlink 8-10, was a record for SpaceX at one hour and five minutes.

Different boosters on different coasts, but still cool.

 

Infographic source: rykllan

https://x.com/_rykllan/status/1830330737788092665

  • B1062 successfully completed its 23rd mission, but failed its 23rd recovery.
  • B1061 is now the sole flight leader at 22 flights.
  • B1067 in second place with 21 flights
  • B1063 in third place with 19 flights.
  • B1069 in 4th place at 18 flights.
  • B1071 and B1073 are tied for 5th place at 17 flights each.

https://x.com/_rykllan/status/1830330746055061979

 

I've just created [email protected]. It is similar to [email protected] but the other way around.

Text reads correctly left to right, but visual cues (like colouration or horizontal separation) lead you to try to read it top to bottom.

Links:

 

New CSI Starbase episode just dropped.

Edit: Additional background info from Zack: https://x.com/CSI_Starbase/status/1830325913776726136

Expand for full tweetThis 77 minute deep dive investigation is a combined re-analysis of the first 4 flight tests of Starship. The main focus of the episode is what I describe as a toxic relationship between Raptor 2 & Superheavy. This is a topic that I don't think a lot of folks fully understand.

While I do take somewhat of a satirical approach, there are a few things I want to make sure people understand.

After watching this episode, some folks may come away asking: Why would SpaceX put themselves in this situation to begin with? Should they have known better? Are they ignoring decades of research?

This is not the question I am intending to answer with this episode, nor am I attempting to throw shade although you may potentially leave with that impression.

Instead, my goal here is to highlight some critical challenges that commonly occur when you have multiple teams working on a project, and each of those teams have similar but different goals.

In this case you have:

  1. The Raptor Development team who - in my opinion - was doing everything they could to figure out how to produce an extremely powerful, yet reliable, full flow combustion cycle methalox engine.

At the same time, they also needed to keep rapid manufacturability at the front of their priority list. For every test flight, they need to produce and successfully test 39 engines along with a handful of spares.

And perhaps most importantly, they needed to do it under ABSURD time constraints in order to keep the program moving forward.

Raptor is without a doubt, the most important part of the entire Starship equation at this point in the development process. It is the singular dependent variable which had the potential to cause immense delays for the Starship, Superheavy and arguably the Stage Zero team as well.

The Raptor team did not have the luxury of spending years/decades developing the perfect engine that would not only achieve an insane level of performance and reliability, but do so while also checking off every item on the wishlist of the other teams.

For that reason, important decisions related to the design of the engine (sacrifices may be the better word here) had to be made to temporarily reduce complexity and allow Integrated Flight Testing to begin.

From an outsiders point of view, I believe Superheavy would have never gotten off of the ground with Raptor 1 and would likely have destroyed the launch site in the process of attempting to do so.

Raptor 2 was a minimally viable product capable of preventing from happening...but not without ALOT of help from 👇🏾

  1. Team Superheavy - The booster design and build teams had the incredibly difficult task of giving the Raptor Development team some much needed breathing room.

Think of it this way.....


TR2 - "Look...we really need more time to get this right"

TSH - "Okay, Lets make a trade - yal give us 3 to 400 semi-reliable engines ASAP and we will find a way to compensate for the current shortcomings while you switch your focus over to developing Raptor 3."

TR2 - "Say less! But FYI it kind of has a very strong tendency to leak fuel, randomly explode...oh and theres going to be some unavoidable contamination of your fuel supply for now"

TSH - "Yeah we noticed that...but don't worry! We will just add 20, wait 40, okay ~50 tons of protective measures onto the vehicle.

Damn, this is a MAJOR hit on performance for us but we have your backs. PLEASE. Make it. Count. "

TSS - "AYO that was WAY more ice then we were expecting." 🤣


Keep in mind, there are no sources revealing behind the scenes information here. This, along with everything included in the episode is just my light hearted interpretation of what I have observed over the last year and a half.

The point I'm trying to make here is that none of these things were surprises. Everything was expected and minimally prepared for. I say minimally, because the key is to not overdo it.

In order to avoid unnecessary mass penalties, the severity of what they were dealing with had to be observed in-flight to provide SS and SH teams the data they needed to adjust accordingly.

And THAT is what this episode is about!

Instead of criticizing their decisions, I hope you all can appreciate having somewhat of an inside look at the amazing things the SpaceX team is achieving.

Space is hard, and every company that decides to hop in the game faces similar challenges...we just don't get to hear about it. Especially to the degree that I'm attempting to cover here.

If you are still reading...there is one more thing I want to mention

Comments About Statements made in the Episode: This is important for me to address considering several people have pointed it out.

There is a chance (I'm still not fully convinced yet) that we may have made some errors with our assumption of how gravitational forces will play a role in this situation.

The CSI team is much larger than you might expect, and by some miracle happens to include people with some level of real world expertise in nearly ever topic we attempt to cover.

We typically - with rare exception - spend a great deal of time discussing the relevant math, physics, chemistry, industrial process etc. before it ever reaches my scripts. While I do write everything myself...its far from a one man show.

With that said, we are not perfect and do get things wrong occasionally. On this topic in particular there were split opinions on whether or not earths gravity would produce the effects I've described.

Ultimately, instead of debating it for weeks on end, I decided to include it in this episode. Whether that was the correct decision or not, I'm not sure. Either way I think 95% of the observations made in this episode remain true, or are reasonable assumptions.

My goal is to help folks understand the issues they were facing...and take a look at how they went about solving them.

As far as the gravity stuff....The main point I was going for is that Superheavy is allergic to roll maneuvers and the rest is me trying to explain and help yal visualize why that is. Maybe we could have done better, had we taken an additional month or two to continue the research phase, but that was not an option so we did the best we could with the time available.

Anyway this is way longer than I intended and I hope you all enjoy the episode 🕵🏽‍♂️🫶🏾

 

What recipe did you use, and how did it turn out?

12
submitted 1 week ago* (last edited 1 week ago) by [email protected] to c/[email protected]
 

Second launch of a potential double header tonight.

Starlink Group 8-10 launch out of SLC-40 in Florida currently scheduled for 2024-08-31 07:43 UTC, or 2024-08-31 03:43 local time (EDT). Booster 1069-18 to land on Just Read the Instructions.

Webcasts:

view more: next ›