{"action":"created","issue":{"url":"https://api.github.com/repos/GBTAmmoniaSurvey/GAS/issues/11","labels_url":"https://api.github.com/repos/GBTAmmoniaSurvey/GAS/issues/11/labels{/name}","comments_url":"https://api.github.com/repos/GBTAmmoniaSurvey/GAS/issues/11/comments","events_url":"https://api.github.com/repos/GBTAmmoniaSurvey/GAS/issues/11/events","html_url":"https://github.com/GBTAmmoniaSurvey/GAS/issues/11","id":62413761,"number":11,"title":"How to store fit parameters?","user":{"login":"jpinedaf","id":6529114,"avatar_url":"https://avatars.githubusercontent.com/u/6529114?v=3","gravatar_id":"","url":"https://api.github.com/users/jpinedaf","html_url":"https://github.com/jpinedaf","followers_url":"https://api.github.com/users/jpinedaf/followers","following_url":"https://api.github.com/users/jpinedaf/following{/other_user}","gists_url":"https://api.github.com/users/jpinedaf/gists{/gist_id}","starred_url":"https://api.github.com/users/jpinedaf/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jpinedaf/subscriptions","organizations_url":"https://api.github.com/users/jpinedaf/orgs","repos_url":"https://api.github.com/users/jpinedaf/repos","events_url":"https://api.github.com/users/jpinedaf/events{/privacy}","received_events_url":"https://api.github.com/users/jpinedaf/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/GBTAmmoniaSurvey/GAS/labels/enhancement","name":"enhancement","color":"84b6eb"},{"url":"https://api.github.com/repos/GBTAmmoniaSurvey/GAS/labels/question","name":"question","color":"cc317c"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-03-17T14:31:04Z","updated_at":"2015-06-22T10:50:43Z","closed_at":null,"body":"I was wondering what is the best option to store the best fit parameters. Currently, PropertyMaps.py creates a single FITS file with each plane representing one best fit parameter or its associated uncertainty. Should it be better to store each parameter in a different HDU within the FITS file? This is similar to the Herschel data format. In this way, we can change the BUNIT keyword to represent the real unit of the fit parameter.\r\n\r\nOne clear disadvantage is that casaviewer does not work really well with it. In ds9 or casaviewer we can just change the channel to see the different parameters. What are your thoughts @low-sky @rfriesen ?\r\n\r\nWe should think about the impact on other team members... i.e. how easy would it be for them to understand and/or access the results.?"},"comment":{"url":"https://api.github.com/repos/GBTAmmoniaSurvey/GAS/issues/comments/114064371","html_url":"https://github.com/GBTAmmoniaSurvey/GAS/issues/11#issuecomment-114064371","issue_url":"https://api.github.com/repos/GBTAmmoniaSurvey/GAS/issues/11","id":114064371,"user":{"login":"jpinedaf","id":6529114,"avatar_url":"https://avatars.githubusercontent.com/u/6529114?v=3","gravatar_id":"","url":"https://api.github.com/users/jpinedaf","html_url":"https://github.com/jpinedaf","followers_url":"https://api.github.com/users/jpinedaf/followers","following_url":"https://api.github.com/users/jpinedaf/following{/other_user}","gists_url":"https://api.github.com/users/jpinedaf/gists{/gist_id}","starred_url":"https://api.github.com/users/jpinedaf/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jpinedaf/subscriptions","organizations_url":"https://api.github.com/users/jpinedaf/orgs","repos_url":"https://api.github.com/users/jpinedaf/repos","events_url":"https://api.github.com/users/jpinedaf/events{/privacy}","received_events_url":"https://api.github.com/users/jpinedaf/received_events","type":"User","site_admin":false},"created_at":"2015-06-22T10:50:43Z","updated_at":"2015-06-22T10:50:43Z","body":"It is as easy to make one file per parameter, as it is to make a multi-HDU\nfile. I see the problem of opening multi-HDU files in CASA as a good reason\nto go with the former option.\n\nOn Sun, Jun 21, 2015 at 4:22 AM Erik Rosolowsky <notifications@github.com>\nwrote:\n\n> I'd lean toward one file per parameter, but I'm okay with one HDU per\n> parameter too. Better than a cube, for sure. I see good things with\n> multi-HDU files being that everything is in one place and versioning is\n> easier.\n>\n> —\n> Reply to this email directly or view it on GitHub\n> <https://github.com/GBTAmmoniaSurvey/GAS/issues/11#issuecomment-113853629>\n> .\n>\n"}}