{"action":"created","issue":{"url":"https://api.github.com/repos/soft-matter/trackpy/issues/213","labels_url":"https://api.github.com/repos/soft-matter/trackpy/issues/213/labels{/name}","comments_url":"https://api.github.com/repos/soft-matter/trackpy/issues/213/comments","events_url":"https://api.github.com/repos/soft-matter/trackpy/issues/213/events","html_url":"https://github.com/soft-matter/trackpy/issues/213","id":59357499,"number":213,"title":"diag.dependencies() availability? vs documentation","user":{"login":"apiszcz","id":1430861,"avatar_url":"https://avatars.githubusercontent.com/u/1430861?v=3","gravatar_id":"","url":"https://api.github.com/users/apiszcz","html_url":"https://github.com/apiszcz","followers_url":"https://api.github.com/users/apiszcz/followers","following_url":"https://api.github.com/users/apiszcz/following{/other_user}","gists_url":"https://api.github.com/users/apiszcz/gists{/gist_id}","starred_url":"https://api.github.com/users/apiszcz/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/apiszcz/subscriptions","organizations_url":"https://api.github.com/users/apiszcz/orgs","repos_url":"https://api.github.com/users/apiszcz/repos","events_url":"https://api.github.com/users/apiszcz/events{/privacy}","received_events_url":"https://api.github.com/users/apiszcz/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":15,"created_at":"2015-02-28T20:43:03Z","updated_at":"2015-03-19T05:58:40Z","closed_at":"2015-03-18T14:40:00Z","body":"The documentation states there is a diag.dependencies()  in the section. \r\n\r\nDiagnostic functions\r\ndiag.performance_report()\tDisplay summary of which optional speedups are installed/enabled\r\ndiag.dependencies()\tGive the version of each of the dependencies – useful for bug reports.\r\nHowever the function does not appear to be int eh diag.py module.\r\n\r\n(Pdb) pprint.pprint(dir(tpdiag))\r\n['__builtins__',\r\n '__doc__',\r\n '__file__',\r\n '__name__',\r\n '__package__',\r\n '__version__',\r\n 'absolute_import',\r\n 'division',\r\n 'performance_report',\r\n 'preprocessing',\r\n 'print_function',\r\n 'six',\r\n 'try_numba',\r\n 'unicode_literals']\r\n(Pdb) tp.__version__\r\n'0.2.4'\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/soft-matter/trackpy/issues/comments/83350220","html_url":"https://github.com/soft-matter/trackpy/issues/213#issuecomment-83350220","issue_url":"https://api.github.com/repos/soft-matter/trackpy/issues/213","id":83350220,"user":{"login":"apiszcz","id":1430861,"avatar_url":"https://avatars.githubusercontent.com/u/1430861?v=3","gravatar_id":"","url":"https://api.github.com/users/apiszcz","html_url":"https://github.com/apiszcz","followers_url":"https://api.github.com/users/apiszcz/followers","following_url":"https://api.github.com/users/apiszcz/following{/other_user}","gists_url":"https://api.github.com/users/apiszcz/gists{/gist_id}","starred_url":"https://api.github.com/users/apiszcz/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/apiszcz/subscriptions","organizations_url":"https://api.github.com/users/apiszcz/orgs","repos_url":"https://api.github.com/users/apiszcz/repos","events_url":"https://api.github.com/users/apiszcz/events{/privacy}","received_events_url":"https://api.github.com/users/apiszcz/received_events","type":"User","site_admin":false},"created_at":"2015-03-19T05:58:40Z","updated_at":"2015-03-19T05:58:40Z","body":"thanks will give it some time and test.\n\n\n\n\n\n\nOn Mar 18, 2015, at 18:59, Nathan Keim <notifications@github.com> wrote:\n\nI'm not sure I understand. NearestVelocityPredict is supposed to use each\nparticle's own distinct velocity (unless the particle is new). The velocity\nof other, nearby particles should be irrelevant.\n\n—\nReply to this email directly or view it on GitHub\n<https://github.com/soft-matter/trackpy/issues/213#issuecomment-83218600>.\n"}}