Phase 2 Scenario runs - #30
Conversation
danlewis85
left a comment
There was a problem hiding this comment.
I've reviewed and run your code and it produced the anticiapted outputs.
As discussed, I've implemented the following changes:
- Added a scenario for cold weather payments.
- Changed the WHD revenue calculations so that the revenue is always: 3x core spending on whd scaled to the eligible group + the ring-fenced non-core spending.
Please check the diff and ensure you're happy with the changes.
|
I've reviewed the changes and am happy with all of them. For ease of further processing of results, I've updated the scenario descriptions and added new code that pickles the summary dataframes. |
|
@danlewis85 Please have a look at the new code added in this commit. The main changes are:
Please check that all the scenarios have been set up correctly, and that the outputs are as you expect. Once we've merged the new EII levy and price cap update changes to dev, I'll get those changes and run everything to get our final set of results. |
a5d6ef9 to
b3b8332
Compare
I've checked the setup for the scenarios for mean and 95%ile have been setup correctly and confirm that the outputs align with my expectations. I'm happy for you to run a final set of results. |
|
@danlewis85 Please have a look at the code for scenarios set 3. There are three new files:
In the code for model runs, please pay special attention to:
The histograms code is mainly the same as set 2 but I've altered the max and min net bill change intervals to capture the range of the new results. If you'd like to check the general pattern across scenarios, preliminary visualisation is here. |
…el into scenarios_phase_2 Merging new set 3 scenarios
|
@danlewis85 You may have already caught this but would also appreciate your opinion on the new way I've calculated
This was previously I guess |
Yeah, the operation of WHD is a bit confusing. In Scotland it's slightly more obvious that the non-core spending covers both industry initiatives (max £7m) and spending on the broader group, whereas in England and Wales it seems as though the 2 core groups are funded from core spending and the non-core spending can act as a contingency of sorts. I think the approach of ringfencing £50m for industry initiatives and then taking the rest as the core spend is the right approach for this. |
Happy with all this. I spent extra time with the ECO4 & GBIS split and that all seemed to function as anticipated (as if using ECO collectively). I also recalculated the 2/3 move to general taxation and got hte same results. Happy for you to proceed with the outputs. |
|
Hi Dan, please see the latest commit for scenarios set 4 analyses. There are two files, one using mean consumption and one using 95th percentile consumption. I have integrated the histogram table creation into these files too. I'm still fixing the code block for generating the helper arrow values for the individual scenario dot plot, so please ignore those lines for now. |
…el into scenarios_phase_2 merging new changes for ongoing review of analytical outputs.
I've had a look at this, paying particular attention to the 3 general taxation split scenarios, and the helper arrows now that you've pushed the fix. All looks good. |
|
Bug fix for calculating bills with a unit discount inclusive of VAT. Note that flat rebate was always inclusive of VAT, but the unit discount wasn't. This fixes that in terms of the final bills calculated for consumers. |
|
Set 5 scenario runs using mean consumption. The code is structured similarly to set 4, except that the unit discount is specified/calculated at the beginning of each run. I've also resorted to numbering them as there are quite a lot to keep track of. @danlewis85 Please could you check the code in general, and that the outputs are as expected? Results data are visualised in the flourish charts. I also wanted to check with you on how to handle VAT when we're specifying the discount value explicitly - I've assumed that the value assigned to the variable is already inclusive of VAT, which should get propagated to the final WHD revenue. |
|
Happy with 8681a02, the handling of VAT looks right in context. The new output of weighted averages looks to be correct. Many thanks. |
|
Added new "Scenario 12" to set 5. This scenario represents "Option 2 (reduced benefits + cut GBIS, taxpayer funds the rest of the support)". @danlewis85 Please could you check that it has been set up correctly 🙏🏼 |
…el into scenarios_phase_2 Merging new work.
I checked the new scenario as I developed the typical domestic consumption value runs and am happy that it is correctly specified. |
|
Added new files for scenarios set 6 runs. @danlewis85 Please could you check that the support parameters and levy rebalancing weights are correctly specified? |
I'm happy these are correctly specified. I've checked the mean script in full, and the alternative variable definitions for tdcv and percentile outputs. |
Description
The new file
analysis/phase_2_scenarios.pymodels levy reform approaches and writes results to Excel for the following scenarios:In the same order as I've listed above, the code takes each scenario and does the following:
There are two Excel files that are generated and saved in
outputs/data:{datetime}_phase_2_scenarios.xlsxcontains raw results data in tidy format for all levies, tariffs, cost ratios, consumers and support mechanisms (i.e. new WHD revenues, core spends, support base, unit discount values) across all scenarios.{datetime}_phase_2_scenarios_flourish.xlsxcontains pivoted consumer results in a format compatible with making Flourish charts.Instructions for Reviewer
For this PR, please could you review the new code in general and check that the results saved in both Excel files are what you would expect.
Please pay special attention to how WHD revenue, core spend and unit discounts are calculated in each scenario. These are calculated using the eligible group sizes given in the CSE archetypes model, so I'd like to check whether you also think it's reasonable to be using the eligible group sizes in each archetype in this way.
Once you're happy with it, I don't think there is an immediate need to merge as I anticipate we will need to run more scenarios for phase 2.
Checklist:
notebooks/pre-commitand addressed any issues not automatically fixeddevREADMEs