{"action":"closed","issue":{"url":"https://api.github.com/repos/adrn/gary/issues/20","labels_url":"https://api.github.com/repos/adrn/gary/issues/20/labels{/name}","comments_url":"https://api.github.com/repos/adrn/gary/issues/20/comments","events_url":"https://api.github.com/repos/adrn/gary/issues/20/events","html_url":"https://github.com/adrn/gary/issues/20","id":52058938,"number":20,"title":"Is there a better way to handle coordinates in Potential classes?","user":{"login":"adrn","id":583379,"avatar_url":"https://avatars.githubusercontent.com/u/583379?v=3","gravatar_id":"","url":"https://api.github.com/users/adrn","html_url":"https://github.com/adrn","followers_url":"https://api.github.com/users/adrn/followers","following_url":"https://api.github.com/users/adrn/following{/other_user}","gists_url":"https://api.github.com/users/adrn/gists{/gist_id}","starred_url":"https://api.github.com/users/adrn/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/adrn/subscriptions","organizations_url":"https://api.github.com/users/adrn/orgs","repos_url":"https://api.github.com/users/adrn/repos","events_url":"https://api.github.com/users/adrn/events{/privacy}","received_events_url":"https://api.github.com/users/adrn/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/adrn/gary/labels/enhancement","name":"enhancement","color":"84b6eb"}],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2014-12-16T00:36:59Z","updated_at":"2015-11-30T22:23:45Z","closed_at":"2015-11-30T22:23:45Z","body":"Right now, all potentials are subclasses of Cartesian potentials so that, for example, even in spherical potentials, the user has to specify a full 3D position for each. Is there a better way to handle this so that a spherical potential can be used as 1D? Or, should the classes support Astropy coordinate `representation`s so the class evaluations can accept, e.g., spherical and cartesian?"}}