{"action":"created","issue":{"url":"https://api.github.com/repos/Astroua/CARTAvis/issues/113","labels_url":"https://api.github.com/repos/Astroua/CARTAvis/issues/113/labels{/name}","comments_url":"https://api.github.com/repos/Astroua/CARTAvis/issues/113/comments","events_url":"https://api.github.com/repos/Astroua/CARTAvis/issues/113/events","html_url":"https://github.com/Astroua/CARTAvis/issues/113","id":119100538,"number":113,"title":"Storing some key file locations in a preferences file","user":{"login":"durga2112","id":4204212,"avatar_url":"https://avatars.githubusercontent.com/u/4204212?v=3","gravatar_id":"","url":"https://api.github.com/users/durga2112","html_url":"https://github.com/durga2112","followers_url":"https://api.github.com/users/durga2112/followers","following_url":"https://api.github.com/users/durga2112/following{/other_user}","gists_url":"https://api.github.com/users/durga2112/gists{/gist_id}","starred_url":"https://api.github.com/users/durga2112/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/durga2112/subscriptions","organizations_url":"https://api.github.com/users/durga2112/orgs","repos_url":"https://api.github.com/users/durga2112/repos","events_url":"https://api.github.com/users/durga2112/events{/privacy}","received_events_url":"https://api.github.com/users/durga2112/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-11-26T20:43:50Z","updated_at":"2015-11-27T16:17:38Z","closed_at":null,"body":"The cartaview() task that I am developing for CASA currently has the following parameters:\r\n\r\n`raster` - The full path of a compatible image file to load.\r\n`executable` - The full path of the Carta executable file.\r\n`configFile` - The full path of the cartavis config.json file.\r\n`port` - The port which will be used to send commands to Carta and receive results.\r\n`htmlFile` - The full path of the Carta desktopIndex.html file.\r\n\r\nIn the interest of making this task as easy to set up as possible, @low-sky has suggested storing most of these values in a preferences file - possibly even the config.json file itself - which could be polled by the cartaview() task instead of relying on the user figuring out which port to use, where the executable is located, etc. This file would be set on the first time CARTA is run post installation on a machine.\r\n\r\nDoes anyone have any thoughts on how this could be set up?\r\n\r\n@astrilet @pfederl @slovelan @JimNrao (have I forgotten anyone?)\r\n"},"comment":{"url":"https://api.github.com/repos/Astroua/CARTAvis/issues/comments/160168914","html_url":"https://github.com/Astroua/CARTAvis/issues/113#issuecomment-160168914","issue_url":"https://api.github.com/repos/Astroua/CARTAvis/issues/113","id":160168914,"user":{"login":"astrilet","id":11414991,"avatar_url":"https://avatars.githubusercontent.com/u/11414991?v=3","gravatar_id":"","url":"https://api.github.com/users/astrilet","html_url":"https://github.com/astrilet","followers_url":"https://api.github.com/users/astrilet/followers","following_url":"https://api.github.com/users/astrilet/following{/other_user}","gists_url":"https://api.github.com/users/astrilet/gists{/gist_id}","starred_url":"https://api.github.com/users/astrilet/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/astrilet/subscriptions","organizations_url":"https://api.github.com/users/astrilet/orgs","repos_url":"https://api.github.com/users/astrilet/repos","events_url":"https://api.github.com/users/astrilet/events{/privacy}","received_events_url":"https://api.github.com/users/astrilet/received_events","type":"User","site_admin":false},"created_at":"2015-11-27T16:17:38Z","updated_at":"2015-11-27T16:17:38Z","body":"port - can be stored in config.json\n htmlFile, executable - it all depends on where it is installed, in my bash\nconfig file I have variable $CARTAROOT which points to the root of\ninstallation, then htmlFile and executable are easily referenced relatively\nto that path.\nNot a good idea to store it in config.json as it might be dependant on user\ninstallation.\nconfigFile - usually in the user $HOME/.cartavis by default but what is the\npoint of storing it in confug.json file if you  need that variable to find\nconfig.json to begin with, we can safely assume that it is always there.\n\nraster - every user will have different image files, how can we make sure\nthat everyone has specific image file, in our carta instlation we provide\nsample images in $HOME/CARTA/Images directory. Does casa installation\nprovide some common image files?\n\n\n\nOn Thu, Nov 26, 2015 at 1:43 PM, Jeff Taylor <notifications@github.com>\nwrote:\n\n> The cartaview() task that I am developing for CASA currently has the\n> following parameters:\n>\n> raster - The full path of a compatible image file to load.\n> executable - The full path of the Carta executable file.\n> configFile - The full path of the cartavis config.json file.\n> port - The port which will be used to send commands to Carta and receive\n> results.\n> htmlFile - The full path of the Carta desktopIndex.html file.\n>\n> In the interest of making this task as easy to set up as possible,\n> @low-sky <https://github.com/low-sky> has suggested storing most of these\n> values in a preferences file - possibly even the config.json file itself -\n> which could be polled by the cartaview() task instead of relying on the\n> user figuring out which port to use, where the executable is located, etc.\n> This file would be set on the first time CARTA is run post installation on\n> a machine.\n>\n> Does anyone have any thoughts on how this could be set up?\n>\n> @astrilet <https://github.com/astrilet> @pfederl\n> <https://github.com/pfederl> @slovelan <https://github.com/slovelan>\n> @JimNrao <https://github.com/JimNrao> (have I forgotten anyone?)\n>\n> —\n> Reply to this email directly or view it on GitHub\n> <https://github.com/Astroua/CARTAvis/issues/113>.\n>\n"}}