Beefy Boxes and Bandwidth Generously Provided by pair Networks
P is for Practical

Comment on

( #3333=superdoc: print w/replies, xml ) Need Help??
Where do I start?

I've never said that it is easy to dodge all space debris. What I've repeatedly said is that any individual known piece of space debris is easy to dodge. Which is true. I've also said that dodging an individual piece of debris is easier than removing it. Which is true. I've also said that collecting debris is easier than deorbiting it. Which is true for all but a handful of large pieces. And that handful is, of course, easy to dodge.

Of course this leaves the huge problems of debris you don't know about. It also ignores the scaling issue, which results from the fact that n satellites and m pieces of debris results in nm combinations that you have to keep track of. And you also have the problem that debris can hit debris, creating more debris.

And the Molinya orbit is a red herring if your aim is to arrange for low speed collisions with debris. (Which is what you were proposing it for.) Sure, your orbits intersect, but at the point of intersection your relative velocity is large. If you just want to intersect debris, then the Molinya orbit is not a bad idea. However you have the huge problem that a high speed impact between a solid object and debris is an event that is very, very likely to result in more orbiting debris, not less. If the solid object is a retired space shuttle, then I guarantee that you'll increase debris, not decrease it. While plenty of other objections can be leveled, that one alone is a deal breaker.

That looks like it addresses all of your points. Did I add any information I hadn't already provided? Unfortunately not. If you come up with another reply which is completely addressed by points I've already made repeatedly, I won't bother replying again.

In reply to Re^20: "Practices and Principles" to death by tilly
in thread "Practices and Principles" to death by ack

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.
  • Log In?

    What's my password?
    Create A New User
    and all is quiet...

    How do I use this? | Other CB clients
    Other Users?
    Others musing on the Monastery: (4)
    As of 2018-02-26 00:30 GMT
    Find Nodes?
      Voting Booth?
      When it is dark outside I am happiest to see ...

      Results (315 votes). Check out past polls.