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

unexpected discrepencies with read_shocks in FramedAgent example #1084

Closed
sbenthall opened this issue Nov 18, 2021 · 4 comments
Closed

unexpected discrepencies with read_shocks in FramedAgent example #1084

sbenthall opened this issue Nov 18, 2021 · 4 comments
Assignees

Comments

@sbenthall
Copy link
Contributor

Originally discussed here: #1071 (comment)

In the FramedAgent example, I've tried to use the read_shocks functionality to use the exact same shocks in the PortfolioConsumerType and the PortfolioConsumerFrameType, on the theory that the simulation histories should then be identical.

My current use as of #1071 of this isn't working, in that the two simulated shock histories are divergent.

On the other hand, making this change does make the simulation histories look more similar.

Likely there are two issues buried in here: one about proper use of read_shocks, which could be a better documented workflow, and another with the alignment of the simulation mechanics of the framed and unframed models.

@sbenthall
Copy link
Contributor Author

Related to #863

@sbenthall
Copy link
Contributor Author

Will revisit this once #1101 is merged to see if that makes a difference, as per @alanlujan91 's suggestion

@sbenthall
Copy link
Contributor Author

It does look like #1101 helped with this.
But I see now that there are possibly subtle differences in the income process, which I'm still not totally able to replicate in the Frames version of the model, because of some irregularities in how the core IndShock models are designed. I've brought up these design challenges in issue #1111

@sbenthall
Copy link
Contributor Author

Closing because the FramedAgent is slated for removal

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

No branches or pull requests

1 participant