Review initialisation tags for Person and Benefit Unit objects
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by locating where Person and Benefit Unit attributes receive the @Lag and @NullInitialised tags, then compare those definitions with the candidate attributes listed in the issue. Check which omissions cause crashes or changed simulation results and identify the expected initialization behavior. Done means the appropriate tags are applied and the affected simulations no longer crash or produce unintended differences; the issue names no tests to run.
Written by the indexing model from the issue text.
Description
Tags @Lag and @NullInitialised have been added to the project to facilitate initialisation of attributes at the start of each simulated period. These tags have not been added to candidate attributes where the model was found to crash or generate different results. The issue is most accute for the Person objects, where tags have been omitted from the following candiates:
- yMiscPersGrossMonth
- yCapitalPersMonth
- yPensPersGrossMonth
- yEmpPersGrossMonth
- yNonBenPersGrossMonthL1
- yNonBenPersGrossMonth
- labWageFullTimeHrly
- labHrsWorkWeekL1
- labHrsWorkWeek;
- demPartnerNYearL1
- xEquivYear
- labWageFullTimeHrly
- labHrsWorkEnumWeek
- Dominant language
- Java
- Stars
- 26
- Forks
- 38
- Avg merge
- 15h 18m
- Merged PRs (30d)
- 10
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from simpaths/SimPaths
-
Difficulty 1/5 Under an hour Newbie friendliness 89/100
Maintainers usually reply within 1 day
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Remove insecurity indexPossibly taken @dav-sonn claimed this 1 day ago. Open
simpaths/SimPaths#551 · 1 assignee ·
Maintainers usually reply within 1 day
-
Double hurdle model of labour supplyPossibly taken @dariaple claimed this 2 days ago. Open
simpaths/SimPaths#548 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
All issues in simpaths/SimPaths
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
quarkiverse/quarkus-google-cloud-services#1188 ·
Maintainers usually reply within 1 day
-
Component: Frontend Component: Web Component Type: Maintenance
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
it-at-m/refarch-templates#1944 ·
Maintainers usually reply within 2 days
-
priority: p2 type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
googleapis/java-genai#1372 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 60/100