From: <tom@evslin.com>
To: "'Mike Puchol'" <mike@starlink.sx>, <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] orbital maneuvers 12 per sat in the last 6 months
Date: Fri, 7 Jul 2023 08:51:10 -0400 [thread overview]
Message-ID: <5c1e901d9b0d1$b49d6e50$1dd84af0$@evslin.com> (raw)
In-Reply-To: <e1d88f8e-6afb-4ea7-a99c-bbbc9e35c5bc@Spark>
[-- Attachment #1: Type: text/plain, Size: 1835 bytes --]
Great visualization. Dumb question but I can’t figure it out. What are the orange planes labeled “instruments”? They are obviously related o the beams below them but I’m not sure what they are either.
Thank you
From: Starlink <starlink-bounces@lists.bufferbloat.net> On Behalf Of Mike Puchol via Starlink
Sent: Friday, July 7, 2023 2:35 AM
To: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] orbital maneuvers 12 per sat in the last 6 months
Profession Hugh Lewis follows Starlink’s conjuction reports closely, and writes very detailed threads whenever a report comes up:
https://twitter.com/ProfHughLewis
Latest thread:
https://twitter.com/ProfHughLewis/status/1658173801924812803
If you want an idea of -what- they are avoiding, LeoLabs operates a set of radars which track anything larger than 10cm in cross-section, and provides an awesome visualization here:
https://platform.leolabs.space/visualization
(make sure to enable the “debris” checkbox too)
Best,
Mike
On Jul 7, 2023 at 08:23 +0200, Daniel AJ Sokolov via Starlink <starlink@lists.bufferbloat.net>, wrote:
On 7/6/23 22:28, blakangel@gmail.com <mailto:blakangel@gmail.com> wrote:
I think the main point of the article is that the amount of maneuvers
needed is currently increasing exponentially:
Indeed, I read that. But the article does not explain why they think
this trend will continue exponentially.
Obviously it can't continue exponentially forever, because eventually
all satellites are on the move evading one another 100% of the time. :-)
Cheers
Daniel
_______________________________________________
Starlink mailing list
Starlink@lists.bufferbloat.net <mailto:Starlink@lists.bufferbloat.net>
https://lists.bufferbloat.net/listinfo/starlink
[-- Attachment #2: Type: text/html, Size: 4425 bytes --]
next prev parent reply other threads:[~2023-07-07 12:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-07 0:54 Dave Taht
2023-07-07 1:01 ` Daniel AJ Sokolov
2023-07-07 4:49 ` David Lang
2023-07-07 5:28 ` blakangel
2023-07-07 6:02 ` David Lang
2023-07-07 22:28 ` Ulrich Speidel
2023-07-08 14:06 ` Dave Taht
2023-07-08 20:49 ` David Lang
2023-07-07 6:23 ` Daniel AJ Sokolov
2023-07-07 6:34 ` Mike Puchol
2023-07-07 7:13 ` Daniel AJ Sokolov
2023-07-07 7:22 ` Mike Puchol
2023-07-07 12:51 ` tom [this message]
2023-07-07 13:18 ` Mike Puchol
2023-07-08 13:53 ` Larry Press
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/starlink.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='5c1e901d9b0d1$b49d6e50$1dd84af0$@evslin.com' \
--to=tom@evslin.com \
--cc=mike@starlink.sx \
--cc=starlink@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox