Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Policy function accuracy in Cake Eating II #260

Open
jms202 opened this issue Oct 7, 2020 · 1 comment
Open

Policy function accuracy in Cake Eating II #260

jms202 opened this issue Oct 7, 2020 · 1 comment
Assignees

Comments

@jms202
Copy link

jms202 commented Oct 7, 2020

The lecture suggests that time iteration is likely to be more accurate than value function iteration.

But playing around with the solution to Exercise 2 suggests that most of the heavy lifting is done by (i) a smaller solution tolerance (1e-5 rather than 1e-4), (ii) you set x_grid_min=0.0, and (iii) the fact that you "handle small x separately" in the K() time iteration operator.

It seems that small changes in the numerical implementation can make a substantial difference to the quality of the solution. It would be great if you could address this issue directly. For example, why are (i), (ii) and (iii) above important? What is going wrong in their absence?

One other important point: when you "handle small x separately", you set the policy to consume zero. This means that you can't use the policy function to calculate the value function because log(0) = infinity. Surely there is a better solution here.

@mmcky
Copy link
Contributor

mmcky commented Feb 9, 2021

@shlff would you mind to take a look at this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants