-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RDRP-646: Construction for short form to long form #182
Conversation
This file contains 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
coatet
approved these changes
Jan 15, 2024
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.
Created a test construction file (separate to the standard one whilst I've been playing with it) - called
JC_test_construction_file.csv
- I've pushed that in the config.Construction ref: 49900102021
Additional function created
prepare_short_to_long()
- this takes any construction references flagged as 'short_to_long' and creates the instance 1 and instance 2. These are a copy of the instance 0, with instances updated. The three instances are then updated with constructed values as per the normal construction process.Short to long in construction file requires:
Note,
201 construction value is PG numeric (snapshot 201 has already been converted to alpha in staging) - Anne and I have discussed and there will be a ticket to move PG conversion to the beginning of imputation so it runs only once over all original/constructed records
Check,
Check this works with the construction updates for postcodes: RDRP-645 (if relevant - I put a postcode update in 601 for the instance 1 and 2 I was using in my test data, so 601 and postcodes_harmonised are showing different postcodes)
FYI,
There were two output_imputation_qa options in config, so I've taken one out