-
-
Notifications
You must be signed in to change notification settings - Fork 58
Fix parameter order in solve_model function calls in ifp_advanced #762
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
Closed
+8
−8
Closed
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Confirmed — this is correct, and the PR is being closed without merging.
Tracing the labels through:
K(a_in, c_in, ifp)takes the asset grid first (it is the x-coords ofjnp.interp) and returns(a_out, c_out).solve_modelthen calls it asc_out, a_out = K(c_in, a_in, ifp)— swapped on both the arguments and the unpacking. That double swap meanssolve_model's first parameter is what actually reachesK'sa_inslot, and its first return value isK'sa_out. So the real contract of the function as written issolve_model(ifp, a_init, c_init) -> (a_grid, c_policy)— exactly the ordering onmain, and the opposite of what the signature and docstring claim.Two notes on the impact, for the record. The argument reordering in this PR is a harmless no-op at every call site, because the two arrays passed are literally identical there (
a_init = σ_init.copy()at :484,c_init = a_initat :644/:736/:813). The return unpacking is the real regression:c_vecends up holding the asset grid anda_vecthe consumption policy, which flow intocompute_asset_stationary(c_vec, a_vec, …)→simulate_household→jnp.interp(a, a_vec[:, z], c_vec[:, z])at :534 with x and y reversed. It does not raise; it silently produces wrong asset distributions and Gini coefficients.The genuine defect you surfaced is the misleading names inside
solve_modelitself, which is a readability problem in a lecture whose source students are meant to read. That will be fixed in a separate PR against latestmain, along the lines of your second suggestion — un-swapping the body toa_out, c_out = K(a_in, c_in, ifp)so the parameter names and return order are truthful, with no behavioural change.