-
Notifications
You must be signed in to change notification settings - Fork 32
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
Steps for putting OG-USA back on TaxBrain #539
Comments
Thanks for kicking this off, @MattHJensen. A concern in the first Phase would be to check that the calibration of OG-USA used matches CBO predictions for debt load, growth rate, and GDP per capita. The biggest remaining problem with using OG-USA for dynamic scoring is that government debt faces a high real interest rate. We have not yet discussed how to solve that. But without a solution, it leaves the model with a strong anti-deficit bias (on top of being a closed economy, which already implies such a bias). |
@salimfurth Thanks for these comments. Let me just clarify that this issue is about just how to get OG-USA back on TaxBrain and producing results that are sensible in terms of percentage changes. I think we were fairly happy with these before as they made sense relative to other results we were seeing from the micro simulation model and the macro elasticities model. As you point out, in the longer run, we'll want to target the model to the levels of various variables forecast by CBO. I view this as a difficult and time consuming exercise and thus my opinion is to delay that until the model is developed much further. However, I'm glad if folks want to step in and add a wedge between interest rates on private capital and public debt or calibrate the current, more simple model to hit CBO targets. But those specific items should be handled under a separate issue, opened in the OG-USA repo. |
Step 3 is checked off. The link pattern to kick of OG-USA runs is http://www.ospc.org/dynamic/ogusa/[STATIC_RUN_#]/?start_year=2017 |
@MattHJensen @jdebacker @PeterDSteinberg @salimfurth It should be noted that the links to the simulation results are not |
@jdebacker, @PeterDSteinberg, @rickecon My first simulation failed:
|
@PeterDSteinberg Can you help with the OG-USA failure above? It looks like it has to do with the start year ( cc @rickecon |
@jdebacker and @rickecon - I'll add you as optional invites for a webex meeting tomorrow at 1 pm Eastern with @MattHJensen @brittainhard and @enelson1995 regarding the fixes involved on this issue. @brittainhard has worked on this one more closely. |
@PeterDSteinberg, is the og-usa failure above something that we should expect to be a quick fix, or do you think there is some bigger issue involved? |
@MattHJensen - I would not expect this to be a quick fix - the bug quoted above is evidence in favor of the one-API approach to deploy and webapp-public repos we discussed (issue #543 ). The quickest fix I would estimate at >6 hours and it would be a temporary solution (temporary in the sense that it would not fully address #543 as an architecture issue). @brittainhard is more familiar with the specifics of this problem. |
Ok @PeterDSteinberg. Let's knock off #543 first then. |
Based on the principal that upstream repos should not be responsible for testing downstream repos, and based on the fact that taxcalc is now reporting all breaking API changes as part of our release notes, I am going to remove step 6 from phase 2. |
@rickecon, @PeterDSteinberg, @jdebacker, @brittainhard
This is based on recent conversations I've had with Jason, Rick and Peter about getting OG-USA back up on TaxBrain.
Phase 1 is a path to having a single default style of OG-USA on TaxBrain. It would not require any changes to the the TB GUI, and testing will primarily occur on TaxBrain itself from a hidden link.
Phase 2 is a path to running multiple styles of OG-USA on TaxBrain. It will require changes to the TB GUI and more work on testing.
One of the goals here is to involve OG-USA maintainers more heavily in test creation and maintenance.
Please raise flags if any aspect of the approach seems inefficient or misguided!
Phase 1.
Phase 2.
DELETED
py.test -m “full-single_reform"
.....
Bonus:
cc @salimfurth
The text was updated successfully, but these errors were encountered: