-
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-1095_run_pipeline_without_backdata #398
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you change this a bit as in my comment.
Also, if we're not loading backdata (if backdata is none) we can't output the links_qa output, so the pipeline fails when you try and do the impuatation_qa output (as I remember from previous experience :-))
src/dev_config.yaml
Outdated
|
||
temporary_pnp_settings: | ||
use_backdata: True | ||
use_mor: True |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
On reflection, I think that rather than using this temporary solution, I think it might be good to give them the option to run the pipeline without backdata/ Mor always.
So I think it would be good to do what we used to do:
in user_config, under load_ni_data, put in
load_backdata
We shouldn't have taken this out :-) Then please update the rest of the code.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ps- we only need one setting- like we have currently, we can have "if backdata not none" in the imputation_main
Hey Anne, you were correct on the imputation QA output needing some work with these preposed changes. Ticket is now ready for review! |
Pull Request submission
Insert detailed bullet points about your changes here!
Insert any instructions to help the reviewer, e.g. "install new requirements from
requirements.txt
"*Let the reviewer know what data files are needed (and if applicable, where they are to be found)
Closes or fixes
Closes #
Code
Documentation
Any new code includes all the following forms of documentation:
Args
andreturns
for all major functionsData
Testing
Peer Review Section
requirements.txt
Final approval (post-review)
The author has responded to my review and made changes to my satisfaction.
Review comments
Insert detailed comments here!
These might include, but not exclusively:
that it is likely to interact with?)
works correctly?)
Your suggestions should be tailored to the code that you are reviewing.
Be critical and clear, but not mean. Ask questions and set actions.