2023 shows up in a couple parts of the microdata generation, aside from #4032. 2023 has no significance: we should either use 2022 as the CPS base year (ideally storing this as a constant for the most recent CPS base year) or the existing CURRENT_YEAR constant (currently 2024) if needed.
2023
shows up in a couple parts of the microdata generation, aside from #4032. 2023 has no significance: we should either use 2022 as the CPS base year (ideally storing this as a constant for the most recent CPS base year) or the existingCURRENT_YEAR
constant (currently 2024) if needed.https://github.com/PolicyEngine/policyengine-us/blob/df6565293d92a9c820652d9a5baeb182e21ae469/policyengine_us/data/datasets/cps/enhanced_cps/calibrate.py#L35
https://github.com/PolicyEngine/policyengine-us/blob/df6565293d92a9c820652d9a5baeb182e21ae469/policyengine_us/data/datasets/cps/enhanced_cps/loss.py#L14
https://github.com/PolicyEngine/policyengine-us/blob/df6565293d92a9c820652d9a5baeb182e21ae469/policyengine_us/data/datasets/cps/enhanced_cps/loss.py#L331
And this seems like these should start at 2022:
https://github.com/PolicyEngine/policyengine-us/blob/df6565293d92a9c820652d9a5baeb182e21ae469/policyengine_us/data/datasets/cps/enhanced_cps/update_dashboard.py#L9
https://github.com/PolicyEngine/policyengine-us/blob/df6565293d92a9c820652d9a5baeb182e21ae469/policyengine_us/data/datasets/cps/enhanced_cps/run_calibration.py#L20-L21