{"action":"created","issue":{"url":"https://api.github.com/repos/QuantEcon/QuantEcon.py/issues/74","labels_url":"https://api.github.com/repos/QuantEcon/QuantEcon.py/issues/74/labels{/name}","comments_url":"https://api.github.com/repos/QuantEcon/QuantEcon.py/issues/74/comments","events_url":"https://api.github.com/repos/QuantEcon/QuantEcon.py/issues/74/events","html_url":"https://github.com/QuantEcon/QuantEcon.py/pull/74","id":41600251,"number":74,"title":"Add solow model","user":{"login":"davidrpugh","id":2219562,"avatar_url":"https://avatars.githubusercontent.com/u/2219562?v=3","gravatar_id":"","url":"https://api.github.com/users/davidrpugh","html_url":"https://github.com/davidrpugh","followers_url":"https://api.github.com/users/davidrpugh/followers","following_url":"https://api.github.com/users/davidrpugh/following{/other_user}","gists_url":"https://api.github.com/users/davidrpugh/gists{/gist_id}","starred_url":"https://api.github.com/users/davidrpugh/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/davidrpugh/subscriptions","organizations_url":"https://api.github.com/users/davidrpugh/orgs","repos_url":"https://api.github.com/users/davidrpugh/repos","events_url":"https://api.github.com/users/davidrpugh/events{/privacy}","received_events_url":"https://api.github.com/users/davidrpugh/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":35,"created_at":"2014-09-01T00:43:35Z","updated_at":"2015-01-07T03:57:53Z","closed_at":null,"pull_request":{"url":"https://api.github.com/repos/QuantEcon/QuantEcon.py/pulls/74","html_url":"https://github.com/QuantEcon/QuantEcon.py/pull/74","diff_url":"https://github.com/QuantEcon/QuantEcon.py/pull/74.diff","patch_url":"https://github.com/QuantEcon/QuantEcon.py/pull/74.patch"},"body":"Placeholder PR for merging a continuous-time version of he  Solow growth model into `quantecon.models`. Basic primitives of the Solow model are an aggregate production function and dictionary of parameter values. I want the user to  provide a sympy expression for aggregate production and some parameters, and then the class methods should set of the resulting differential equation compute the jacobian and pass these to the `ivp.IVP` class.\r\n\r\nAs always feedback is much appreciated!\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/QuantEcon/QuantEcon.py/issues/comments/68976036","html_url":"https://github.com/QuantEcon/QuantEcon.py/pull/74#issuecomment-68976036","issue_url":"https://api.github.com/repos/QuantEcon/QuantEcon.py/issues/74","id":68976036,"user":{"login":"albop","id":276777,"avatar_url":"https://avatars.githubusercontent.com/u/276777?v=3","gravatar_id":"","url":"https://api.github.com/users/albop","html_url":"https://github.com/albop","followers_url":"https://api.github.com/users/albop/followers","following_url":"https://api.github.com/users/albop/following{/other_user}","gists_url":"https://api.github.com/users/albop/gists{/gist_id}","starred_url":"https://api.github.com/users/albop/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/albop/subscriptions","organizations_url":"https://api.github.com/users/albop/orgs","repos_url":"https://api.github.com/users/albop/repos","events_url":"https://api.github.com/users/albop/events{/privacy}","received_events_url":"https://api.github.com/users/albop/received_events","type":"User","site_admin":false},"created_at":"2015-01-07T03:57:52Z","updated_at":"2015-01-07T03:57:52Z","body":"@davidrpugh @spencerlyon2 and @jstac : It is a good pedagogical material with a lot of hard work inside. Given how long it has stayed in the pipeline my vote would go for merging the PR exactly as it is, with the several files. The next step is obviously to advertise the notebooks on quantecon.org .\r\n\r\nAs for turning it into a general purpose continuous time module, I am not 100% sure that it is the right base to build upon. After looking at the code for a while, a big part of it seems tailored to a special class of models, namely the Solow models and I don't understand very well how you could turn it into a generic tool without rewriting it significantly. In any case, it seems important to design a bit in advance what the goals of such a module would be and possibly to develop it outside of the main library for a while. Let's open an issue for that and discuss it there rather than in a PR."}}