Fix to default_parameters.json

[jdebacker]

With the updates to ogusa_default_parameters.json in PR #140, the tax_func_type was not updated to "HSV". This PR makes that change.

The ogusa_default_parameters_2sector.json is also simplified, keeping just the parameters that need to be changed on top of the ogusa_default_parameters.json changes used in the one-sector model.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 45.69%. Comparing base (e76f917) to head (71c9153).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #141   +/-   ##
=======================================
  Coverage   45.69%   45.69%           
=======================================
  Files          18       18           
  Lines        1416     1416           
=======================================
  Hits          647      647           
  Misses        769      769           

Flag	Coverage Δ
unittests	45.69% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
ogusa/__init__.py	100.00% <100.00%> (ø)

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[jdebacker]

@rickecon this PR is ready for your review.

[rickecon]

@jdebacker. The file ogusa_default_parameters_2sector.json has been reduced to a very small number of specifications. However, shouldn't this be almost as big as ogusa_default_parameters.json? I thought the usage was to call one or the other, not one after the other. If we are following the former workflow, then ogusa_default_parameters_2sector.json should be bigger. LMK

[jdebacker]

@rickecon asks:

The file ogusa_default_parameters_2sector.json has been reduced to a very small number of specifications. However, shouldn't this be almost as big as ogusa_default_parameters.json? I thought the usage was to call one or the other, not one after the other. If we are following the former workflow, then ogusa_default_parameters_2sector.json should be bigger. LMK

I think it makes sense to keep the JSON files small so they are more readable. So I recommend the workflow of adding one on top of another. It adds only one line of code to layer updates like this and it saves about 10MB of disk space to use the smaller 2 sector JSON file. Both would already be included with the package so if one has OG-USA installed, they can load both if they wish.

[rickecon]

@jdebacker. I noticed that we don't have an example of this multi-country preferred parameter update workflow, neither in the OG-USA repo nor the OG-Core repo.

[rickecon]

@jdebacker. I just submitted a PR to your update_baseline branch for this PR. I simply increased the debt_ratio_ss to 2.6. and updated the cit_rate changes over time, which matches the data. I can merge this PR as soon as you review and merge my PR to your branch.

[rickecon]

Looks good to me. All questions answered. Merging now. @jdebacker