Bugfix/302 assign random variation to mcs pcs life satisfaction scores

[andrewbaxter439]

Bringing in PR for comparison and checks just now, though do hold off merging until refactoring sorted.

What

• adds expected variation to MCS, PCS, Life Satisfaction and DHE variables
• Restricts age of mental health and wellbeing processes to over 16 (for stage 1) and 25-64 (for stage 2) in line with calculated effect estimates

Why

• These were likely giving overly-precise mental health estimates and applying effects to wider-than-intended age groups

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

[andrewbaxter439]

Hi @dav-sonn - was going to merge this as it requires some further changes to things to be built on top of it. is it suitable to merge or should I hold off until after refactoring?

[dav-sonn]

Hi @dav-sonn - was going to merge this as it requires some further changes to things to be built on top of it. is it suitable to merge or should I hold off until after refactoring?

Hi @andrewbaxter439 - the refactoring is done, but I haven't merged the branch yet, as I wanted to discuss with everybody an outstanding related issue. If possible, I'd wait until tomorrow's meeting to discuss this together. Many thanks!

[andrewbaxter439]

Hi @dav-sonn - was going to merge this as it requires some further changes to things to be built on top of it. is it suitable to merge or should I hold off until after refactoring?

Hi @andrewbaxter439 - the refactoring is done, but I haven't merged the branch yet, as I wanted to discuss with everybody an outstanding related issue. If possible, I'd wait until tomorrow's meeting to discuss this together. Many thanks!

No worries, have a few things I think should be updated in this branch before merging anyway as the health module parts need some standardising and documenting. Will work on changes but hold off merging

[andrewbaxter439]

To review at meeting today @dav-sonn @justin-ven @matteorichiardi but should be ready to merge with refactoring finished. Ideally tidies up health variables to be consistent with prediction of other variables

[andrewbaxter439]

To note: updated variable name demLifeSatScore1to7 to demLifeSatScore0to10 so will need updated in codebook!

[andrewbaxter439]

Hi @justin-ven - thanks for sorting this. Let me know if you need me to do any quick fixes my end

[justin-ven]

Andy, I haven't been able to resolve the conflicts listed here - I think it might be worth using the "Convert to draft" option and then re-issuing the pull request.

[andrewbaxter439]

Hi @justin-ven - managed to get it fixed here so good to merge I think? 👍

[justin-ven]

Awesome – well done Andy. Would be good to hear how you managed to sort the conflicts out (I was at my wit’s end)… From: Andrew Baxter ***@***.***> Sent: 27 January 2026 17:51 To: centreformicrosimulation/SimPaths ***@***.***> Cc: justin-ven ***@***.***>; Mention ***@***.***> Subject: Re: [centreformicrosimulation/SimPaths] Bugfix/302 assign random variation to mcs pcs life satisfaction scores (PR #307) [Image removed by sender.]andrewbaxter439 left a comment (centreformicrosimulation/SimPaths#307)<#307 (comment)> Hi @justin-ven<https://github.com/justin-ven> - managed to get it fixed here so good to merge I think? 👍 — Reply to this email directly, view it on GitHub<#307 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AKJL7NH4G5QKN6NQQGXEIJT4I6JPXAVCNFSM6AAAAACPCYQDRWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTQMBWGMYTANBSGA>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[andrewbaxter439]

Hi Justin, managed it by using GitKraken GUI to do it and select 'prefer incoming' on each file in the merge commit. Then could run again afresh to get updated Stats files. I've looked up and there's ways of doing the 'accept all incoming changes' in the git cli which I've never used but perhaps that's the way forward: https://stackoverflow.com/questions/278081/resolving-a-git-conflict-with-binary-files

[justin-ven]

I tried to follow the directions for using the cli, but that didn't seem to help. Will bear in mind GitKraken next time I run into difficulty.