{"action":"created","issue":{"url":"https://api.github.com/repos/nsat/pypredict/issues/21","labels_url":"https://api.github.com/repos/nsat/pypredict/issues/21/labels{/name}","comments_url":"https://api.github.com/repos/nsat/pypredict/issues/21/comments","events_url":"https://api.github.com/repos/nsat/pypredict/issues/21/events","html_url":"https://github.com/nsat/pypredict/issues/21","id":66985070,"number":21,"title":"Wrong results .. comparison with gpredict and pyephem","user":{"login":"alexschultze","id":4873079,"avatar_url":"https://avatars.githubusercontent.com/u/4873079?v=3","gravatar_id":"","url":"https://api.github.com/users/alexschultze","html_url":"https://github.com/alexschultze","followers_url":"https://api.github.com/users/alexschultze/followers","following_url":"https://api.github.com/users/alexschultze/following{/other_user}","gists_url":"https://api.github.com/users/alexschultze/gists{/gist_id}","starred_url":"https://api.github.com/users/alexschultze/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/alexschultze/subscriptions","organizations_url":"https://api.github.com/users/alexschultze/orgs","repos_url":"https://api.github.com/users/alexschultze/repos","events_url":"https://api.github.com/users/alexschultze/events{/privacy}","received_events_url":"https://api.github.com/users/alexschultze/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-04-07T20:39:27Z","updated_at":"2015-12-02T13:48:54Z","closed_at":null,"body":"I recently started to try to compare a specific observation to see how the different free programs perform. I could not get the right value out ouf pypredict. The complete observation Is in the second post here:\r\nhttps://stackoverflow.com/questions/18763484/wrong-range-rate-with-pyephem/29500861#29500861\r\n\r\nYour input is very welcome. :)"},"comment":{"url":"https://api.github.com/repos/nsat/pypredict/issues/comments/161295818","html_url":"https://github.com/nsat/pypredict/issues/21#issuecomment-161295818","issue_url":"https://api.github.com/repos/nsat/pypredict/issues/21","id":161295818,"user":{"login":"LongHairedHacker","id":1888799,"avatar_url":"https://avatars.githubusercontent.com/u/1888799?v=3","gravatar_id":"","url":"https://api.github.com/users/LongHairedHacker","html_url":"https://github.com/LongHairedHacker","followers_url":"https://api.github.com/users/LongHairedHacker/followers","following_url":"https://api.github.com/users/LongHairedHacker/following{/other_user}","gists_url":"https://api.github.com/users/LongHairedHacker/gists{/gist_id}","starred_url":"https://api.github.com/users/LongHairedHacker/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/LongHairedHacker/subscriptions","organizations_url":"https://api.github.com/users/LongHairedHacker/orgs","repos_url":"https://api.github.com/users/LongHairedHacker/repos","events_url":"https://api.github.com/users/LongHairedHacker/events{/privacy}","received_events_url":"https://api.github.com/users/LongHairedHacker/received_events","type":"User","site_admin":false},"created_at":"2015-12-02T13:48:54Z","updated_at":"2015-12-02T13:48:54Z","body":"I can confirm this.\r\n\r\nComparing with gpredict the timing is off about a few minutes as well as all the peak elevation values.\r\nBased on the sattelite signals I captured, the gepredict values should be correct."}}