You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A concise description of why we're pursuing this task.
Currently we assume all ancestry requests are for hg38. As we don't have a liftover step, preferring to natively process hg19 vcf's, we need to carry the assembly in the ancestry submission job request, so that the appropriate model can be loaded.
Completion Criteria:
What is the goal, and how do we know this task is accomplished?
In the ancestry submission, assembly is a property, having the value of the assembly property on the job document
Implementation Summary
Give enough technical detail for a teammate to understand the proposed solution.
AncestryJobData needs to now expect an assembly property (string valued). This property then needs to be threaded through to the ancestry inference procedure, which currently hardcodes an hg38 expectation
The text was updated successfully, but these errors were encountered:
Background:
A concise description of why we're pursuing this task.
Currently we assume all ancestry requests are for hg38. As we don't have a liftover step, preferring to natively process hg19 vcf's, we need to carry the assembly in the ancestry submission job request, so that the appropriate model can be loaded.
Completion Criteria:
What is the goal, and how do we know this task is accomplished?
In the ancestry submission, assembly is a property, having the value of the assembly property on the job document
Implementation Summary
Give enough technical detail for a teammate to understand the proposed solution.
AncestryJobData needs to now expect an assembly property (string valued). This property then needs to be threaded through to the ancestry inference procedure, which currently hardcodes an hg38 expectation
The text was updated successfully, but these errors were encountered: