Email Detail

HTTP 200 OK
Allow: GET, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "url": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/43K2424CYLTPQO4VUI4UX5AWYUIR4HHR/",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/",
    "message_id": "[email protected]",
    "message_id_hash": "43K2424CYLTPQO4VUI4UX5AWYUIR4HHR",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/2A6XCU6JZG7FGIGHDULSE2IPEF4676Q4/",
    "sender": {
        "address": "wb4gcs (a) amsat.org",
        "mailman_id": "87014499e012476c8198fad186f7f963",
        "emails": "https://mailman.amsat.org/hyperkitty/api/sender/87014499e012476c8198fad186f7f963/emails/"
    },
    "sender_name": "Jim Sanford",
    "subject": "[eagle] Re: The thorny issue of SDX/Analog linear transpnder",
    "date": "2006-10-04T19:54:48Z",
    "parent": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/TNENTI5MVFDJVYQXCFU34CUDYL57XFGU/",
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "Bdale:\nYour asssessment of how we should do the risk analysis is EXACTLY the \nlevel I seek  -- we're not doing the space shuttle replacement.\n'\nIn my mind (?) when we have a few more systems and interfaces defined, \nI'd like to convene a team who's SOLE responsibility would be to do the \n\"what if\" on each failure, and somehow rank risk, probability, and \nconsequences.  Then they'd suggest mitigations that aren't already there. \n\nThanks & 73,\nJim\[email protected]\n\n\nBdale Garbee wrote:\n\n>On Tue, 2006-10-03 at 12:25 -0400, Louis McFadin wrote:\n>  \n>\n>>Martin is exactly right. Two of the same things is only partial\n>>redundancy. In order to be fully redundant the two systems must be\n>>independent, built by different teams and have different technology. \n>>    \n>>\n>\n>I think we should also remind ourselves that redundancy exists at\n>different levels of granularity.  For example, we might build more than\n>one unit of Eagle, P3E provides redundancy with Eagle and vice versa,\n>etc.\n>\n>It's important that we think through the various possible failure modes\n>and \"do the right thing\" to mitigate each, and maximize the probability\n>that we're left with something useful even if various important parts\n>fail.  However, if we insist on a mil-aero level of absolute redundancy\n>at too fine a level of granularity on a single satellite, we run a real\n>risk of specifying something we can't afford to build or fly.  Our prior\n>and future success hinge heavily, I think, on our collective ability to\n>be smart about these sorts of tradeoffs.\n>\n>Howard, if I were the one giving your talk this weekend I'd be inclined\n>to assert that reliability and redundancy are being considered at every\n>level of the Eagle project, but I wouldn't be inclined to commit us to\n>any particular technology path like promising an analog transponder as\n>backup.\n>\n>73 - Bdale, KB0G\n>\n>_______________________________________________\n>Via the Eagle mailing list courtesy of AMSAT-NA\n>[email protected]\n>http://amsat.org/mailman/listinfo/eagle\n>\n>  \n>\n\n\n",
    "attachments": [
        {
            "email": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/43K2424CYLTPQO4VUI4UX5AWYUIR4HHR/",
            "counter": 2,
            "name": "attachment.html",
            "content_type": "text/html",
            "encoding": "iso-8859-1",
            "size": 2709,
            "download": "https://mailman.amsat.org/hyperkitty/list/[email protected]/message/43K2424CYLTPQO4VUI4UX5AWYUIR4HHR/attachment/2/attachment.html"
        }
    ]
}