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
Some newer Family Tree DNA famfinder files seem to have SNPs assigned to chromosome 0. Similar to SNPs._assign_par_snps, use the RefSNP API to assign each of these SNPs to a chromosome and update the SNP's position to be consistent with the assembly.
The text was updated successfully, but these errors were encountered:
I have noticed that for AncestryDNA files, the _assign_par_snps step can take a substantial amount of time (> 1 minute), because of repeated API requests. I have currently bypassed this issue by setting assign_par_snps=False. Is there a way we can speed this up with the VCF_endpoint like you suggest in #19.
Yeah, I agree that having a resource like discussed in #19 to lookup SNPs would help here as well and would reduce repeated API calls. I'll start looking into this as part of #42.
Some newer Family Tree DNA famfinder files seem to have SNPs assigned to chromosome 0. Similar to
SNPs._assign_par_snps
, use the RefSNP API to assign each of these SNPs to a chromosome and update the SNP's position to be consistent with the assembly.The text was updated successfully, but these errors were encountered: