-
-
Notifications
You must be signed in to change notification settings - Fork 198
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
Changes to Gentle Introduction to HARK #1355
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #1355 +/- ##
=======================================
Coverage 73.33% 73.33%
=======================================
Files 83 83
Lines 13596 13596
=======================================
Hits 9971 9971
Misses 3625 3625 ☔ View full report in Codecov by Sentry. |
The code and the earlier model assumes $\Gamma_t$ to be a constant, so changed the notation in the later model as well
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.
Great job! I made some notational changes but agree with all your changes.
A couple of things I wanted to clarify:
Once these things are addressed, this is good to go (but you'll have to merge them, I can't) |
@sidd3888 were you going to redo this one? |
Added one sentence and a couple words, adjusted commas.
I adjusted a few words, including the age-varying notation in the first paragraph. I moved the sentence about death probability to be semicolon clause in the LivPrb sentence; it's less prominent now, as Siddarth is correct that it serves little purpose. The existence of the reference to death probability might be a legacy of older notation. I think we used to use D for death probability and \cancel{D} for survival probability, making it more useful to actually mention death probability. Some of the checks are now failing after adjusting text, which is surprising. I'll look into it. |
It looks like it's because I cleared notebook output, but Sphinx relied on its existence. Will fix. |
Output was mysteriously missing in some notebook cells; trying again for tests.
Ok, I'm baffled @sbenthall . I'm now getting an error from ruff-format, which is apparently unhappy with a coding style change I made-- I think I moved a comment or two. I can't get ruff to run on my computer, as it says that the notebook isn't a JSON file at all. |
I think this should pass now, is it ready to merge @mnwhite ? |
It should be. Any guesses for getting ruff to work for me?
…On Fri, Dec 8, 2023 at 7:46 PM Alan Lujan ***@***.***> wrote:
I think this should pass now, is it ready to merge @mnwhite
<https://github.com/mnwhite> ?
—
Reply to this email directly, view it on GitHub
<#1355 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADKRAFOXRRYHBDLTH237YGTYIOYHFAVCNFSM6AAAAAA66SD2K6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBYGAYTONRZGQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
first thing i did was merge all the changes in master branch @MridulS is there a way to let ruff make and push the changes needed instead of not passing? |
Changes made according to points mentioned in #1354
Primarily made changes to the description of the models or fixed typos. Only thing I changed in the code was to generate the plot of the model with updated parameters and then removing the pertinent code, so that the image matches the description (also detailed in the issue).
@alanlujan91 sent you an email about one of details. Ready to merge from my end once that is addressed