SOI business net profit/loss targets omit SSTB Schedule C income on the model side
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
Research direction
Start with us_runtime/fiscal_targets.py:256-257 and compare the model mapping for business_net_profits and business_net_losses with SOI A00900, which counts all Schedule C income. Read the qbi_inputs.with_us_qbi_input_reconciliation path to understand how base and SSTB income are routed, then check the loss sign convention and whether farm operations income belongs. Done means choosing and implementing the mapping, re-pinning, and measuring its effect on a calibration run.
Written by the indexing model from the issue text.
Description
Raised in #1380. It is still open after #1384.
us_runtime/fiscal_targets.py:256-257 (at dce4aa99b) maps the SOI business_net_profits and business_net_losses targets to self_employment_income only. SOI A00900 counts all Schedule C income. So the model side of those targets leaves out sstb_self_employment_income:
- PUF channel: #1380 measured $253.8B (weighted) of SSTB Schedule C income that the targets don't see.
- ACS rows after QBI reconciliation:
qbi_inputs.with_us_qbi_input_reconciliationroutes base + SSTB wholly to the SSTB leaf whenbusiness_is_sstb. In the lanes that run it (pool, stacked), an SSTB owner's SEMP then leaves the target's model side too.
To do
- Decide whether the business-net-profit and loss targets should sum the base and SSTB leaves (and farm operations income, if SOI's line maps there). Check the loss leg's sign convention.
- Re-pin, and measure the effect on a calibration run.
- Dominant language
- Python
- Stars
- 0
- Forks
- 6
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 130
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from PolicyEngine/microcosm
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
PolicyEngine/microcosm#1220 ·
Maintainers usually reply within 1 day
-
Update two stale comments about the export-mass reviewed-exclusion registerPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 1/5 Under an hour Newbie friendliness 88/100
PolicyEngine/microcosm#1108 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
PolicyEngine/microcosm#475 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
PolicyEngine/microcosm#1390 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
PolicyEngine/microcosm#1389 ·
Maintainers usually reply within 1 day
All issues in PolicyEngine/microcosm
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
UKGovernmentBEIS/optstop#10 ·
-
maintenance
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
pollen-robotics/reachy_mini#1508 ·
Maintainers usually reply within 1 day
-
[BUG] `cloud-keys.env` values retain enclosing quotes causing 401 Unauthorized, and missing utf-8 encoding crashes on WindowsPossibly taken @divyanshu07-code claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
open-jarvis/OpenJarvis#1192 · 1 comment ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sylvainmetayer/homelab#851 ·
Maintainers usually reply within 1 day