Comments (4)
Just wanted to comment here so that I will receive updates on this issue. I am likely affected by your second case above: my disabled child's life expectancy is relatively short.
from open-social-security.
@batsatt Unfortunately, this is an issue I am aware of but no longer working on. I cannot see a way forward that does not cause the complexity of the code to absolutely explode. I've spent a fair bit of time attempting it, but I'm completely stumped.
Right now, in a married couple scenario, the benefits are calculated each year for four cases: both alive, only personA alive, only personB alive, neither alive. (This occurs in benefit.service, familymaximum.service, and earningstest.service.) To add one child's mortality outcomes into the mix doubles that to 8 different cases that have to be calculated. And we'd have to be able to account for mortality outcomes of multiple children (as many as 6, at least in theory). So instead of 4 cases, it's 4 x 2^6.
from open-social-security.
I hear you. Well, at the very least you should consider adding a warning about this. And maybe some guidance about how to interpret the report while factoring in the life expectancy of a disabled child...
Seems to me there are two scenarios:
- Child's life expectancy exceeds both parents. In this case, only the present value is too high, right? The last line of the Year-by-Year child benefit is still valid, and would just apply out to the child's death. I assume this scenario has no impact on the parent SS income.
- Child's life expectancy does not exceed both parents. In this case, the present value is again too high, but the Year-by-Year benefit amounts can be manually adjusted by the user to subtract the child benefit starting in the assumed death year.
Perhaps you could add to the content below where the present value result is shown. For example, a sentence that says what the calculation assumed as the age/year of death for each spouse, followed by the (dynamic) warning/guidance if child benefits are included.
Knowing the assumed age/year of death for each parent would enable a user to adjust for the second case above without too much work. I'd probably map your table into a spreadsheet and make the adjustments there.
from open-social-security.
@batsatt I added a warning regarding the mortality assumption for the child(ren).
As far as mortality assumptions for the parents, it's an input that's adjustable by the user. But by default the calculator is not assuming a particular age/year of death. This article discusses the reasoning for such:
https://obliviousinvestor.com/long-will-collect-social-security-survivor-benefits/
from open-social-security.
Related Issues (16)
- Bug: no alternative-strategy table output when "yes cut" is selected HOT 2
- Bug: range component output includes spousal filing date when not applicable HOT 3
- Bug: range component output not responding to new clicks in already-filed scenario HOT 1
- Scale (or hide) range chart for mobile HOT 5
- Convert range component output to unordered list and add ages HOT 4
- Code Cleanup HOT 4
- ExpressionChangedAfterItHasBeenCheckedError: Expression has changed after it was checked. HOT 1
- Spouse Survivor Benefit Computation? HOT 4
- Error running presentvalue.service.spec.ts HOT 1
- URL query parameters missing child inputs HOT 2
- Children-only benefits are not included in present value calculation for a couple HOT 1
- Incorrect rounding of benefits HOT 1
- Save your inputs link drops discount rate if 0% HOT 1
- Survivor Benefits appear incorrectly calculated HOT 3
- Inaccurate probabilityAlive calculations for some couples HOT 7
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from open-social-security.