Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Ulrich Speidel <u.speidel@auckland.ac.nz>
To: "blakangel@gmail.com" <blakangel@gmail.com>, David Lang <david@lang.hm>
Cc: "starlink@lists.bufferbloat.net" <starlink@lists.bufferbloat.net>,
	Daniel AJ Sokolov <daniel@falco.ca>
Subject: Re: [Starlink] orbital maneuvers 12 per sat in the last 6 months
Date: Fri, 7 Jul 2023 22:28:26 +0000	[thread overview]
Message-ID: <SY4PR01MB6979AF7082BE0F944BF491C7CE2DA@SY4PR01MB6979.ausprd01.prod.outlook.com> (raw)
In-Reply-To: <qn00n610-9125-q21s-9o98-797087o504o4@ynat.uz>

[-- Attachment #1: Type: text/plain, Size: 5213 bytes --]

Now there is the misuse of the expression "exponentially" in cases when people just mean "a bit faster than before". If you have a time series 1, 2, 4, 6, 8 then you could claim that it's exponential because the first three terms double each time, yet the last four terms could be used to claim that it's linear.

Plus, exponential growth doesn't necessarily mean fast growth. Your 2020 term deposit for 5 years at 1% interest rate with interest reinvested sees your money growing exponentially, too. This is perhaps why decision-makers from the economics sphere tend to get caught out be fast exponential growth (the sort of growth us science and engineering folk tend to think of).

Beyond that: I'm not sure that I can make much of orbital maneuver numbers. Even GEO sats - for which collision probability is very low - undertake regular corrective maneuvers for station-keeping. For anything further down, a maneuver could be a short-term evasive action, a longer term orbit injection or change maneuver, or corrective action to any of these.

Each maneuver uses some of the satellite's propellant reserve. As a general rule, a maneuver executed over a longer period of time is more fuel efficient: A small change in a satellite's trajectory now can lead to a large change down the time axis, with very little propellant use - think Starlink satellites transitioning from launch train to final station over months. Making small corrective adjustments to this over time might bring the total number of maneuvers up, too. Conversely, large short-term corrections dip into fuel reserves, which can impact on service life. So you'd really need to ask which sort of maneuvers these are, and how much each maneuver costs in terms of service life.

--
****************************************************************
Dr. Ulrich Speidel

Department of Computer Science

Room 303S.594
Ph: (+64-9)-373-7599 ext. 85282

The University of Auckland
u.speidel@auckland.ac.nz<mailto:u.speidel@auckland.ac.nz>
http://www.cs.auckland.ac.nz/~ulrich/<http://www.cs.auckland.ac.nz/%7Eulrich/>
****************************************************************
________________________________
From: Starlink <starlink-bounces@lists.bufferbloat.net> on behalf of David Lang via Starlink <starlink@lists.bufferbloat.net>
Sent: Friday, July 7, 2023 6:02 PM
To: blakangel@gmail.com <blakangel@gmail.com>
Cc: starlink@lists.bufferbloat.net <starlink@lists.bufferbloat.net>; Daniel AJ Sokolov <daniel@falco.ca>
Subject: Re: [Starlink] orbital maneuvers 12 per sat in the last 6 months

they have been filling shells (altitude sets), so it makes sense for the numbers
to have been going up.

we'll have to see if they keep going up as much as they move on to different
altitude shells.

David Lang

On Thu, 6 Jul 2023, blakangel@gmail.com wrote:

> I think the main point of the article is that the amount of maneuvers needed
> is currently increasing exponentially: "It's been doubling every six months,
> and the problem with exponential trends is that they get to very large
> numbers very quickly." I'm wondering if they are not taking into account the
> massive amount of satellites that have been launched since the previous six
> month report.
>
> I found the semi-annual reports filed w/ the fcc:
> https://licensing.fcc.gov/myibfs/download.do?attachment_key=23204343<https://licensing.fcc.gov/myibfs/download.do?attachment_key=23204343> and
> https://licensing.fcc.gov/myibfs/download.do?attachment_key=23204338<https://licensing.fcc.gov/myibfs/download.do?attachment_key=23204338> for gen
> 1 and gen 2 constellations.
>
> Still reading them and haven't found the older ones yet to compare.
>
>
> David Lang via Starlink wrote on 7/6/2023 9:49 PM:
>
>> some people are assuming that more satellites launched will mean more
>> maneuvers needed (not recognizing that what matters is only the things at
>> the same altitude)
>>
>> plus, it's a scary large number :-)
>>
>> David Lang
>>
>>  On Thu, 6 Jul 2023, Daniel AJ Sokolov via Starlink wrote:
>>
>>> On 7/6/23 17:54, Dave Taht via Starlink wrote:
>>>>
>>> https://www.space.com/starlink-satellite-conjunction-increase-threatens-space-sustainability<https://www.space.com/starlink-satellite-conjunction-increase-threatens-space-sustainability>
>>>>
>>>> I am under the impression that each sat is capable of about 500 over
>>>> the satellite's lifetime. I am curious as to what they are avoiding.
>>>
>>> Assuming your number of 500 is correct, I don't see any worry here. 12
>>> moves in 6 months makes 492 in 20.5 years. That is less than 500 and
>>> beyond the lifetime expectation of the satellite anyway.
>>>
>>> A I missing something?
>>> Daniel AJ
>>> _______________________________________________
>>> Starlink mailing list
>>> Starlink@lists.bufferbloat.net
>>> https://lists.bufferbloat.net/listinfo/starlink<https://lists.bufferbloat.net/listinfo/starlink>
>>>
>> _______________________________________________
>> Starlink mailing list
>> Starlink@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/starlink<https://lists.bufferbloat.net/listinfo/starlink>
>
>

[-- Attachment #2: Type: text/html, Size: 8167 bytes --]

  reply	other threads:[~2023-07-07 22:28 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 [this message]
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
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=SY4PR01MB6979AF7082BE0F944BF491C7CE2DA@SY4PR01MB6979.ausprd01.prod.outlook.com \
    --to=u.speidel@auckland.ac.nz \
    --cc=blakangel@gmail.com \
    --cc=daniel@falco.ca \
    --cc=david@lang.hm \
    --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