Live data from Hacker News

SpaceX Refused to Move Satellite at Risk of Collision with a European Satellite

forbes.com

11–20 of 229 posts

Re: SpaceX Refused to Move Satellite at Risk of Collision with a European Satellite

#13

From the twitter thread: It is very rare to perform collision avoidance manoeuvres with active satellites. The vast majority of ESA avoidance manoeuvres are the result of dead satellites or fragments from previous collisions. [ ... ] As the number of satellites in orbit increases, due to 'mega constellations' such as #Starlink comprising hundreds or even thousands of satellites, today's 'manual' collision avoidance p…

This is unreadable on mobile due to the use of code formatting. https://i.imgur.com/562ORgL.png EDIT: Said comment is now one full screen tall due to manual insertion of linewraps, and is very wasteful of space on desktop and landscape layouts: https://i.imgur.com/H15eCXo.png

It so weird that there is no incentive to fix many usability shortcomings like this one and too tiny UI elements on mobile etc. - all of that despite multiple complaints over years..

Re: SpaceX Refused to Move Satellite at Risk of Collision with a European Satellite

#14

From the twitter thread: It is very rare to perform collision avoidance manoeuvres with active satellites. The vast majority of ESA avoidance manoeuvres are the result of dead satellites or fragments from previous collisions. [ ... ] As the number of satellites in orbit increases, due to 'mega constellations' such as #Starlink comprising hundreds or even thousands of satellites, today's 'manual' collision avoidance p…

It is very rare to perform collision avoidance manoeuvres with active satellites. The vast majority of ESA avoidance manoeuvres are the result of dead satellites or fragments from previous collisions. [ ... ]

As the number of satellites in orbit increases, due to 'mega constellations' such as #Starlink comprising hundreds or even thousands of satellites, today's 'manual' collision avoidance process will become impossible...

Re: SpaceX Refused to Move Satellite at Risk of Collision with a European Satellite

#15

I wonder if AI is really the right tool to automate the process. Couldn’t it be done more robustly with a simple algorithm that takes todays collision probability models as input?

How much thrust? How high should it go? And on what information? Data sources will become more complex, risks need to be weighed. I'm not sure 'AI' is the right answer as most (all?) of AI is probably today just ML or more often simple BS - but certainly what ESA & co need won't be a simple one-variable algorithm.

I'm actually wondering if there's not a need to communicate more between all the bodies having satellites in space - just like autonomous cars, if both make an evasive maneuver they might cancel each other out. So there needs to be some kind of communication to avoid this.

Re: SpaceX Refused to Move Satellite at Risk of Collision with a European Satellite

#16
post #13

Earlier quoted context omitted.

This is unreadable on mobile due to the use of code formatting. https://i.imgur.com/562ORgL.png EDIT: Said comment is now one full screen tall due to manual insertion of linewraps, and is very wasteful of space on desktop and landscape layouts: https://i.imgur.com/H15eCXo.png

It so weird that there is no incentive to fix many usability shortcomings like this one and too tiny UI elements on mobile etc. - all of that despite multiple complaints over years..

It’s meant for code, where the browser isn’t necessary very good at wrapping lines.

Re: SpaceX Refused to Move Satellite at Risk of Collision with a European Satellite

#17
post #12

> In 2018, ESA performed 28 #collisionavoidance manoeuvres across its fleet.

One every two weeks (about) don't seem "rare" to me.

Its rare to have to avoid an active satellite, rather than random orbiting garbage.

Re: SpaceX Refused to Move Satellite at Risk of Collision with a European Satellite

#19
post #13

Earlier quoted context omitted.

This is unreadable on mobile due to the use of code formatting. https://i.imgur.com/562ORgL.png EDIT: Said comment is now one full screen tall due to manual insertion of linewraps, and is very wasteful of space on desktop and landscape layouts: https://i.imgur.com/H15eCXo.png

It so weird that there is no incentive to fix many usability shortcomings like this one and too tiny UI elements on mobile etc. - all of that despite multiple complaints over years..

Mobile works fine for me and the UI elements as shown honor my text size setting accurately. Using code formatting for non-code results in broken formatting for non-code. This should come as no surprise to anyone. Indents aren’t worth a semantic violation. Use “> ” prefixes like classic email, and optionally italic asterisks if that’s desirable.

Re: SpaceX Refused to Move Satellite at Risk of Collision with a European Satellite

#20
Of course, inside the article it’s explained that SpaceX didn’t “refuse” to move the satellite, they were politely asked to do so and declined for reasons the author is unaware of. Possibly because they couldn’t move the satellite or had a higher collision tolerance.
Post reply on HN