-
-
Notifications
You must be signed in to change notification settings - Fork 199
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
Conversation
Codecov ReportBase: 72.71% // Head: 72.79% // Increases project coverage by
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
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. |
@sbenthall this might be related to #1084 |
@wdu9, could you review this? |
Maaaybe but the bug was introduced after that issue was created. So maybe related but unlikely to fix it. |
Looks good. |
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. |
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 nott_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.