{"action":"opened","issue":{"url":"https://api.github.com/repos/GalSim-developers/GalSim/issues/751","repository_url":"https://api.github.com/repos/GalSim-developers/GalSim","labels_url":"https://api.github.com/repos/GalSim-developers/GalSim/issues/751/labels{/name}","comments_url":"https://api.github.com/repos/GalSim-developers/GalSim/issues/751/comments","events_url":"https://api.github.com/repos/GalSim-developers/GalSim/issues/751/events","html_url":"https://github.com/GalSim-developers/GalSim/issues/751","id":155966330,"number":751,"title":"use LookupTable2D more consistently in python layer","user":{"login":"rmandelb","id":1454906,"avatar_url":"https://avatars.githubusercontent.com/u/1454906?v=3","gravatar_id":"","url":"https://api.github.com/users/rmandelb","html_url":"https://github.com/rmandelb","followers_url":"https://api.github.com/users/rmandelb/followers","following_url":"https://api.github.com/users/rmandelb/following{/other_user}","gists_url":"https://api.github.com/users/rmandelb/gists{/gist_id}","starred_url":"https://api.github.com/users/rmandelb/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rmandelb/subscriptions","organizations_url":"https://api.github.com/users/rmandelb/orgs","repos_url":"https://api.github.com/users/rmandelb/repos","events_url":"https://api.github.com/users/rmandelb/events{/privacy}","received_events_url":"https://api.github.com/users/rmandelb/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-05-20T13:44:34Z","updated_at":"2016-05-20T13:44:34Z","closed_at":null,"body":"Once #549 is merged, it would be nice to identify other places where we should be using LookupTable2D.  The example that comes to mind is ```lensing_ps.py```, where we have some kludgy use of InterpolatedImages that would make more sense as a LookupTable2D.  Are there other cases where this would be a useful change to make?"}}
{"actor":{"display_login":"rmandelb"}}