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/G37CYB4EVXY6UQHVSW5QWOUPFC3L7ZNZ/",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/",
    "message_id": "[email protected]",
    "message_id_hash": "G37CYB4EVXY6UQHVSW5QWOUPFC3L7ZNZ",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/G37CYB4EVXY6UQHVSW5QWOUPFC3L7ZNZ/",
    "sender": {
        "address": "phillor (a) telstra.com",
        "mailman_id": null,
        "emails": null
    },
    "sender_name": "Phil",
    "subject": "[amsat-bb]  Programming question - frequency units",
    "date": "2009-12-16T07:49:45Z",
    "parent": null,
    "children": [
        "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/FSBZRZHEVGA33572T4BXRODYIF743YK4/"
    ],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "Thank you for reading this.\n\nAfter a five year rest from the satellites I may soon be in a position to once \nagain resume one of my favourite hobbies. So, over the past couple of \nmonths I have been updating my tracking programme. In the process I have \ndiscovered that I need to make a design change.\n\nOriginally the whole programme used Hertz as the frequency unit until \nAO-40 came along and the numbers became too large for the int variables. \nIt wasn't too difficult, at the time, to change to long variables but I found \nthe long strings of numbers confusing especially in the configuration file. So \nthen I experimented with double variables in Kilohertz. Around the same \ntime AO-40 died and a lifestyle change ended my access to all satellites as \nwell.\n\nI've rewritten the configuration class and modelled it around Erich \nEichmann's sqf Doppler file which has made selecting satellites with multiple \nmodes neater. This is where the design decision comes in.\n\nThe main class now uses Kilohertz as the frequency unit while the radio \nclass still uses Hertz. The main class is responsible for the conversion each \nway but confusion reigns supreme because some variables are in Hertz and \nothers in Kilohertz. This is currently causing me a problem where I'm \nmodifying the code that takes care of calculating a new uplink frequency \nwhen the receiver VFO dial is moved.\n\nIt seems to me that the best idea is to rewrite the radio class so that it \naccepts double type Kilohertz parameters. This introduces minor frequency \nerrors of a few Hertz due to rounding errors but I don't think that is a \nproblem since my FT-847 only has a ten Hertz resolution anyway.\n\nAlternatively, I could convert the double frequencies in the configuration \nclass to longs and use long variables in all other classes. This will now be a \nmore difficult and error prone task to undertake.\n\nTo answer my own question, I think working in Kilohertz might be the best \noption but I'd still like to know how others have handled frequency units.  \n\n-- \nRegards,\nPhil\n",
    "attachments": []
}