bitss-opa / opa-wealthtax Goto Github PK

• numberTaxpayers

• taxBase

• brackets

• total number of households

• total number of tax units

There are assumptions/parameters that affect these. Ultimately make a new tab that allows interactive choices of these.

Hi @sastoudt Sara, love the work and I am following the work at wealthtaxsimulator.

Don't have expertise in R but in python : how can contribute to support API and data integration for other Countries, too ?

• Basic: Choose your bracket limits (4 brackets, 3 tax rates, bottom bracket set at zero by default)

• Advanced: on the plot rather than on the side

Clarify following line in document:

 We use a standard Pareto interpolation technique, to estimate the billionaire tax base between \$1 billion and `r paste("$", round(totax_last_400_in, 1),sep="")` (below the Forbes 400).

Please add a more narrative explanation and if possible, add code to that uses the pareto distributin parameters in R

Some way to visualize that the number of affected households is very small (e.g. open pie chart?).

Add this next to the numerical output.

Moving these from README

High level to dos:

• Create a DD based on spreadsheet
• Remove rounding
• Wrap each chunk in the DD into a function
• Run the shiny app based on the functions above
• Run everything on datahub
• Share prototypes of DD and App privately
• Rename taxbase variables into taxreveneu when apropiate

• streamline getGroup (had to rollback changes due to a bug in the streamlined version)
• streamline getAverage

Fix the fact that showMargin is currently not reactive.

So far the app and dynamic doc produce the same analysis, but that analysis is performed using a different function. So if something changes in the DD, it will not be reflected in the app.

To achieve a higher level of transparency and reproducibility we need to have both running on the same functions.

This will probably entail two big tasks:

• Make code from app more compact and readable.

• Wrap each step of the DD into a function. With the following structure:

dd_overall_chunk_functions{
    ...
    functions_in_common_dd_and_app{
        ...
    }
    ...
} 

• Make the relevant functions in the in the app with the following structure:

shiny_app_functions{
    ...
    functions_in_common_dd_and_app{
        ...
    }
    ...
} 

Dynamic Document creates functions that are called by the interactive app.

• change increment to by 0.1
• length of xval (try 1000, too laggy)
• change getMarginal function name to be more representative
• format of numerical outputs (emphasize Total Taxes and Total Taxes over 10 years)