Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Jonathan Morton <chromatix99@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: Jim Gettys <jg@freedesktop.org>, cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] spacebee
Date: Wed, 14 Mar 2018 03:49:32 +0200	[thread overview]
Message-ID: <B6195ECC-2E0E-44E6-87BA-D78432151E56@gmail.com> (raw)
In-Reply-To: <CAA93jw6U7cBrnJcqqNyAnst9uAwsOj_==CzUc57NNHahM_zf2Q@mail.gmail.com>

> On 13 Mar, 2018, at 7:31 pm, Dave Taht <dave.taht@gmail.com> wrote:
> 
>> Size, until the object gets really small, really doesn't matter.
> 
> The odds of a collision drop proportionally (what's the math?) to
> size. Imagine useful sats this small, or smaller, in lower orbits that
> burn up in a few years, and constant replacement and technological
> refreshment...

Observation: we're talking about an object that's substantially bigger than a bullet, substantially heavier than a bullet, and travelling *faster* than a bullet.  Collisions with such an object would be extremely high-energy, and spacecraft don't have the weight budget for the tank-grade armour required to survive such an impact.

I don't think the occupants of the ISS would be very happy with being hit by a titanium cricket ball at 10,000 kph relative.

Also, the probability of collision, given random trajectories, depends on the sizes of *both* objects involved - and rather more strongly on the size of the *larger* object.  If you reduce the size of a 10cm object by 50%, it has much less effect on the combined collision radius than reducing the size of a 10m object by 50%.

 - Jonathan Morton


  reply	other threads:[~2018-03-14  1:49 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-12  4:13 Dave Taht
2018-03-12 16:25 ` dpreed
2018-03-13 18:31   ` Dave Taht
2018-03-12 16:26 ` Jim Gettys
2018-03-12 17:18   ` dpreed
2018-03-12 17:34     ` Christopher Robin
2018-03-12 19:10       ` dpreed
2018-03-12 20:29         ` Christopher Robin
2018-03-13 16:12           ` Jim Gettys
2018-03-13 16:52             ` Dave Taht
2018-03-13 17:03               ` Jim Gettys
2018-03-13 17:31                 ` Dave Taht
2018-03-14  1:49                   ` Jonathan Morton [this message]
2018-03-13 17:47                 ` Christopher Robin
2018-03-13 18:25                   ` Dave Taht
2018-03-14  4:16                   ` Matt Taggart
2018-03-13 17:49               ` valdis.kletnieks
2018-03-13 18:06                 ` Dave Taht
2018-03-14  4:08                   ` Matt Taggart
2018-03-15 20:22               ` Ray Ramadorai

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/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=B6195ECC-2E0E-44E6-87BA-D78432151E56@gmail.com \
    --to=chromatix99@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=jg@freedesktop.org \
    /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