Addressed boundary solution issues in UK employment alignment#333
Open
LiangShi369 wants to merge 7 commits intodevelop_LS_PortEmploymentAlignmentfrom
Open
Addressed boundary solution issues in UK employment alignment#333LiangShi369 wants to merge 7 commits intodevelop_LS_PortEmploymentAlignmentfrom
LiangShi369 wants to merge 7 commits intodevelop_LS_PortEmploymentAlignmentfrom
Conversation
…the JAS-MINE core already update regression coefficient during employment alignment, hence I remove refreshLabourSupplyUtilityRegression(...) method in the Parameters class.
… little bit - Employment alignment now warm-starts from previous year’s solved adjustment when year > startYear; otherwise it uses current-year configured value. - Added inline comments explaining purpose and behaviour.
1. use new initial population to calculate employment targets, hence singleDep_male/female have the same alignment target variable as other groups. Simulation code is modified accordingly. 2. Add warm-start and search boundary adjustments as in the inSchool alignment. 3. Integration test passed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I have made following changes to SimPath Java code and Stata code:
For the simulation side:
Root causes of boundary roots after employment alignment:
Key fixes:
For the data side:
01_employment_shares_initpopdata do-file calculates the employment ratio of male/female in BUs that only one person is at risk of work:
bu_fracemployed = bu_male_emp / (number of SingleDep_Males/Females BUs),
Notice that unlike EU model, the UK model defines "at risk of work" additionally with "careNeedFlag!=1".
02_person_risk_employment_stats do-file calculates employment statistics for all 7 categories (couple, single_male, single_female, singleDep_Males, singleDep_Females, singleAC_males and singleAC_females). It shows there are persons long-term disabled but employed, and persons need care but employed.