Here's how it looks on my screen

e.g. Sam's slides

Or remove from the mobile view for now if easier

For parallelism with the organization-level parameters like the UBI Center logo

The official icons are at https://www.facebook.com/brand/resources/facebookapp/logo

Since they're centered, they look like section breaks that would contain multiple parameters, and then the description seems more like the variable name. I think left-aligning would be more consistent with the theme and easier to read.

Similarly, the household variables could be left-aligned, but the descriptions don't seem necessary.

e.g. it does https://uk.policyengine.orghttps://uk.policyengine.org/population-results?basic_rate=22

http://policyengine.org/uk/household?abolish_UC_child=1

Net income doesn't change. Changing the adult age fixes it. Bug with no working-age adults by default.

Cap at 100? Add an open circle?

The URL currently includes only policy parameters, to avoid users accidentally revealing their income and other household information. We should also provide a way for users to share the scenario including their household information (with clear disclaimers about it including income).

Our current Donate link in the footer goes to https://opencollective.com/psl. This creates two problems:

1. PSL-F won't know to direct donations to PolicyEngine
2. OpenCollective charges a 10% fee which can be avoided by sending a check or wire transfer (though wire fees make OpenCollective cheaper for small gifts)

We should create a Donate page that describes the options for donors and suggests that they email us or PSL to direct the donation. PSL-F will likely do this soon, though I think we should mirror the information on PolicyEngine for a consistent user experience.

@jdebacker is it OK for us to put the PSL-F bank info on the site? Anything else you'd suggest here?

http://policyengine.org/uk/household-impact?abolish_CB=1 shows no difference between baseline and reform when the household has a child.

• Simulate on the population -> See UK impact
• Skip to your household -> Describe your household
• See your results -> See household impact
• Change the policy reform -> Adjust the policy

e.g. from this:

This has colors flipped, doesn't use rdbl, and labels as if it's a household.

That chart gets created here:

Which calls population_waterfall_chart here:

And waterfall_chart has different logic for formatting the waterfall chart depending on:

The simplest explanation would be if isinstance(baseline, Microsimulation) no longer holds, but it still looks like that would be the case:

e.g. at http://policyengine.org/uk/population-impact?basic_rate=23 it tweets

I just simulated a reform to the UK tax and benefit system with @ThePolicyEngine. Check it out or make your own! https://uk.policyengine.org/uk/population-impact?basic_rate=23

https://uk.policyengine.org/uk/population-impact?basic_rate=23 doesn't work

Here's an example from the policy page, but the same issue shows up on the household definition page.

https://www.loom.com/share/e77dc72f4a9b4b298b0e4127883f71b1

Currently the text in Your Plan describing a parameter's change (light gray text) is specified from a template provided in openfisca. This requires extra work, creates redundant text, and produces inconsistencies:

Here's an example of the summary:
https://github.com/PolicyEngine/openfisca-uk/blob/192cea3c0c38c27cdb6ad574ae25b9f5943143fc/openfisca_uk/parameters/benefit/universal_credit/means_test/work_allowance.yaml#L19

I think this can instead be Change to @ for all. If we need to vary it by parameter type (I don't think we do), we can have logic based on metadata.policyengine.type.

Avoid 0% 0% 1% 1% but don't introduce decimals unnecessarily. See also #76.

I haven't seen other policy organizations include this, risks looking juvenile

e.g. Raise from 25% to 30% or Lower from £12,570 to £4,000

See #78

https://uk.policyengine.org/?higher_threshold=0

https://blog.policyengine.org

Might get crowded so we can shrink Share your feedback to Feedback

Per user feedback

e.g. https://github.com/PolicyEngine/policyengine/runs/4012526696?check_suite_focus=true#step:5:452 says

WARNING: You are using pip version 21.3; however, version 21.3.1 is available.
You should consider upgrading via the '/opt/hostedtoolcache/Python/3.7.12/x64/bin/python -m pip install --upgrade pip' command.

This traces to https://github.com/actions/virtual-environments, e.g. actions/runner-images#3285. It isn't affecting anything so just logging to keep track.

They currently differ between the header, the form, and the graphs

e.g. going from http://policyengine.org/uk/household-impact?basic_rate=30, the Change your household button goes to http://policyengine.org/uk/undefined/household?basic_rate=30

See also the gif in #50 (comment)

Not exactly sure how to do this, but not having this type of test has caused a fair few issues recently. Essentially, we want to have a GH action briefly host the built site "locally", and test all the API endpoints and client pages.

http://policyengine.org/uk/household-impact?child_UBI=46

Something like plcyn.gn? Won't need for a while so just jotting down for now.

It'd be cool for the policy cart + buttons to be frozen on the right side, so as you scroll through the charts it remains visible.

This is a significant rewrite, consolidating the PolicyEngine-UK and -US repos into one package, PolicyEngine (containing both PolicyEngine (python server) and policyengine-client (React app). The advantages include:

• Significantly reduced dependency complexity (and therefore reverting to old versions becomes feasible)
• Significantly easier deployment of PolicyEngine-US (different entity structures would've made it either very complex, or a high amount of duplicated code)

For minor reforms, this can look weird with 0% 0% 1% 1% kind of thing, but for most it'll look cleaner without the decimal.

Similar to GitHub's custom cards for issues:

Could have the top-level metrics for the country impact page and the net income impact on the household page.

Splitting off from #14:

For example, this is how Compute Studio presents inputs, see this from Tax-Cruncher: