Show an email

GET /hyperkitty/api/list/[email protected]/email/BGVMUTYJGUKKYHBJHE2MDMFDD52CPOUA/?format=api
HTTP 200 OK
Allow: GET, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "url": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/BGVMUTYJGUKKYHBJHE2MDMFDD52CPOUA/?format=api",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/?format=api",
    "message_id": "003c01cac454$7f913480$7eb39d80$@com",
    "message_id_hash": "BGVMUTYJGUKKYHBJHE2MDMFDD52CPOUA",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/4YAQ6WJ52QA46R3IFNDAGYUYTF4CMT3I/?format=api",
    "sender": {
        "address": "howard (a) howardlong.com",
        "mailman_id": "82a1d3d58c6f48898b755d208f81930e",
        "emails": "https://mailman.amsat.org/hyperkitty/api/sender/82a1d3d58c6f48898b755d208f81930e/emails/?format=api"
    },
    "sender_name": "Howard Long",
    "subject": "[amsat-bb] Re: use of PI in amsat development practice",
    "date": "2010-03-15T15:30:52Z",
    "parent": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/MIAF7FIPQGSN2LHUG6ZC4A2X3EHSZZA3/?format=api",
    "children": [
        "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/BWYSUAQHYXGTTRBRY4JFO6VDF4X4XRSS/?format=api"
    ],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "Bruce\n\n> What an interesting question! As many of you know, I'm having fun\n> porting the G3RUH's Plan13 algorithm to the Atmel platform. One of the\n> first things you want to be able to do in programs like this is to\n> convert degrees to radians; and that means pi.\n\nFWIW I used 32 bit accuracy (equivalent to IEEE754 single precision) in my\nPIC LVB Tracker 2 code (based on G3RUH Plan13 too) without any significant\ndifference in results over 64 bit. Although the accuracy did cause some\nanomalies, they were small and inconsequential for amateur purposes,\ntypically a second or two in predictions. I tested this by running the same\ncode on a PC and carefully coding constants, stored values and datatypes\nwith #defines so I could recompile on demand and see the differences in the\nresults.\n\nI was lucky, ISTR I had 3.5KB, but even that was a struggle, although I did\nhave the additional dimension of having to deal with manual bank switching\ntoo of the PIC18 - you might not have this on your device. And the compiler\nI used, although generating very compact code, wouldn't compile anything\nslightly complex, so I had to manually split the statements into simpler\nsteps.\n\nIf I did it again, I'd head for at least a 16 bit and probably a 32 bit\ndevice, and a different compiler. But five plus years ago we didn't have\nsuch devices or capabilities!\n\n73, Howard G6LVB\n\n\n",
    "attachments": []
}