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

generalize configuration of income process #673

Closed
sbenthall opened this issue May 5, 2020 · 4 comments
Closed

generalize configuration of income process #673

sbenthall opened this issue May 5, 2020 · 4 comments
Labels
Milestone

Comments

@sbenthall
Copy link
Contributor

Most models now inherit the lognormal income process from ConsIndShock:

IncomeDstn, PermShkDstn, TranShkDstn = self.constructLognormalIncomeProcessUnemployment()

def constructLognormalIncomeProcessUnemployment(self):

But some models have subtle changes to the process, requiring some overwriting of the model function:

https://github.com/econ-ark/HARK/blob/0.10.6/HARK/cstwMPC/cstwMPC.py#L51-L74

It may be possible to design this so that the income process distributions are defined when a model is parameterized. This would lead to a more consistent API. See #620

@llorracc
Copy link
Collaborator

llorracc commented May 5, 2020

Incidentally, I have long felt that our default should be using a lognormal truncated at some (large) number of standard deviations (like, 5). This would ameliorate (though not fix) the fact that as we increase the number of gridpoints, the minimum possible realization moves substantially. This matters because a good bit of the logic of the model depends on the value of the minimum possible realization.

An even better approach would be to institute an infinitesimal probability of a "minimum income event" corresponding exactly to the truncation bound of the distribution. That would effectively eliminate the problem because the minimum possible income would remain the same as long as the truncation threshold remained the same, regardless of how many (or few) points were used in the approximation.

@mnwhite
Copy link
Contributor

mnwhite commented May 5, 2020 via email

@sbenthall sbenthall added this to the 1.0.0 milestone Jan 29, 2021
@sbenthall
Copy link
Contributor Author

This issue is now quite complicated because it's not clear whether it refers to the original scope or the one CDC introduced in the comment.

It looks like #804 is a more fleshed out version of the issues raised in the comment here.

So this ticket refers to the original item now,

@sbenthall
Copy link
Contributor Author

Now redundant with #620

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

No branches or pull requests

3 participants