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

[Bug-fix] Mortality and t_cycle when shocks are read #1181

Merged
merged 6 commits into from
Oct 19, 2022

Conversation

Mv77
Copy link
Contributor

@Mv77 Mv77 commented Oct 12, 2022

Some months ago I did some work on the functionality that allows you to read pre-computed shocks.

I made a crucial omission of resetting t_age and not t_cycle when killing agents when one reads a shock that kills them.

This is a pretty serious bug. The upside is that it was introduced not that long ago in the grand scheme of things (9 months), and that the read_shocks feature is not used as often. I hope this did not cause trouble to anyone...

This patch fixes the issue.

  • Tests for new functionality/models or Tests to reproduce the bug-fix in code.
  • Updated documentation of features that add new functionality.
  • Update CHANGELOG.md with major/minor changes.

@project-bot project-bot bot added this to Needs Triage in Issues & PRs Oct 12, 2022
@codecov-commenter
Copy link

codecov-commenter commented Oct 13, 2022

Codecov Report

Base: 72.71% // Head: 72.79% // Increases project coverage by +0.08% 🎉

Coverage data is based on head (c635830) compared to base (73f6521).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #1181      +/-   ##
==========================================
+ Coverage   72.71%   72.79%   +0.08%     
==========================================
  Files          72       72              
  Lines       11764    11793      +29     
==========================================
+ Hits         8554     8585      +31     
+ Misses       3210     3208       -2     
Impacted Files Coverage Δ
HARK/Calibration/Income/IncomeTools.py 92.79% <100.00%> (ø)
...nsumptionSaving/tests/test_IndShockConsumerType.py 78.55% <100.00%> (+1.81%) ⬆️
HARK/core.py 91.48% <100.00%> (+0.01%) ⬆️
HARK/ConsumptionSaving/ConsIndShockModel.py 79.47% <0.00%> (+0.20%) ⬆️

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

@Mv77 Mv77 added the Ready-To-Merge Has been reviewed and when branch is updated and checks pass it should be merged label Oct 13, 2022
@alanlujan91
Copy link
Member

@sbenthall this might be related to #1084

@llorracc llorracc self-assigned this Oct 15, 2022
@llorracc
Copy link
Collaborator

@wdu9, could you review this?

@llorracc llorracc removed their assignment Oct 15, 2022
@Mv77
Copy link
Contributor Author

Mv77 commented Oct 15, 2022

@sbenthall this might be related to #1084

Maaaybe but the bug was introduced after that issue was created. So maybe related but unlikely to fix it.

@wdu9
Copy link
Collaborator

wdu9 commented Oct 15, 2022

Looks good.

@Mv77
Copy link
Contributor Author

Mv77 commented Oct 19, 2022

I've corrected the typo that Will identified and merged the latest master.

I'll merge after tests are done if there are no objections.

@Mv77 Mv77 merged commit 76d0e48 into econ-ark:master Oct 19, 2022
Issues & PRs automation moved this from Needs Triage to Done Oct 19, 2022
@Mv77 Mv77 deleted the plumbing/mkshks_bugfix branch October 23, 2022 22:03
@sbenthall sbenthall added this to the 0.13.0 milestone Jan 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Ready-To-Merge Has been reviewed and when branch is updated and checks pass it should be merged
Projects
Issues & PRs
  
Done
Development

Successfully merging this pull request may close these issues.

None yet

6 participants